Database Develop

[SCRIPT] [GUIDE] Google Play Services Battery Drain Fix/Workaround

Anyone's Google Play Services update recently? If you're suddenly experiencing dreadful battery life due to Google Play Services (see pic below) then this fix might be right for you. ​
Background: Recently, an update to Google Play Services (ver. 7.0.97) was released and reports flooded the internet with complaints of battery life issues. People had battery graphs similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also experienced this issue. After checking my frequency tables in my kernel tweaker, I noticed that my phone was NEVER going into Deep Sleep, and, instead, was sitting at 300mhz even when the screen was off. After some Googling and reading some comments on GitHub, it seemed apparent that the problem was one Service in particular "SystemUpdateService".
The Problem: Without going into much detail SystemUpdateService is basically Google's OTA update service, and when it detects that your phone need and update while running a Custom ROM, it fails and re-runs this check over and over again. It's this wakelock that drains your battery.
The Solution: Enabling the service. You read that correctly. For whatever reason, enabling the service actually prevents the wakelock from occurring. I, along with a few testers, have been using our phones for hours now after having run the script and the wakelock and battery drain is completely gone.
Method #1: init.d Script
For those of you with custom ROMs that support init.d scripts, simply unzip and place this script in the /etc/init.d folder (as root) and set permissions to 755. The service becomes disabled again as soon as the phone reboots. We place this script in the init.d folder so the script runs automatically every time the phone boots. If your Custom ROM does NOT support init.d scripts skip over to Method #2 or 3.
DOWNLOAD SCRIPT HERE: View attachment fixUpdateService.zip
Permissions Screenshot:
The source code to this script (Edited slightly, Credit to Oreganoian on Reddit):
Code:
echo "Disabling SystemUpdateService Battery Drain"
su -c pm enable com.google.android.gms/.update.SystemUpdateActivity
su -c pm enable com.google.android.gms/.update.SystemUpdateService
su -c pm enable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
su -c pm enable com.google.android.gms/.update.SystemUpdateService$Receiver
su -c pm enable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
su -c pm enable com.google.android.gsf/.update.SystemUpdateActivity
su -c pm enable com.google.android.gsf/.update.SystemUpdatePanoActivity
su -c pm enable com.google.android.gsf/.update.SystemUpdateService
su -c pm enable com.google.android.gsf/.update.SystemUpdateService$Receiver
su -c pm enable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
echo "Script Execution Successful"
Method #2: Manually Running the Script
This method works best if you like working in the terminal or file explorer. Or if you would rather just do things yourself. Place the script above in the /etc/init.d directory and set permissions to 755. This time, however, you must run the script yourself EVERY TIME THE PHONE BOOTS. You can do this by using your file explorer, if it supports executing scripts (see output below) or running the script via Terminal.
Terminal: Run this command as root (type "su" and hit enter):
Code:
./etc/init.d/fixUpdateService.sh
File Explorer: I personally use FX (File Explorer), which is a wonderful app by the way, so the output in the screenshot below may be styled different but generally should appear the same:
Method #3: Enabling SystemUpdateService via App
Now, if you're a no frills kinda person, or just don't feel comfortable rummaging around in your filesystem or terminal, there is an app you can download called Disable Service which lets you do the same thing, just with a nice GUI. YOU MUST DO THIS EVERY TIME YOU REBOOT YOUR PHONE.
Steps:
Once installed, launch the app.
Then click the "System" tab on the top right.
Scroll down and select "Google Play services"
Scroll down to "SystemUpdateService" and CHECK the box.
Done!
There you have it! Hope this helps!

Great!
Method 1 doesn't work on hammerheadcaf 20150318 but Method 3 is working like a charm and the battery drain issue seems to be gone!
And CyanogenMod is going to deal with this issue before long:
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/

Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...

blackzigong said:
Great!
Method 1 doesn't work on hammerheadcaf 20150318 but Method 3 is working like a charm and the battery drain issue seems to be gone!
And CyanogenMod is going to deal with this issue before long:
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/
Click to expand...
Click to collapse
Interesting, I'll try to see if I can edit the script to get it to work right. Make sure you enable the service with that app every time you reboot your phone.
Also, I've been reading those CyanogenMod discussions. Very interesting. Hopefully they tackle the issue soon and the solution makes its way into other ROMs
Kc_Nirvana said:
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
Click to expand...
Click to collapse
As far as I know, this bug only affects custom ROMs.

Method 1 didn't work but method 2 and 3 worked. I believe the permissions for the script
should be 755 instead of 744.
Update : changing permissions didn't help either.

755 or 744? Screenshot shows 744 but instructions say 755. Assuming 744 is correct.

soundneedle said:
755 or 744? Screenshot shows 744 but instructions say 755. Assuming 744 is correct.
Click to expand...
Click to collapse
Permissions for init.d scripts should;d be 755. I'll update the picture to reflect that. Thank you for pointing that out.

Kc_Nirvana said:
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
Click to expand...
Click to collapse
I'm experiencing the battery drain with stock HTC sense on my M8 and GP services 7.0.97. The battery usage is very high for GP services (e.g. 38% for screen off!) and the "awake" bar shows the phone awake even during periods of low usage--too many awake intervals.

Will init.d scripts work on CM11s?

CM fixed this a couple days ago with 2 commits. Hopefully all the ROM teams will incorporate it into their builds.
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/

AndrasLOHF said:
CM fixed this a couple days ago with 2 commits. Hopefully all the ROM teams will incorporate it into their builds.
Click to expand...
Click to collapse
CM11s may not get another update though. I can confirm that the shell script doesn't work at startup on CM11S.
Edit: sorry didnt realise this was posted in the Nexus 5 section

Does this also effect cm11s?

Pretty important to add that for that 3rd Method to work you also have to enable that same SystemUpdateService in Google Services Framework. (In addition to enabling it in Google Play Services).
At least, that's what I've read on other posts/Google+ pages. I'm trying it now so do this at your own risk =)

Thanks for the script. Works for me, but only manually. I can't get it to work in the init.d at startup. It's in the folder, permissions 755. I'm not that into scripts - anyone who got it working mind for some tips?

humba80 said:
Thanks for the script. Works for me, but only manually. I can't get it to work in the init.d at startup. It's in the folder, permissions 755. I'm not that into scripts - anyone who got it working mind for some tips?
Click to expand...
Click to collapse
Your ROM may not support init.d. Mine doesn't and so I'm using tasker to run the script at boot.

Sandman-007 said:
Your ROM may not support init.d. Mine doesn't and so I'm using tasker to run the script at boot.
Click to expand...
Click to collapse
Tasker! Didn't think of it. Thank you!

Script works for me, but it doesn't solve battery drain: I have to use privacy guard to remove both keep awake and wake up...

Why you try these hard to stop the Systemupdate Wakelock??
See my guide here.Its simple as you like.No scripts included:http://forum.xda-developers.com/showthread.php?t=3060548
This is a permanent fix.No need to redo after reboots

vaisakh7 said:
Why you try these hard to stop the Systemupdate Wakelock??
See my guide here.Its simple as you like.No scripts included:http://forum.xda-developers.com/showthread.php?t=3060548
This is a permanent fix.No need to redo after reboots
Click to expand...
Click to collapse
Yup, but checking after the script mod, only keep awake permission was denied and I still got more than 8000 wake locks

gpvecchi said:
Yup, but checking after the script mod, only keep awake permission was denied and I still got more than 8000 wake locks
Click to expand...
Click to collapse
Did you try my fix?
I've attached screenshots there.
Tapped from my furious ZR

Magisk mount and system-less details ?

hi
after searching about Magisk mount details, i need more info about it. Github document is obscure .
i work in low level customization in android and need some feature like system-less in Magisk.
i want to know how Magisk use overly mount and how create it.
why when create file in system folder in module, that not exist in real system partition , it mount all thing from real system partition.
@topjohnwu
Thank you for your great work. If it's possible to give a more professional description of this

no any idea ?

surbiks said:
hi
after searching about Magisk mount details, i need more info about it. Github document is obscure .
i work in low level customization in android and need some feature like system-less in Magisk.
i want to know how Magisk use overly mount and how create it.
why when create file in system folder in module, that not exist in real system partition , it mount all thing from real system partition.
@topjohnwu
Thank you for your great work. If it's possible to give a more professional description of this
Click to expand...
Click to collapse
1) First of all, when a module adds a new file, the first most leaf directory present in the real partition needs to be over-layed by tmpfs, because the new file appearing is coming from that dir, if we don't overlay the dir, we won't know where the file actually exists, and if that exists in the directory we over-layed, the overlay will make the file appear in real system, while the file will actually be in the magisk.img, I'm not a native English speaker, so forgive any bad English.
2) If you need to know how Magic Mount works, you should browse through this source module, all of the Magic Mounting is done in the post-fs-data boot stage, which triggers the void post_fs_data(int client) function, follow the control flow from there on and you will know how that actually works.
*) If you don't understand the "C" language, quote me back with actually what you're trying to accomplish, so that I can help you better.

anybody know how to magisk mount system and data to mmc1p1 and mmc1p2?

[Deleted]

[ROM][UNOFFICIAL][11][R]LineageOS 18.1 for z5c (suzuran)

Hi all:
Here is a LineageOS 18.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-12
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these command line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 11 (R)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.6.2!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
Camera (with the restriction to 8 MP); both built-in camera (Snap) and 3-rd party camera apps.
Camera2 may be a little bit laggy, please use 3-rd party camera app instead; for example OpenCamera. If you're running into errors, please report.
Enforced SELinux support
Fingerprint
FM-Radio (maybe it needs a few restarts before it's working)
GApps (MindTheGApps 11 arm64)
German app AusweisApp2
GPS
Headset
Hotspot
LiveDisplay
Location services
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
SafetyNet test passed successfully
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Camera focus at low distances.
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.

If you want to remove apps, that are available in much better variants (or that you don't need ), enter these lines one by one in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm -rf /system/product/app/Email
rm -rf /system/product/app/Exchange2
rm -rf /system/product/app/Jelly
rm -rf /system/product/app/Recorder
rm /system/product/priv-app/Eleven/Eleven.apk
rm /system/system_ext/priv-app/Gallery2/Gallery2.apk
"Email" is the built-in E-Mail app, I've replaced it with K-9 Mail
"Jelly" is the built-in browser, I've replaced it with Firefox
"Eleven" is the built-in music-app, I've replaced it with poweramp
"Gallery2" is the built-in picture gallery, I've replaced it with simple gallery pro
Don't forget to reboot!

Hello,
Thanks for updating the ROM!
The performance is about the same (maybe a bit faster), and everything works OK.
However hotspot is still not working for me.

litelinux said:
However hotspot is still not working for me.
Click to expand...
Click to collapse
Oh, I'm sorry, I haven't answered your post in the los18 thread.
I'll take a look at it asap.

I'm using this ROM since some hours now and I have to say, that it's working very good. Better that expected. The device is not getting warm (or hot) and the battery comsumption is very low.
I'll take a closer look at this for some days now.
If the overall performance is convincing, I will delete the "BETA" status...

Is the "Recent Apps" button in the nav bar working?
I just installed this rom, but that button is not working.
Maybe app switcher is missing.

esrevinu said:
Is the "Recent Apps" button in the nav bar working?
I just installed this rom, but that button is not working.
Maybe app switcher is missing.
Click to expand...
Click to collapse
Working for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

(Posted on accident, please delete)

@litelinux Thank you for the answer.
I had installed NikGapps full version. It seems that some gapps made that trouble. With NikGapps core, I can use "Recent Apps" button.
But, even NikGapps core version seems to cause unexpected reboots if micro SD card is set as phone storage(adopted storage), not potable storage.
And, is it normal that the fingerprint reader works when the screen is off?

Hello,
Animations are not as smooth as in Android 10, such as:
Opening/closing recents
Notification panel
Background grayout of popup boxes
Horizontal scrolling
Not sure what the problem is...
Sorry for repeating this but I really hope it would be solved.

esrevinu said:
And, is it normal that the fingerprint reader works when the screen is off?
Click to expand...
Click to collapse
I can't confirm that at my device.

litelinux said:
Animations are not as smooth as in Android 10
Click to expand...
Click to collapse
Maybe because it's still in development state? At my device, for example, the fingerprint reader is not working when the device had been in deep sleep mode for a longer time. Then I have to unlock it by using the "normal" swipe...

esrevinu said:
And, is it normal that the fingerprint reader works when the screen is off?
Click to expand...
Click to collapse
Berni-0815 said:
At my device, for example, the fingerprint reader is not working when the device had been in deep sleep mode for a longer time. Then I have to unlock it by using the "normal" swipe...
Click to expand...
Click to collapse
Both are present on my device.

litelinux said:
Both are present on my device.
Click to expand...
Click to collapse
That's right. Something must have been messed up! I have to investigate it more.

Berni-0815 said:
That's right. Something must have been messed up! I have to investigate it more.
Click to expand...
Click to collapse
You need to cherrypick this commit
Keyguard: Allow disabling fingerprint wake-and-unlock · LineageOS/[email protected]
* When the fingerprint sensor is embedded in the power key, wake-and-unlock is total chaos. Add an option to disable it. * The default behavior is unchanged. Change-Id: I50c0a857daba92c17470d...
github.com

Hello,
Thanks for the ROM,
I installed this version, it works fine at the moment.
Indeed, the photo lag application but by installing open camera it's OK.
On the other hand, the resolution of the camera is at the maximum at 8.3MP.
You also have this resolution blocked?
With lineage OS 14 I was at 23MP

esrevinu said:
You need to cherrypick this commit
Click to expand...
Click to collapse
Thanks. I've already seen that there have been made changes in that files. But unfortunately there have been made so much changes that a simple cherry-pick is not possible! I've tried to manually change these files and I'm hoping, it works.
I will report....

FRFaucigny said:
On the other hand, the resolution of the camera is at the maximum at 8.3MP.
You also have this resolution blocked?
With lineage OS 14 I was at 23MP
Click to expand...
Click to collapse
I've blocked nothing! AFAIK the maximum resolution of the built-in sensor is 8,3MP and the resolution of 23MP is realized by software upscaling. Try to take a photo of the same object with 8,3MP and 23MP and compare them. I for myself have never seen any difference.
So, for me 8,3MP is fine..

Bummer. I was hoping root install for F-Droid would be fix by now.

You're right! I haven't tested if the so called "FDroidPrivilegedExtension" can be used in this version. I'll try it next.
Is that what you're meaning?

Have others found that mount-master works under Android 11?

Hi there,
I recently got my OnePlus 9, and am converting the scripts I use to run luks to the new phone. Everything seems fine, losetup creates the node and loads the file as a block device, dmcrypt unlocks it, mount /dev/mapper/<partition-name> mounts it fine, but it's only visible as root (the user that mounted it). I've verified that the Magisk (22100) setting is to use the globalname space and just to make certain I've explicitly run mount within "su -mm", but regardless can only see the unmounted directory (verified by containing a file that isn't present within the encrypted partition).
Dmesg doesn't mention anything about the mount namespace (but I don't know that it would), so I wanted to verify that others have managed to use the su -mm/-M/--mount-master option successfully under android 11 (or, I guess more specifically Oxygen OS 11.2.4.4)?
As a side-note, this same script has been tested and worked with a OnePlus 7 on android 10 with magisk set to use globalnamespaces. Happy to provide further information or run tests if it'll help to get to the bottom of what's going on...
Thanks!

This also occurs in Magisk 23000.
I've discovered this thread:
https://twitter.com/i/web/status/1279508461370269696, however, I'm calling `su -mm` and I've set the mount namespace mode to "All root sessions use the global mount namespace", so I don't think that's relevant.
As best I can tell, once root mounts a directory, any other process running as root can see it (because of the global mount namespace), but normal processes can't access it. This seems to be due to mount namespaces, so the device now needs to be mounted with `-o shared` or `--make-shared`, but unfortunately that gives an unhelpful "invalid argument" message. Trying to change it with `-o remount` seems to succeed but the change to shared appears to be ignored.
When running the command, I get a single log entry that might provide more details:
05-15 03:02:54.184 30090 30090 I su : type=1400 audit(0.0:1523): avc: denied { ioctl } for path="/dev/pts/3" dev="devpts" ino=6 ioctlcmd=0x5404 scontext=u:r:magisk:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file permissive=1
But I can't quite tell what's causing that to be stopped. I don't know whether it's related or not and whether I should be digging into audit/selinux permissions, or figuring out what the ioctlcmd is. Any help would be much appreciated...

Well, I've confirmed that any app that launches root can see the mountpoint, but otherwise can't. The `-o shared` option seems to cause either a parsing error, or at least no success with both the native toybox implementation and with busybox.
I found this excellent article suggesting that `nsenter -t 1 -m <shell-command>` should get me into the pid 1 namespace, which should then be inherited by everyone. I can get in there, and carry out the mount, but I can only get apps to see the mount point if I enter their specific pid namespace and mount the directory I want. This happens if root namespace is both global or inherited (I haven't tried isolated, but I can't see why that would work?). So essentially, even though I seem to be doing all the right things, I'm getting nowhere. Clearly it's possible to mount things so that everyone can see them (because magisk does it when it bind mounts various programs from modules), so could anyone that knows the internals of magisk better shed some light on what might be going wrong and how I could get global mounting working properly? I tried the pid for zygote64 as well (which seemed to be part of `main` which was at the top of the process tree), but again it wasn't seen by the test program.
Any help would be much appreciated...

[Kernel]Kali-NetHunter kernel Pixel 3a and 3a XL sargo/bonito[Kernel]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WITH GREAT POWER COMES GREAT RESPONSIBILITY............
Please use kernel responsibly and respect the rights of others including and especially privacy!
The mad tech clown is back with another Kernel for all of the Kali-linux-nethunter users wanting the portability of kali-nethunter for their Pixel 3a and 3a XL devices codenamed sargo and bonito.
hahahahahahahahahahahahahahahahahahaha
Warning your warranty is now void. Do this at your own risk. The mad clown is in no way responsible for the chaos, worldwide disease, nuclear destruction, laughing fish, costumed caped crusaders or damage caused to your device by performing the steps involved.
hahahahahahahahahahahahahahahahahahaha
I now bring you the
Mad-Kali-MaxHunter kernel
Features :
compiled with clang 8 and linaro aarch64 5.5
-optimized for performance and battery life
-Klapse color control with backlight dimmer and high brightness mode
-Boeffla wakelock blocker
-vibration control
-sound control
-the usual I/O schedulars like zen fiops deadline and such
-adreno boost
-fsync switch
-wireguard support
-HID support
-previously disabled otg is now enabled
-full usb support including.........
---serial
---ACM
---OBEX
---NCM
---ECM
---RNDIS
---EEM
---mass storage
---MTP and PTP
---MIDI
---DIAG
-ntfs
-devtmpfs and mount
-full bluetooth support
-Wifi injection
-dvb / sdr support
- use your own modules
-systemd/upstart support for dual boot
-LZMA compression to keep twrp
-binfmt_misc -------- you can do alot of cool stuff with this enabled like use exe programs ie wine and for you compilers you can effectively change the architecture of your device in a chroot to use qemu properly. what does that really mean you can compile as x86_64 on your aarch64 device like building your own kernel.
and every thing you need for your kali hacking excursions packed inside this kernel
source available at
P
https://github.com/Duhjoker/android_kernel_google_bonito/tree/Mad-Kali-MaxHunter-P3A-P
Q
https://github.com/Duhjoker/android_kernel_google_bonito/tree/Mad-Kali-MaxHunter-P3A-Q
R
https://github.com/Duhjoker/android_kernel_google_bonito/tree/Mad-Kali-MaxHunter-P3A-R
S
https://github.com/Duhjoker/android_kernel_google_bonito/tree/Mad-Kali-Maxhunter-P3A-S
Thanks to Lineage, ElementalX, Dirty Unicorns and beidl aka fredldotme.
Please use this kernel responsibly and mind the rights of others including and especially privacy.
To install flash Mad-Kali-MaxHunter-kernel.zip from twrp. also included are some libs and binaries and other such materials needed to get a fully working version of Kali-nethunter on your pixel 3A and 3A XL device. just unzip the kali-hacks.zip place in proper directories using twrp and give proper permissions.
Download Kali store install the chroot manager nethunter terminal and kex manager install your chroot and happy hunting
Once again and this is no laughing matter. please use this kernel responsibly and mind the rights of all people including and especially privacy.
The mad clown is not responsible for any thing you might do in good or bad concious
Download from here or my personal gihub repository to hold the prebuilt kernels in an anykernel3 zip. i update from time to time so check the dates on the zips.
GitHub - Duhjoker/Mad-Kali-MaxHunter-kernel-prebuilt: repository to hold prebuilt kali nethunter kernel
repository to hold prebuilt kali nethunter kernel. Contribute to Duhjoker/Mad-Kali-MaxHunter-kernel-prebuilt development by creating an account on GitHub.
github.com
COMING SOON
KALI-TOUCH! its like ubuntu touch but using a kali-linux root file system instead of ubuntu.
For pixel 3a sargo and bonito roms and more check out my mega!
16.68 GB folder on MEGA
74 files and 20 subfolders
mega.nz

change log:
Pie:::::::
10/9/21
improved systemd
10/10/21
now with built in wlan
Kernel can be used with any stock or custom rom
Q:::::::::
10/9/21
Brand new off the compiler
features::::::
same as Pie plus built in wlan.ko
Kernel can be used with any stock or custom rom
R::::::::::::
10/14/21
features::::::::::
same as above
S:::::::::::::
10/26/21
features:::::::::::
same as above
11/21/20
link time optimisation enabled
fix system warning on startup

what version its android 12 ??? thanks
regards

Can the pixel-3a deauth WPA networks?

the kernel versions are labled according thier corresponding letter in alphabetical order. p is 9, q is 10, r is 11 and 12 is s.
yes the pixel 3 is capable of de-auth of wpa networks although it will take longer than it would on a pc. if the tools are available the device can use them

all updated kernels will be found on my github page from here on out.
major update now for A12-S and A11-R kernels. the system warning at startup has been fixed. enjoy

can you make one for pixel 4a. i tried but failed

@Duhjoker
Ayy first off thanks for putting the kernal together! After tinkering with trying to get nethunter functional on my pixel 3a for about 3 days I figured it was time to reach out haha.
I did follow your instructions the best I could multiple ways. I now have re flashed lineage os many times and followed the guide from their site (https://wiki.lineageos.org/devices/sargo/install). I am running the p3a R kernal since I have android 11 running on the pixel. The kernal seems to be functional as it shows up as expected when looking inside of the nethunter app. I have magik v23 installed with root access and all is fine there. I did run into a hicups with the terminal throwing the error " "Required key not available"." when trying to run any commands from zsh from the kali terminal app.
I was able to resolve this problem by doing the following
SSH Bash: Required key not available
Hi guys, When I connect to my Nethunter through SSH from my laptop, (tried both root and kali as user). It seems the SSH bash environment is limited. with most commands I type in, the SSH terminal returns: -Bash: /usr/bin/TheCommandIJustTyped Required key not available I looked everywhere...
forums.kali.org
I've been able to solve the problem commenting the line:
#session optional pam_keyinit.so force revoke
in /etc/pam.d/sshd and /etc.pam.d/su-l files.
After restart chroot environment, write operations from chroot to Android encrypted data partition is working.
Click to expand...
Click to collapse
So I can get to a point where It appears that I have a "fully functional" nethunter app / terminal the problem arises when I actually try using it. I cannot seem to get any of the hardware functional. For example bluetooth interfaces listed under "bluetooth arsenal" show up as none. When trying to run the wlan1 or wlan0 in monitor mode it is not functional. I am not even able to scan for SSIDs of networks broadcasting.
I know you stated the following.
also included are some libs and binaries and other such materials needed to get a fully working version of Kali-nethunter on your pixel 3A and 3A XL device. just unzip the kali-hacks.zip place in proper directories using twrp and give proper permissions.
Click to expand...
Click to collapse
After many attempts and learning how the android filesystem / chroot are laid out I managed to copy the files from "kali-hacks.zip" into the "/system" directory. This made the most sense to me after poking around on the phone and online. This leads to my first question. Is this the correct file path to copy the files to? I applied a chroot 755 on the files and then ran "mount -o rw,remount /" to make root writable and simply copied all of the files over by doing "mv * /system" from the kali-hacks directory. This was all done as the root user from TWRP. I would assume if I did this correctly everything would be functional hardware wise. So either I am going about it all silly like or something is funky.
My second question is the following. Did you do anything to make sure that your file system is NOT encrypted? I know thats why zsh was giving me there error "Required key not available". Therefore, assuming that I did infact copy the kali_hack.zip files correctly I feel this may be the cause of my woes. When checking the kali nethunter documentation it does list that you need to make the system non-encrypted.
[Kernel]Kali-NetHunter kernel Pixel 3a and 3a XL sargo/bonito[Kernel]
WITH GREAT POWER COMES GREAT RESPONSIBILITY............ Please use kernel responsibly and respect the rights of others including and especially privacy! The mad tech clown is back with another Kernel for all of the Kali-linux-nethunter users...
forum.xda-developers.com
6. Flashing Universal DM-Verity & ForceEncrypt Disabler​IMPORTANT NOTE for Android 9, 10, & 11 users: Please ensure that you flash the Universal DM-Verity, ForceEncrypt Disabler and format the data partition prior to installing NetHunter. Magisk does not support user context changes on encrypted data partitions, which leads to errors when connecting to the Kali rootfs via ssh (i.e. “Required key not available”) if the data partition is encrypted.
Click to expand...
Click to collapse
Although funny enough when following the official docs the link from the site redirects you to "https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/" which then sends you to "https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt" which is depreciated and last updated 14 months ago... I still tried anyways out of desperation with a fresh install of lineage os using the method he provided to get a non encrypted filesystem. The outcome was not successful. (instructions I followed can be found in the XDA link above).
Thanks in advance if you get around to reading this. I have bashed my head against this for probably 20ish hours now over the last couple of days and exhausted all of my ideas. Any help is appreciated.
Recap on Questions (TL;DR)
1. How / at what time during install / where should I be copying the files in "kali-hacks.zip" to?
2. Did you do anything to make your file system not encrypted as recommended per the kali nethunter docs? If so how did you manage to do so?

The kali-hacks should be unzipped and copied to /syatem and i usually install them after getting the apks and rootfs installed.
As far as encrypted.... i do not know what you mean by that. Its best to let the gui app download the roots from thier server during install.

create for pixel 3 pls

Has anyone made this to use on pixel 3 XL yet?

hey guys i just updated the kernel to 12.1.

attached is a Mad-Kali-MaxHunter kernel for blueline and crosshatch pixel 3 (xl) only. let me know what you think

Super stoked for Kali-Touch! lmk if you need a tester - I've got spare phones.

PSA -
For anyone running the newest linage OS (19.1) on the pixel 3a and are struggling to get the nethunter app to boot properly after providing it root perms using magisk. Try the following, it worked for me.
get the app to boot properly you need to do the following
The issue was of Permissions - to solve the issue run the following commands in AndroidSU
Code:
pm grant com.offsec.nethunter android.permission.ACCESS_FINE_LOCATION
pm grant com.offsec.nethunter android.permission.ACCESS_COARSE_LOCATION
pm grant com.offsec.nethunter android.permission.READ_EXTERNAL_STORAGE
pm grant com.offsec.nethunter android.permission.WRITE_EXTERNAL_STORAGE
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_SU
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH
pm grant com.offsec.nethunter com.offsec.nhterm.permission.RUN_SCRIPT_NH_LOGIN
NetHunter not open crashed (#306) · Issues · Kali Linux / NetHunter / Apps / kali-nethunter-app · GitLab
i have android version 11 on my phone and i can't use netuntar, its crashed every time
gitlab.com

Duhjoker said:
please make it available for pixel 4a (sunfish)
Click to expand...
Click to collapse

Hey guys, I'm trying to make it work but I'm out of luck
this is what I did:
1. I unlocked the phone and installed twrp recovery
2. I flashed the "Mad-Kali-MaxHunter-P3A-S.zip" using twrp
3. I used twrp to install magisk
4. Installed "KaliNethunter-v8.2(22).zip" using magisk modules
5. after reboot after updating the Nethunter app from the Nethunter Marketplace and giving it all the permissions that it requested it gives this error in the notification:
```
Nethunter: Startup
Root: OK.
BusyBox: OK.
Chroot: Chroot is not yet installed.
Make sure the above requirements are met.
```
and the Nethunter app keeps crashing as soon as it opens....

Possible to build some modules for this card?
GitHub - aircrack-ng/rtl8812au: RTL8812AU/21AU and RTL8814AU driver with monitor mode and frame injection
RTL8812AU/21AU and RTL8814AU driver with monitor mode and frame injection - GitHub - aircrack-ng/rtl8812au: RTL8812AU/21AU and RTL8814AU driver with monitor mode and frame injection
github.com