Develop Bugs

[Q] add module to kernel

Hello freinds,
I have a microsoft lifecam cinema hd webcam which I want to connect through my note2.is there any tutorial to add module to the kernel and make it working.
I am a windows user btw.
So anybody know if I can do it on window pc.
I know this thread should be in q/a section but due to any reason my question is not visible to that section.
Thanks in advance...

liondroid said:
Hello freinds,
I have a microsoft lifecam cinema hd webcam which I want to connect through my note2.is there any tutorial to add module to the kernel and make it working.
I am a windows user btw.
So anybody know if I can do it on window pc.
I know this thread should be in q/a section but due to any reason my question is not visible to that section.
Thanks in advance...
Click to expand...
Click to collapse
Even if it were possible, why do you want to add another camera to the device?
Edit: You however did pique my curiosity whether this can be done and perhaps it can!. The camera model you have mentioned is supported by the Linux UVC driver (check here: http://www.ideasonboard.org/uvc/). This is a part of the standard kernel source (it's located at /drivers/media/video/uvc)
So basically, you need to compile the 'uvcvideo.ko' module. I don't know if this can co-exist with the existing camera driver, so you may have to disable the driver for the front / back cameras and compile the uvcvideo driver in or as a module.
Good luck!

seltaeb said:
Even if it were possible, why do you want to add another camera to the device?
Edit: You however did pique my curiosity whether this can be done and perhaps it can!. The camera model you have mentioned is supported by the Linux UVC driver (check here: http://www.ideasonboard.org/uvc/). This is a part of the standard kernel source (it's located at /drivers/media/video/uvc)
So basically, you need to compile the 'uvcvideo.ko' module. I don't know if this can co-exist with the existing camera driver, so you may have to disable the driver for the front / back cameras and compile the uvcvideo driver in or as a module.
Good luck!
Click to expand...
Click to collapse
The stock front camera has a bad low light visibility where as the microsoft lifecam has a very good visiblity even in the room with all lights off, at night ofcourse (the light source is only the screen itself falling on my face)
As i already know this is possible. Take a look..
http://www.youtube.com/watch?v=taZ3zd37nMI
I think there is no option other than to install linux on my pc and give a try.
Any suggestions would be appreciated.

liondroid said:
The stock front camera has a bad low light visibility where as the microsoft lifecam has a very good visiblity even in the room with all lights off, at night ofcourse (the light source is only the screen itself falling on my face)
As i already know this is possible. Take a look..
http://www.youtube.com/watch?v=taZ3zd37nMI
I think there is no option other than to install linux on my pc and give a try.
Any suggestions would be appreciated.
Click to expand...
Click to collapse
Although unsupported, I believe it is possible to build the kernel on Windows under Cygwin. Have a look here for setting up the build environment etc on Windows: http://forum.xda-developers.com/showthread.php?t=1686310. Note that Samsung's recommended toolchain is actually 4.4.3 (but you might be able to find that with a bit of Googling).
Alternately, I can build the uvcvideo.ko module for you. However, I am going away from tomorrow morning for a long weekend, so you might have to wait till Sunday evening unless I manage to find some time to do it tonight itself. Otherwise you can try requesting someone else here to build it for you - it only takes a few minutes.

seltaeb said:
Although unsupported, I believe it is possible to build the kernel on Windows under Cygwin. Have a look here for setting up the build environment etc on Windows: http://forum.xda-developers.com/showthread.php?t=1686310. Note that Samsung's recommended toolchain is actually 4.4.3 (but you might be able to find that with a bit of Googling).
Alternately, I can build the uvcvideo.ko module for you. However, I am going away from tomorrow morning for a long weekend, so you might have to wait till Sunday evening unless I manage to find some time to do it tonight itself. Otherwise you can try requesting someone else here to build it for you - it only takes a few minutes.
Click to expand...
Click to collapse
it will be a great help if u can create the module for me. Thanks in advance

liondroid said:
it will be a great help if u can create the module for me. Thanks in advance
Click to expand...
Click to collapse
This is more a driver issue than kernel. And even though there may be linux drivers for your webcam. Google has not yet fully merged the android kernel into the linux family, so it may not be possible to port. I wish you all the luck though :fingers-crossed:

AndroHero said:
This is more a driver issue than kernel. And even though there may be linux drivers for your webcam. Google has not yet fully merged the android kernel into the linux family, so it may not be possible to port. I wish you all the luck though :fingers-crossed:
Click to expand...
Click to collapse
uvcvideo.ko is a module which contains almost all webcam drivers including mine.It can be implemented to android kernel also.See the video link in previous posts.I already managed to get uvcvideo.ko, now trying to add to the kernel source. Hope I am going in right direction.

liondroid said:
uvcvideo.ko is a module which contains almost all webcam drivers including mine.It can be implemented to android kernel also.See the video link in previous posts.I already managed to get uvcvideo.ko, now trying to add to the kernel source. Hope I am going in right direction.
Click to expand...
Click to collapse
Seems like the reverse direction actually. You already got your module compiled and now you are changing the source?
PS: So you no longer want me to compile the uvc module for you?
Sent from my GT-N7100 using Tapatalk 2

seltaeb said:
Seems like the reverse direction actually. You already got your module compiled and now you are changing the source?
PS: So you no longer want me to compile the uvc module for you?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
one of my frend is a linux user so i asked him to do for me but he messed up the kernel so pls sir I am waiting for ur work.

liondroid said:
one of my frend is a linux user so i asked him to do for me but he messed up the kernel so pls sir I am waiting for ur work.
Click to expand...
Click to collapse
Here you go. This is an ODIN flashable kernel (unzip it and flash the .tar file using the PDA section in ODIN). The module is located in /lib/modules.
PS: The kernel is compiled from stock sources, except for addition of the lulzactiveQ governor (pegasusQ is still default) and a couple of other patches (missing touchkey drivers and AndreiLux's firmware naming / boot-up time reduction fix).
Edit: Added only the module in uvcvideo.zip. Unzip & copy it to your phone somewhere and insmod it to load. If it doesn't work with your stock kernel, please use the full kernel against which it is built (provided above).

And here's the Samsung stock kernel from DDLJ3, in case you want to revert back. Again, ODIN-flashable after unzipping.

I might be a bit off topic:
Is there anyway to load an under volt module?
I've always been using Tegrak over clock ultimate but it's not updated since 2 months..
And it's obviously not working on our beloved gsn2
I'd love to stay as stock as possible but with under volt

TMaLuST said:
I might be a bit off topic:
Is there anyway to load an under volt module?
I've always been using Tegrak over clock ultimate but it's not updated since 2 months..
And it's obviously not working on our beloved gsn2
I'd love to stay as stock as possible but with under volt
Click to expand...
Click to collapse
Please just use AndreiLux's excellent kernel to accomplish this.
Sent from my GT-N7100 using Tapatalk 2

Well I'll give it a try, but in term of battery life I've never had better results than stock kernels, that's why I was asking

seltaeb said:
And here's the Samsung stock kernel from DDLJ3, in case you want to revert back. Again, ODIN-flashable after unzipping.
Click to expand...
Click to collapse
Thankyou so much sir, will let u know after trying it.

seltaeb said:
Even if it were possible, why do you want to add another camera to the device?
Edit: You however did pique my curiosity whether this can be done and perhaps it can!. The camera model you have mentioned is supported by the Linux UVC driver (check here: XXXurl omittedXXX is a part of the standard kernel source (it's located at /drivers/media/video/uvc)
So basically, you need to compile the 'uvcvideo.ko' module. I don't know if this can co-exist with the existing camera driver, so you may have to disable the driver for the front / back cameras and compile the uvcvideo driver in or as a module.
Good luck!
Click to expand...
Click to collapse
Hello, excuse my off topic but i have a similar need:
i have an Android mk3188 tv box that has uvcvideo support in the kernel i'm using. the Camera is in the list of supported cam (093a:2700 - iSonic W002)
When i connect the camera i receive the following message:
[10501.638841] usb 1-1.3: Product: USB2.0_Camera
[10501.643370] usb 1-1.3: Manufacturer: PixArt Imaging Inc.
[10501.657777] uvcvideo: Found UVC 1.00 device USB2.0_Camera (093a:2700)
[10501.673615] input: USB2.0_Camera as /devices/platform/usb20_otg/usb1/1-1/1-1.3/1-1.3:1.0/input/input5
[10559.678208] qtaguid: ctrl_counterset(s 1 10112): insufficient priv from pid=422 tgid=364 uid=1000
[10560.472909] DWC_OTG: dwc_otg_hcd_urb_enqueue urb->transfer_buffer address not align to 4-byte 0xed6abaca
[10560.482867] uvcvideo: Failed to query (GET_DEF) UVC control 2 on unit 3: -1 (exp. 2).
[10560.492619] DWC_OTG: dwc_otg_hcd_urb_enqueue urb->transfer_buffer address not align to 4-byte 0xed6abaaa
[10560.502458] uvcvideo: Failed to query (GET_DEF) UVC control 3 on unit 3: -1 (exp. 2).
[10561.087346] qtaguid: ctrl_counterset(s 0 10047): insufficient priv from pid=422 tgid=364 uid=1000
I have tried to set /dev/video0 chmod to 666 but the error message is the same.
How can i update uvcvideo from 1.00 to 1.10? i need to recompile kernel or there are others solutions?
can i use uvcvideo.ko provided in this thread? how can i do?
Thank you

seltaeb said:
Here you go. This is an ODIN flashable kernel (unzip it and flash the .tar file using the PDA section in ODIN). The module is located in /lib/modules.
PS: The kernel is compiled from stock sources, except for addition of the lulzactiveQ governor (pegasusQ is still default) and a couple of other patches (missing touchkey drivers and AndreiLux's firmware naming / boot-up time reduction fix).
Edit: Added only the module in uvcvideo.zip. Unzip & copy it to your phone somewhere and insmod it to load. If it doesn't work with your stock kernel, please use the full kernel against which it is built (provided above).
Click to expand...
Click to collapse
Is file uvcvideo.ko specifically for galaxy note or can i use it on a different device?

Is this still required for UVC video to work or does it work on the latest ROMs/kernel?
I've read it works out of the box on the Nexus 7 but I don't have webcam to test on my Note2.

Nevermind. I tried the app Dashcam which checks for UVC driver. GFs S3 does not pop up an error while my Note2 (and my HTC Desire 601) do.

OnePlus One DroidKit | by iTechy OPEN SOURCE! | No longer being maintained

Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirements​To run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
Downloads​No Download as no longer maintained and buggy​QR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issues​You tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06​

FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit

I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...

GOOD JOB .....Bro

kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you

Anyone already try this tool? I want download, but size so damn high

zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up

timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD

... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.

itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:

ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)

I can´t flash twrp with this toolikt any one have a clue?

Do you have the adb drivers installed? Or is it throwing an error?

Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk

Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.

dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...

Download link is not working. Please re-up. Thanks

godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1

If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.

[CLOSED] Enable Native Call Recording [OOS] [ROOT/NON-ROOT] [APP/MAGISK MODULE/ADB/TASKER]

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.

[SOLVED] Wi-Fi failure with custom kernel

I built a minimally modified BTI (Android 10) kernel for my Exynos S20+ (G986B) from the Samsung-released source and used Android Image Kitchen by @osm0sis to extract the boot.img from my device and repack it with the kernel image I built. I subsequently installed the new boot.img with dd, and the phone boots normally, including showing the expected uname output.
The only issue I've seen so far is that Wi-Fi doesn't work. I observed the following:
Immediately after installing the kernel, Wi-Fi simply refuses to turn on, with the button turning back to gray a few seconds later. dmesg output includes complaints about failure powering up Wi-Fi chip and downloading firmware to it.
After reformatting /data, Wi-Fi turns on and wlan0 is even visible in ifconfig output, but no networks are discovered and it is impossible to connect to any network. dmesg output contains numerous WIFI_SEC errors including references to files that do not exist in /data/misc/conn
After reinstalling a boot.img containing the stock kernel, normal Wi-Fi functionality is immediately restored on next boot, even without reformatting /data.
A search of XDA and the greater web turned up lots of complaints about this issue spanning many years and generations of Galaxy devices. The solutions I found fell into three categories:
Replacing libsecure_storage components with a patched version. The version I found was quite old.
Setting ro.securestorage.support to false in build.prop. There are also comments that indicate this doesn't work.
Placing some provided files in /data/misc/conn. This seems somewhat unlikely to be applicable for this device/build since there are no files here even when Wi-Fi is working correctly with the stock kernel.
Can someone (maybe one of the prolific kernel devs like @freeza ) explain to me what is going on here and suggest a good way to address it? I'd definitely prefer an approach that doesn't involve inserting prepared binaries.
Thanks.

The problem here is the way the Wi-Fi driver (drivers/net/wireless/broadcom/bcmdhd_101_12) is built in my custom Kernel:
Makefile uses the ANDROID_VERSION or PLATFORM_VERSION environment variables to define the ANDROID_PLATFORM_VERSION macro, but does not do so if ANDROID_VERSION or PLATFORM_VERSION are not set.
dhd.h uses the lack of ANDROID_PLATFORM_VERSION to:
Set the VENDOR_PATH macro to "" resulting in firmware being sought in /etc/wifi instead of /vendor/etc/wifi as expected for Android 10.
Set the PLATFORM_PATH macro to "/data/misc/conn/" resulting in configuration being sought in /data/misc/conn instead of /data/vendor/conn as expected in Android 10.
So, the solution was much simpler than any of possible methods I found earlier. All I had to do to resolve this problem was run this before building my Kernel:
Bash:
export PLATFORM_VERSION=10.0
It seems that this is an omission in Samsung's build instructions. Upon installing my kernel built this way, Wi-Fi works as expected. This is very similar to what is described in post 79 of this thread.

Thank you, I also meet wifi problem on my s8 kernel, I will try to fix it by you provided.

Sadly, this didn't work for the Galaxy Tab 8.0 (SM-T290) which suffers identical symptoms when I build from kernel source. There's no reference to ANDROID_VERSION, PLATFORM_VERSION, ANDROID_PLATFORM_VERSION or even VENDOR_PATH in any kernel source file.

sjevtic said:
The problem here is the way the Wi-Fi driver (drivers/net/wireless/broadcom/bcmdhd_101_12) is built in my custom Kernel:
Makefile uses the ANDROID_VERSION or PLATFORM_VERSION environment variables to define the ANDROID_PLATFORM_VERSION macro, but does not do so if ANDROID_VERSION or PLATFORM_VERSION are not set.
dhd.h uses the lack of ANDROID_PLATFORM_VERSION to:
Set the VENDOR_PATH macro to "" resulting in firmware being sought in /etc/wifi instead of /vendor/etc/wifi as expected for Android 10.
Set the PLATFORM_PATH macro to "/data/misc/conn/" resulting in configuration being sought in /data/misc/conn instead of /data/vendor/conn as expected in Android 10.
So, the solution was much simpler than any of possible methods I found earlier. All I had to do to resolve this problem was run this before building my Kernel:
Bash:
export PLATFORM_VERSION=10.0
It seems that this is an omission in Samsung's build instructions. Upon installing my kernel built this way, Wi-Fi works as expected. This is very similar to what is described in post 79 of this thread.
Click to expand...
Click to collapse
how do I know my platform version?

dirty flash of my ROM worked for me.

dirty flash of my ROM worked for me.

walker2771 said:
dirty flash of my ROM worked for me.
Click to expand...
Click to collapse
what is it

UPDATED & MODDED ADRENO 640 DRIVERS for SURFACE Duo (MAGISK MODULE)

*shouldn't start this way but this first paragraph is for the SAVY Rooted SURFACE DUO USERS whom understand drivers and this whole comcept of the ability to upgrade Adreno drivers, LOOKNG TO SKIP THE FLUFF AND CUT THE CHASE *expedited summary*
You can see your current Display/graphics driver via an app like AIDA64 via the play store (for reference my up to date Android 12 Duo had v502 drivers).... The installation is like any standard magisk module. Simply flash a suitable SM8150(aka snapdragon 855/Andreno 640) driver via magisks/Fox's MMM obtained from this link:
adreno driver for sm8xxx/sm7xxx/sm6xxx
adreno driver magisk module for sm8150 or sm8xxx/sm7xxx/sm6xxx family running on R or newertested on sm8150 and sm8250WARNING : [email protected] has known crash issues when used with magiskWARNING: BLOBS HAS...
www.pling.com
be sure to read the details of the different varients... I recocommend starting with the stock 530. Use at your own risk,.. I recommend the 530 edition, as they have reported no known issues, after install you can verify the current driver version via an app like AIDA64...
Ps.. I used fox's MMM to install the magisk module for the stock 530 first, and after verifyimg all was well, I was able to revert to v502 simply by uninstalling via Foxs MMM & rebooting... so that gave me confidence to install the version I am using currently which ist The December 2022 530 release posted, that also emulates being an ADRENO 730...it's actually as smooth as butter, past first 24hrs & benchmark tests etc (no battery studies by me tho so you'll have to explore that yourself as all I can say is that my temps were much more stable in AnTuTu enroute to higher scores.. also I have not tried the later drivers, opting to stay bug free with the v530 for now, since performance is already top tier imo, playing all games I have at max even prior, but the UI/UX is noticably more responsive and smooth which makes me eager for my pen to arrive as I'm certain these improvements will also translate there as well as the UX for me now has literally zero input/update delay)
**************************
FULL Post below
**************************
Here goes a full post....I am not good at this but yeah..lemme drop something useful relevant and compatible to our devices I'm thanks *this is not any of my work nor is it specifically designed for Surface Duo users yet it works perfectly considering it's targeted for our same underlyimg hardware
------UPDATED/MODIFIED ADRENO 640 GRAPHICS DRIVERS TO BOOST OVERALL PERFORMANCE
...We all know Microsoft is historically behind when it comes to providing users with the latest hardware drivers and the situation is no different here....
Vroom, hello I've been super busy absolutely renovating my Surface Duo and I'm just felt this particular discovery of a mod would be a great one to highlight. Essentially, you more than likely are running outdated drivers for our Andreno 640, to identify exactly what version your drivers are, you can use the 'AIDA64' application to identify which drivers you are running (I'll guess v 502 if your surface is up to date on Android 12 like minea).. nevertheless we all know how important drivers can be to increased performance and implementation of various codimg advancements to enhance existing hardware. Your display drivers are oh so critical to your entire experience while using your device for absolutely any visible task, and especially are the backbone of gaming performance... So because this is such a useful all around mod for all of us looking to stay on the bleeding edge of things, I feel it would be unjust to not share such a useful thing that most Duo users may not otherwise sought out.
This is not my own tweak nor creation, so use this at your own risk. In which case, I will recommend that if your set-up is like mines, in that your Surface is running driver version 502 and is up to date with either Android 12, you should feel pretty safe to install this mod via FOXES MMM... However if you typically flash magisks mods in other fashions, well proceed with caution (only because I just don't know, however it is my belief that if you flash version 530 which has been determined stable and don't touch anything that isn't designed exclusively for OUR SURFACE DUO MODEL SM8150, that you should be safe..
Sorry i am not in the business of posts like these so let me just tell you my process of which I feel safe, however I am not suggesting there is any one correct way as I'm theory ,it's simply a matter of flashing the correct files to magisk..
But because I have to explain something without just assuming you're a modded that's already ready for the links
***********UPDATED AND MODIFIED GRAPHICS DRIVERS FOR SM8150 (SNAP855,A640)*****
Requirements (for SURFACE DUO, SNAPDRAGON 855 (aka **SM8150**), ADRENO 640)
Android 11/12
Rooted
Magisk installed
Fox's MMM (at least that's what I use to flash magisk files)
Optional (Aida64) this app is one of such that will display your driver version in the display tab
*****Step 1
So essentially after verifying with the Aida64 app that you have a Duo with an 855, and ADRENO 640...
************Step to 2
You simply need to head over to this site download the desired drivers
Click files and select an SM8150 driver*
adreno driver for sm8xxx/sm7xxx/sm6xxx
adreno driver magisk module for sm8150 or sm8xxx/sm7xxx/sm6xxx family running on R or newertested on sm8150 and sm8250WARNING : [email protected] has known crash issues when used with magiskWARNING: BLOBS HAS...
www.pling.com
Personal advice/info
*(I person highly recommended 530 as they have been reported essentially flawless and I can testify that even the very latest 530 mod posted that reports itself as being a fake Andreno 730 (this allowing more freedom in certain games that limit options based on hardware) nevertheless I am but a user who hasn't tried everything however I did beginning installing the stock v530 and confirming that after uninstalling with Foxs MMM that!y original 502; drivers safely returned prior to reaching for the recent December 530 fake a730 running ever so beautifully on my device currently *
*********Step 3
After downloading the desired SM8150 driver, use Fox's MMM and select install module from storage then reboot and confirm the updated driver version via AIDA64, that it!
**********DOME!
For more detail here are the original Sources I followed
Honestly this is the key source, where I obtained all the important stuff...which is a telegram channel
Adreno | Konabess support
You can view and join @adreno_konabess right away.
t.me
And I got them telegram link from this thread (of which has information I found ultimately irrelevant in the end but hey..)
Update Adreno GPU drivers Vulkan to latest v615 any Device: Drastically improve performance gaming.
4utech85.blogspot.com
Ummm here are some screenshots of my Duo getting a boost in score (feels bigger than that tho) and now reporting my Duo has a 730 in it lol ps no the drivers doesn't make the display small like mines I change the dpi myself via developer options to make use of the screen lol

@cqqx2
Hello. I have noticed that you created some duplicates of this thread. I'm sure there was a glitch in the matrix
So is this thread your go-to thread now?
Be so kind to let me know.
Cheers,
mrjuniork (Forum Mod)

mrjuniork said:
@cqqx2
Hello. I have noticed that you created some duplicates of this thread. I'm sure there was a glitch in the matrix
So is this thread your go-to thread now?
Be so kind to let me know.
Cheers,
mrjuniork (Forum Mod)
Click to expand...
Click to collapse
Yes this is the correct one

cqqx2 said:
Yes this is the correct one
Click to expand...
Click to collapse
Perfect. Thx for getting back to me.
Cheers