yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nr7777:
Differs strongly, Last night in around 6 hours i lost 2-3%. This ist currently with Scorpion Rom ans Blackened Mod and only Whatsapp/XDA installed, no other tweaks.

Currently trying out different Android Q Roms to see which ones best for battery life since theyre all more than enough for me in terms of performance.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Try STOCK and gravitybox! Magisk/Edxposed/Riru core:svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nr7777:
I am new to all this. Could you please explain what tweaks I should apply with the things you mentioned ? I heard that with Edxposed losing SafetyNet status is basically unavoidable. Currently i am running Lineage 17.1 and this mod, else is stock but auto sync off, AOD off, swift black theme...

Seems good so far but let's say i was expecting a bit more improvement on battery (not saying that i am not the one doing it wrong).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Did you try just a clean flash? Are you on pie?

What I mentioned was Magisk which is what gives us root.

Then there is a module Riru core I think that allows us - Edxposed .

Then lastly, there's gravitybox - the module which, when applied via Edxposed that NEEDS Riru core module from magisk to work - allows STOCK ROM users additional features not readily available in STOCK!

The stuff I had mentioned, though, I don't think have heavy impact on battery...

Are you on Pie (Android 9)? What I think (and I'm no expert) is to just maybe do a clean flash of the ROM and setup all your apps again. I've found that, while reading XDA and my experience, there are many many reasons for battery drain, usually one common answer or suggestion.

Hope I was some help, I mean. If you aren't like, stuck on your phone setup now a clean flash ( in TWRP - FACTORY RESET) then reflash the ROM may be whats needed.

Edit - and Aha, you're on 10 . So you are familiar with flashing without TWRP. :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nr7777:
Already did several clean flashs with different ROMs (I'm on 10). I will let it settle now a bit and then see but appreciate the help !

Another weird thing maybe OP [MENTION=8852292]xFirefly93[/MENTION] knows...

Newest blueline version, mobile data does not turn back on after I turned it off allthough it shows to be turned on. Simple reboot and mobile data works again. Maybe someone can take a look at this. This also happens when switching to WiFi and back.

This happens for me when installing BlackenedMod. Does this mod work flawlessly with Kiri Kernel so far besides for me? Does anyone have an idea ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] prozo:
So IDK if anyone followed those guides but we have differing guides. The OP says to place it in a certain directory and the other guides by Phalanx go to a different directory. Then they also have two different permissions they say need to be applied.

That being said I did do OPs guide still trying to see if it's enabled though.

Edit: still haven't seen the logs folder populate. Made the logs folder under my internal storage too. Can't seem to figure out what's going on here
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rooneyaut:
Hello!

I have an strange issue since installing this mod.

After installing this mod with no errors showing up in the logs, I had issues with my mobile network connection.

After a reboot it's working fine.

It seems like it happends only if I connect for some time with a WiFi network and after disconnecting/turning wifi off my LTE connection is gone. The only way to get LTE back is a reboot. I am currently on Havoc OS 3.1 (200120) with the Kernel coming with the ROM (Kirisakura 1.4.1) and Magisk 20.3.

My Magisk modules are BusyBox for Android NDK v1.31.1 and Pixel Camera DSP/Easel Permission v2 (for CameraPX).

I have created an logcat while the LTE connection was gone.

I have disabled & reenabled my mobile data, turned wifi on & off again while logcat was running.

Holefully somebody can help, because I really want to use this mod.

Thanks

Ronny
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
Did you reboot after placing the files where the OP states?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] prozo:
Yes
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
[MENTION=8852292]xFirefly93[/MENTION]

Any news on how things are going?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RagedElimanator:
Any chance we could please get an update on the status of this project, the latest patch for pixels fixed some big issues. This mod has been becoming more and more obsolete recently, when a good while back it was making a real difference.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] darkstar73:
See the title of the thread. It shows EOL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Magnufire2:
I can't find the download link anywhere. This is the page the "latest release can be found HERE" link goes to but there's no download on any post or page of this MOD.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] entux:
does anyone know if this helps with the battery consumption on playstore service-less signal battery drain? It regularily uses 70%+ (with mobile data) and 30%+ (with wlan).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Look for the "Logs" folder on your internal storage. You should see 4 files. You can then check if all the scripts were executed :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
If there aren't any files, what should I do? I've placed the script in the folder in service.d, and created the logs folder already. And busybox is installed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
And you changed the permissions of the 2 scrip files to 0755?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
Two files? I thought there's just one script file. I changed it to 755 already
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
After you extract the zip file, is this what you see?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
No! Just blackened mod and changelog

---------- Post added at 04:30 AM ---------- Previous post was at 04:29 AM ----------

Could you please share the zip? I just used the one in the op
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
I really can't because I have the P2XL. So I reckon Firefly hasn't enabled the junkcleaner script yet for your device. Still, it shouldn't matter. If you've changed permissions, have magisk and busybox installed, the script should initiate after you reboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
Also, magisk applies its stuff after 3 seconds right? Because I set exkm to apply on 3 seconds. I did not change any defaults of the kernel except switch to anxiety io. So wondering if exkm might overwrite the script.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Usually magisk takes up to 90 seconds to apply my scripts and all my other modules. When you say "anxiety" are you meaning the governor?? As far as the EXKM app, mine is set to 10 seconds to apply after reboot, and it never overwrites my scripts.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
Scheduler.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Still shouldn't matter. What kernel and root explorer type app are you using?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
Exkm with kirisakura. Use solid explorer
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Might try a different file manager. I've seen reports of problems with some of the file manager apps. Root Explorer works great for me :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ART:
So updating to magisk 18 worked. Got the log, says it's successful. But the governor options on exkm don't change as per the script. I changed the io scheduler to anxiety, does it make a difference?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
i downloaded the zip on a computer and there was only one script.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
That's right! :)

By checking if a output log file have been generated inside the logs folder at the root of your internal storage.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Did you put the script within the service.d folder with 0755 file permissions before you rebooted?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dukat0s:
[MENTION=8852292]xFirefly93[/MENTION] welcome on board my friend ?

Great work as always. Running fast and smooth
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Your scheduler won't change. Pick whatever you like :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Thanks a lot!

:highfive:

When did you shift to Pixel 3 (XL)?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dukat0s:
Before it even released :) it's great device so far ;) hope you like it.. if u need anything msg me at telegram buddy ❄️❄️❄️
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bbender716:
Been a long time user of root explorer myself. Nice script and I like the idea of someone creating this instead of LTK which tries to account for so many devices when Pixel is a very unique beast. :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
I will!

:highfive:

That's true.

It's better to make / write a device specific script because something that is working perfectly on device A may perform like Justin Bieber (which means like thrash) on device B.

Pure dedication is IMO the only way to creating some pretty unique!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] J32A:
I want to install but i don't understand what you mean by name the folder "log".
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nyydynasty:
use your file manager app of choice (i.e. for me its root explorer) and go to the root of your internal storage and create a folder called "logs". Then install this mod and reboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
Still one script in the zip and nothing in logs
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jd1639:
Will that folder survive a reboot?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] CoreGaming:
anyone tried it with the january patch?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Works fine on the P2XL. Can't imagine why it wouldn't on your device :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dukat0s:
Yeah running good so far since yesterday :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] freebee269:
I'm having issues with the logs folder also. I'm on stock rooted kernel. I have the text and .sh files in service.d and created a logs folder in Internal storage. Changed permissions to 0755. Also am using root explorer. But upon reboot I have nothing in the logs folder.

Edit: after the third reboot it finally took effect. Now there's a .log file in logs folder that says it has more than successfully worked.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Then everything is working as it should!

Enjoy :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
A little, but important, update will be released at the end of this week once I am off from work. Perhaps at Saturday if everything is going as planned!

Just wait.

How have the initial release btw performed so far for everyone? :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] freebee269:
I'm using the stock kernel on December build. The thing I've noticed the most is the decrease in idle battery consumption.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DarkPhoenix:
I found the BusyBox module on GitHub but I can't get it to download. Can someone send me the link for the download please?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DarkPhoenix:
Got it, thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Julian_U2:
Hi, how much screen time are you achieving?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jblanko6:
Hello, do I need to uninstall this mod or BusyBox for that matter before updating to January update ?

And if so how ?

Thanks in advance v
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 12Fully:
If you want to delete it just delete the file from /data/adb/service.d

Couldn't hurt just to be safe since it's so easy to install.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Anyone find out why this mod is breaking karisakura kernel causing freezing?

As soon as I remove this script the phone works normally
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Update!

Note: It is recommended that you reboot your phone after you have applied v1.1 so the changes / improvements takes full effect and is fully up & running as intended.

Version v1.1 (Minor release):

- Customized a huge amount of various kernel specific stuff (So everyone will benefit from using version 1.1)

- Adjusted a few IO block queue based tunables for a overall snappier and more responsive system

- Added in & modified my partition mounting tweak from BM for P2(XL) (All the credit goes to [MENTION=4793042]pkgnex[/MENTION])

- Tweaked the Flag Tuners (Originally thanks to [MENTION=5514152]Paget96[/MENTION] for sharing this with me, you rock).

- Made it possible to disable Fsync directly on-the-fly within the script if wished and needed (Experimental)

- Some other misc stuff that I've forgotten to mention here

Enjoy! :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Does this still generate a log for the logs folder
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Oh crap, I forgot to add a possible workaround for it.

Everyone, create the logs folder manually for now and just reboot the phone once so the output log is generated as intended (after the script have been executed behind the scenes).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
I already have the logs folder but this doesn't seem to be generating a script after execution like 1.0 did.

---------- Post added at 10:31 PM ---------- Previous post was at 10:26 PM ----------

Never mind. It was the permissions.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
It replaces the older output log file automatically after the script have been executed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I had to remove the same line of the script in v1.1.

Otherwise I instantly got bootloops on the Kirisakura kernel.

It seems to work fine now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
The difference(s) is all userspace specific - how you interacts with your device for example.

Regarding the discard_max_bytes, I don't know tbh. I am using it set to 0 with great results on Proton kernel. Maybe something at the kernel level for Kiriskura that may causes a kernel panic?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kdrag0n:
discard_max_bytes shouldn't be there in the first place. TRIM, also known as "discard" in Linux filesystems, is a way for the OS to inform the storage controller (UFS) that certain blocks of storage are no longer being used and the controller can safely erase and overwrite them without consequences.

Normally, the blocks are marked as free by the controller upon receiving a TRIM command. The filesystem will issue a TRIM command as soon as files are deleted. Without TRIM, the controller isn't aware of which blocks are free to be used and which have important data on them. Over time, this results in write speed degrading significantly and is the reason TRIM was created in the first place. It might result in some temporarily miniscule improvements in file deletion performance, but bite back with slow write performance later on, especially when there's a lot of data on the filesystem.

And yes, this renders the fstrim calls later in the script useless.

[MENTION=8852292]xFirefly93[/MENTION] please remove this.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
I'm uploading v1.2 tomorrow with the earlier mentioned stuff removed. Sorry btw for the impulsive and deeply full scale experimental mistake that I've done, everyone.

It won't happen again, I promise.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Update!

Note: It is recommended that you reboot your phone after you have applied v1.2 so the changes / improvements takes full effect and is fully up & running as intended.

Version v1.2 (Minor release):

- Added, but commented out, my own preferred settings for Dynamic Stune respectively CPU Input Boost (See the specific section for more information)

- Made the whole fstrim part optional (You're free to manually "enable it" yourself if you of course want to)

- Removed the experimental 'discard_max_bytes' part

- Purged a few additional & pretty much useless lines

Enjoy! :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I'm not sure what you mean by "commented out". How do I enable the cpu input boost?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Seriously? You're on a Dev forum
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Remove the "#" in front of the commented out parts.

For example..

Instead of looking like this;

# echo "N" > /sys/module/sync/parameters/fsync_enabled

It should end up like this;

echo "N" > /sys/module/sync/parameters/fsync_enabled
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hyundai2010:
hello, can i use this mod with xenonhd and magisk?

which app i need to put the file in the correct folder?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
The steps are detailed in the first post, have fun!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kingbri:
Blackened Mod v1.3 has been released!

This is the new official, unified magisk module for blackened mod which supports all pixel devices. (If you're not on a pixel device, you will be rejected by the installer). The OP [MENTION=8852292]xFirefly93[/MENTION] is going to learn how to do this whether he likes it or not...

-Fix sqlite issues

- Use my own compiled sqlite binary (Tools are not mine) https://github.com/bdashore3/sqlite-...ster/README.md

Please remove the sqlite module as it is auto-installed

Download here: https://github.com/King-Kernel/Blackened-releases

(There's an easter egg in the latest commit if you find it, post it here :) )
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Abortion due to not being a Pixel or pixel 2. I am on a Pixel 3 XL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kingbri:
It's aborting for you? Ok, I'll look at it

Edit: I'm an idiot. Forgot to change device names when cping

EDIT #2: fixed
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Part 2 was successful. Thank you for sharing
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DaKrampi:
Not completely successful on my side.

02BlackenedMod.sh does not get copied to /data/adb/service.d/ by install.sh, because the script in common/bluecross/ is named 02blackenedmod.sh (all lower case).

Fixed it by renaming it to 02BlackenedMod.sh inside the zip and reinstalling using Magisk Manager.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kingbri:
Once all of those errors are fixed up and everything's smooth, I'm gonna submit to official magisk repo.

V1.4 has been released with improvements to logging
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
1.4 installed and I have no issues so far. Thanks!

FWIW, 1.4 was also successful on my p2xl.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
1.4 kills ok Google for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paget96:
Thanks for mentioning me. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Running a theme?

It worked for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jblanko6:
V1.5 is been out but not sure what the change log or if it's for the 3XL even lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kingbri:
Hear that big things are happening soon

---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------

Also, v1.5 fixes a naming issue. So install it asap
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paget96:
Yes, we are working on it. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
Tried it again and it work this time. Go figure.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hochoch:
Hi - I installed v1.5 on my 3xl using magisk and it appeared to execute fine. now i'm just curious how i know it was properly installed and working properly. I tried looking for the log folder/files or in the script in the location mentioned in the OP or other instructions but am not seeing anything. Is there something i need to do? Thanks!

Edit: uninstalled and reinstalled with sqlite on and now seeing files in my log folder. hopefully that doesn't screw anything up for me!)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DaKrampi:
I don't see any logging related changes from 1.3 to 1.4.

What I see is:

Initial wait time of the script was increased from 45s to 65s.

For Pixel 1 discard_max_bytes was removed and settings for io_poll, nr_requests, write_cache added

Uninstall script was replaced by a simple script which just deletes the .sh files from /data/adb/service.d/

Version information of the magisk module was fixed from 1.0 to 1.4

I don't see any fixes related to naming from 1.4 to 1.5. All I see are changes to the device settings in common/marlin/03KingKernel.sh, which is only relevant if you use KingKernel on Pixel 1.

Inside Magisk Manager the module is reported as installed, but with 1.3, 1.4 and 1.5 the actual BlackenedMod script does not get installed at all on Pixel 2 and Pixel 3 devices. The problem I reported for 1.3 regarding the wrong file name still exists in 1.4 and 1.5. There is also an error message in the install log, which is created in /sdcard and that points to the problem: common/bluecross/02blackenedmod.sh needs to be renamed to common/bluecross/02BlackenedMod.sh inside the zip and for Pixel 2 probably also common/wahoo/02blackenedmod.sh to common/wahoo/02BlackenedMod.sh.

If the script is installed correctly, then you will have the file 02BlackenedMod.sh in /data/adb/service.d, also the log file, which is created by the version of the script coming with these installers, is called logs/blackenedmodlog. The script has a delay of 65s (v1.5) at the beginning, so after you restart your device, you need to wait this time until you see the log file. Another 25s later you get additional output in the file.

Regarding the other log files: they are created by a script called Zipalign_sqlite.sh, which gets installed to /data/adb/service.d if you choose the "Sqlite Tweaks" during installation.

This script has three parts:

auto zipalign: This does basically nothing on my device, because it searches for *.apk files in /data/app, but for me there are only folders in there (the script does not search inside those folders). Also I don't have a zipalign executable on my device, which seems to be required for the script.

SQlite vacuum and reindex: calls sqlite3 vacuum and reindex command on every *.db file it can find in /data (so all database files of all apps). Throws a lot of errors on my device. Maybe because the script installs sqlite3 binary without executable flag, so this cannot be used at all.

"Junk Cleaner": unconditionally deletes *.apk, *.tmp, *.log, *.txt and some other stuff from various locations in /cache and /data. Cannot tell, if this is safe.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Daisymae:
If it doesn't install the blackened Mod script why even install the module? Why is it even called Blackened mode module?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
I just installed over previous releases. Derp. My previous post was totally incorrect.

It doesn't install for all the reasons listed in your very detailed explanation.