[ROM][10.0] DerpFest for OnePlus5/T [Official][2020-08-11]

[idoybh]

Apps in /system/app and especially /system/priv-app should bother us even more, because of more opportunities for those apps to collect data, share it with some server and do other stuff you don't want them to do, for example installing proprietary apps on your phone without asking(e.g. Health Services).

The default permissions for these apps are in the rom source, and no, they absolutely can't install another app without asking you first.

I find it gross that it is easier to make some OEM ROMs google-free than some Custom ROMs. If there are tens of proprietary google apps, of THE data collector, with tons of permissions and privileges, for example running in the background whenever they want to, on your phone, and it doesn't even BOTHER you, there is something wrong with you.

If you find it "gross" this rom is just not for you - go use some other rom (and PLENTY are available) with no google apps. I WANT some of them to run in the background, because I enjoy the services they offer for it. NO I don't care some big company collects data for revenue from me, not everyone is a privacy freak like you. And I don't want to hear your opinion about what is wrong or right with me.

Objectively read the whole Google Privacy Policy and then maybe question using this ROM. And saying "don't like it? use something else" is not helpful and stops progression of this ROM by stifling constructive criticism. This ROM shouldn't even be considered open source, as it includes non-crucial proprietary software which can't be removed without modifying /system yourself, and of that a lot!

The privacy policy is literally linked to you in the setup page when you sign in. Progression of this rom will NEVER be in the direction of not including gapps, and the fact YOU think it's better won't change that and won't change the definition of "progression". We have a vanilla variant (with no gapps) - you can always clone the source and build for yourself. And EVERY rom ships with proprietary parts btw. Most also either include gapps or have a gapps variant. I don't understand your whining to be honest - no one forced you to use this rom!! Just go somewhere else. Stop bothering me and wasting my time. Thank you.

 

[idoybh]

In my opinion AOSiP has more than enough customization, you should give it a try But of course, use what you want. You wouldn't need to debloat much on AOSiP tho, with pico gapps

If you like AOSiP I just can't understand why in the world would you come here to complain.

 

[skanadian]

cheeseburger - firmware

Heads up, cheeseburger link is broken in the OP.

 

[The_Overthinker]

In my opinion AOSiP has more than enough customization, you should give it a try But of course, use what you want. You wouldn't need to debloat much on AOSiP tho, with pico gapps

Probably, but there are a few other things to consider too when choosing a ROM. Firstly, the ROM has mostly been stable for me since Android 9. This creates a reliable impression about Derpfest as a whole. Battery life isn't always the greatest, but it has been pretty good for me too.

Most importantly, the derp community is buzzing and pretty active. Alex and Ido are pretty responsive and friendly devs, who're usually on top of a problem. :good:

So these are some of the reasons why I always return to Derp and it makes manual debloating worth it

 

[idoybh]

Heads up, cheeseburger link is broken in the OP.

Forgot to change one "dumpling" to "cheeseburger" when I copied the link. Terribly sorry. Thanks for letting me know

 

[skanadian]

Forgot to change one "dumpling" to "cheeseburger" when I copied the link. Terribly sorry. Thanks for letting me know

You taking feature requests at all? I would love to see 180 degree rotation (reverse portrait) and HD SBC (https://review.lineageos.org/q/ten-sbc-hd). More details on HD SBC here https://lineageos.org/engineering/Bluetooth-SBC-XQ/

 

[idoybh]

You taking feature requests at all? I would love to see 180 degree rotation (reverse portrait) and HD SBC (https://review.lineageos.org/q/ten-sbc-hd). More details on HD SBC here https://lineageos.org/engineering/Bluetooth-SBC-XQ/

I am, when it makes sense. 180° rotation is possible I guess, but will require too much work (changing stuff we already have implemented) for too little profit, if at all. Will add to my TDL nonetheless. Also the commits from LOS's gerrit are marked as abandoned, and viewing developer settings it seems like we already have it anyways. Not exactly sure but I think it's AOSP.
Edit: Yap, seems like we do have it: https://github.com/DerpLab/platform_system_bt/commit/444ea2c15a24cabaae87c8806b5d50e6ecb9a24d

 

[skanadian]

I am, when it makes sense. 180° rotation is possible I guess, but will require too much work (changing stuff we already have implemented) for too little profit, if at all. Will add to my TDL nonetheless. Also the commits from LOS's gerrit are marked as abandoned, and viewing developer settings it seems like we already have it anyways. Not exactly sure but I think it's AOSP.
Edit: Yap, seems like we do have it: https://github.com/DerpLab/platform_system_bt/commit/444ea2c15a24cabaae87c8806b5d50e6ecb9a24d

Thank you for the consideration.

LOS has it abandoned in favour of adding commits to 17.1 only. It was approved in LOS16 but not officially for LOS17.0.
I believe that derp commit is for A2DP SBC (normal audio), it is not for A2DP HD SBC. Not all bt devices support HD SBC so a toggle was added to the bluetooth profile settings (and developer options).
Here's the unapproved AOSP commits https://android-review.googlesource.com/q/topic:bt-sbc-hd-dualchannel+(status:open OR status:merged).
Compare a2dp_sbc.cc https://android-review.googlesource.com/c/platform/system/bt/+/759299/1/stack/a2dp/a2dp_sbc.cc to the derp commit you posted with references to "DUAL".

Alex added it to DerpFest pie (here: https://forum.xda-developers.com/showpost.php?p=79783435&postcount=1235) but unfortunately never made it to 10.

 

[NurKeinNeid]

Thank you for the consideration.

LOS has it abandoned in favour of adding commits to 17.1 only. It was approved in LOS16 but not officially for LOS17.0.
I believe that derp commit is for A2DP SBC (normal audio), it is not for A2DP HD SBC. Not all bt devices support HD SBC so a toggle was added to the bluetooth profile settings (and developer options).
Here's the unapproved AOSP commits https://android-review.googlesource...d-dualchannel+(status:open OR status:merged).
Compare a2dp_sbc.cc https://android-review.googlesource.com/c/platform/system/bt/+/759299/1/stack/a2dp/a2dp_sbc.cc to the derp commit you posted with references to "DUAL".

Alex added it to DerpFest pie (here: https://forum.xda-developers.com/showpost.php?p=79783435&postcount=1235) but unfortunately never made it to 10.

And I added it to Bare since first release. I tried to be close as possible to my Pie stuff.
@idoybh He is right. But yes, it's not merged by LOS. Poad merged it too btw. You can ask him if it's safe.

 

[neomeone]

Thanks for the smooth rom, instant daily driver!


Since I once again had to wrestle with Viper4Android, just wanted to share how I got it working after trying multiple methods. In case anyone else is struggling with it, give this a try.

1. Downloaded ViPER4Android FX 2.7.1.6 from https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

2. Installed the app, but did NOT open it

3. Rebooted

4. Opened the app, granted superuser, installed the driver and let it reboot

5. Opened the app again, installed the driver (dunno why this came up second time) and let it reboot

6. Now V4A was working, but I was missing all the DDC profiles, convolvers etc.

7. Got the profiles from https://androidfilehost.com/?fid=1322778262904011552

8. Copied the extracted files to the corresponding folders in: /Android/data/com.pittvandewitt.viperfx/files/
after this I noticed the files in /ViPER4Android/ so you might be able to just copy them from there

If you happen to switch master power off while playing media and playing with the settings, V4A might not work when you turn it back on. Just pause the media and re-plug your headphones.


Now of to GCam...

 

[bkma]

Thanks for the smooth rom, instant daily driver!


Since I once again had to wrestle with Viper4Android, just wanted to share how I got it working after trying multiple methods. In case anyone else is struggling with it, give this a try.

1. Downloaded ViPER4Android FX 2.7.1.6 from https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

2. Installed the app, but did NOT open it

3. Rebooted

4. Opened the app, granted superuser, installed the driver and let it reboot

5. Opened the app again, installed the driver (dunno why this came up second time) and let it reboot

6. Now V4A was working, but I was missing all the DDC profiles, convolvers etc.

7. Got the profiles from https://androidfilehost.com/?fid=1322778262904011552

8. Copied the extracted files to the corresponding folders in: /Android/data/com.pittvandewitt.viperfx/files/
after this I noticed the files in /ViPER4Android/ so you might be able to just copy them from there

If you happen to switch master power off while playing media and playing with the settings, V4A might not work when you turn it back on. Just pause the media and re-plug your headphones.


Now of to GCam...

I got a better and fully working procedure..
1. Intsall AML,reboot
2.Intsall Viper Magisk module, reboot
3.Open Viper and install drivers,reboot
4.It should work fine..
(Before all this remove all audio mods)

 

[Kopi Eyes]

Microphone not functioning

Hi all!

For the past two updates, 20200611 and 20200623, I have been having some issues with my microphone;
- unable to record voice notes on WhatsApp and Telegram
- I cannot be heard over voice call on Telegram and WhatsApp
- I cannot be heard over the phone app (a restart fixes this temporarily)
- WhatsApp video call works fine though

Any assistance with this matter would be highly appreciated!

 

[idoybh]

And I added it to Bare since first release. I tried to be close as possible to my Pie stuff.
@idoybh He is right. But yes, it's not merged by LOS. Poad merged it too btw. You can ask him if it's safe.

It probably is "safe" but I'm also sure LOS have a good reason abandoning it - Just can't seem to figure out why Anyways since it's opt-in, I will look at the code and if I see no red warning flags I will merge here as well.
EDIT: Tagging @skanadian

 

[idoybh]

Hi all!

For the past two updates, 20200611 and 20200623, I have been having some issues with my microphone;
- unable to record voice notes on WhatsApp and Telegram
- I cannot be heard over voice call on Telegram and WhatsApp
- I cannot be heard over the phone app (a restart fixes this temporarily)
- WhatsApp video call works fine though

Any assistance with this matter would be highly appreciated!

First of all I would love to see your logs. It works fine here. Secondly try with OK Google detection on and off. Make sure you have 0 audio modules installed
If all seems to have failed you (including clean flash) try it on stock - if it's still broken you have to replace the bottom mic

 

[Kopi Eyes]

Microphone functioning

First of all I would love to see your logs. It works fine here. Secondly try with OK Google detection on and off. Make sure you have 0 audio modules installed
If all seems to have failed you (including clean flash) try it on stock - if it's still broken you have to replace the bottom mic

Hey there!
Thanks for your quick feedback! I'm really enjoying this ROM and the community.

Firstly, I'm not sure how to send you my logs as I'm still a newb. :laugh:

Secondly, I tried with OK Google detection, switching it off then on, and that seems to have done the trick. All my above concerns have been fixed.

A detail that might be relevant or not, is that my system language was in French at first, then I changed it to English.

Thanks again! Glad I don't have to replace the mic.

 

[tcat007]

Very odd for system to default to French, never saw that happen, and I've flash about every version of Derp.

There's a log QS tile. I think you just hit that after you've done something you want a log of. Sometimes difficult if you have a crash.

 

[calvio]

Hi all!

For the past two updates, 20200611 and 20200623, I have been having some issues with my microphone;
- unable to record voice notes on WhatsApp and Telegram
- I cannot be heard over voice call on Telegram and WhatsApp
- I cannot be heard over the phone app (a restart fixes this temporarily)
- WhatsApp video call works fine though

Any assistance with this matter would be highly appreciated!

It's very strange, I clean flashed previous version and I had no mic problem, then I dirty flashed last version and still no problem (also with OK Google on) till this morning (I have sent many voice messages). After I read your post I tried again and nothing was working, voice recorder and Whatsapp messages were blank. But rebooting was enough to make everithing work again.

 

[Kopi Eyes]

Very odd for system to default to French, never saw that happen, and I've flash about every version of Derp.

There's a log QS tile. I think you just hit that after you've done something you want a log of. Sometimes difficult if you have a crash.

Hey tcat007! Just to clarify, my system didn't default to French. I set it that way, since I'm trying to pick up the language in as many ways as possible. I just pointed that out, since it was one of the steps I took.

It's very strange, I clean flashed previous version and I had no mic problem, then I dirty flashed last version and still no problem (also with OK Google on) till this morning (I have sent many voice messages). After I read your post I tried again and nothing was working, voice recorder and Whatsapp messages were blank. But rebooting was enough to make everithing work again.

Hey calvio! I know right! :fingers-crossed:

It's quite weird. Again, the microphone bugged out this evening as I was WhatsApp calling and it was okay after a reboot.

 

[Arokia]

Thanks for the smooth rom, instant daily driver!


Since I once again had to wrestle with Viper4Android, just wanted to share how I got it working after trying multiple methods. In case anyone else is struggling with it, give this a try.

1. Downloaded ViPER4Android FX 2.7.1.6 from https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx

2. Installed the app, but did NOT open it

3. Rebooted

4. Opened the app, granted superuser, installed the driver and let it reboot

5. Opened the app again, installed the driver (dunno why this came up second time) and let it reboot

6. Now V4A was working, but I was missing all the DDC profiles, convolvers etc.

7. Got the profiles from https://androidfilehost.com/?fid=1322778262904011552

8. Copied the extracted files to the corresponding folders in: /Android/data/com.pittvandewitt.viperfx/files/
after this I noticed the files in /ViPER4Android/ so you might be able to just copy them from there

If you happen to switch master power off while playing media and playing with the settings, V4A might not work when you turn it back on. Just pause the media and re-plug your headphones.


Now of to GCam...

If u want v4a to work for all audio apps n games u AUDIO COMPATIBILITY PATCH file.

Flash this acp on magisk while flashing give these volume steps.
After checking vol key workings
Press vol - (select No)
Press vol + (patch new logic)
Press vol - (select No)
Press vol - (remove listener)
Press vol - (select No)
Press vol - (No recommended)

If u want gcam and v4a work togather u need to switch selinux to permissive thats the only way

 

[idoybh]

Stop using audio mods. The best sound in a non biased sound