Database Develop

[Source] add kernel "name" to version information

Hi again everyone,
So this is kind of a continuation of my earlier thread here: http://forum.xda-developers.com/showthread.php?t=977211
Cmenard and I were talking earlier about adding the individual developers custom kernel "names" into that display string, and thanks to his direction, now we can!
Its kind of "hack-ish" right now, piggybacking on either the version# or the individual build #XX string in order to actually display in Settings.apk, and so it makes the string look nasty and unformatted. Sadly though, even though I've spent 3-4 hours learning rudimentary regex syntax to understand the code used, I don't feel comfortable enough yet to modify it.
(If anyone here is a REGEX master and can tell me how to build the string and insert it into the original AOSP regex string, then I'll update both this thread and my Settings.apk thread accordingly.)
Here's the AOSP regex code for anyone that's a master and wants to help me out, my best guess would be to group the third line (group 1) a second time, and after it finds white space, then add something to look for anything other than a digit (assuming devs always end their name with a numerical version number) maybe something like: ([^\\d]+[\\d]*)\\s+
Code:
"\\w+\\s+" + /* ignore: Linux */
"\\w+\\s+" + /* ignore: version */
"([^\\s]+)\\s+" + /* group 1: 2.6.22-omap1 */
"\\(([^\\[email protected]]+(?:@[^\\s.]+)?)[^)]*\\)\\s+" + /* group 2: ([email protected]) */
"\\((?:[^(]*\\([^)]*\\))?[^)]*\\)\\s+" + /* ignore: (gcc ..) */
"([^\\s]+)\\s+" + /* group 3: #26 */
"(?:PREEMPT\\s+)?" + /* ignore: PREEMPT (optional) */
"(.+)"; /* group 4: date */
Ok, so source for kernel developers:
In the makefile:
First, at the very top, change the name to whatever you want, though if you want it appended to the kernel version (for instance 2.6.32.9-XXXXXkernelXXXXX) then you need to make sure you omit ANY whitespace/
Code:
NAME = Categorically Worthless v4
or
NAME = CategoricallyWorthless4
then in "define filechk_version.h"
Change the line:
Code:
(echo \#define LINUX_VERSION_CODE $(shell \
to the following
Code:
(echo \#define LINUX_CODE_NAME \"$(NAME)\"; \
echo \#define LINUX_VERSION_CODE $(shell \
And second, in /init/version.c we need to display the LINUX_CODE_NAME somewhere, and this depends on your naming convention in the makefile; did you use whitespace or not?
If you DIDN'T use whitespace, the cleanest formatting is to append to the version number string:
in "const char linux_proc_banner[] ="
Change the first line
Code:
"%s version %s"
to the following
Code:
"%s version %s" "-" LINUX_CODE_NAME
If you DID use whitespace in your kernel name, then instead change the last line
Code:
" (" LINUX_COMPILER ") %s\n";
into two lines that read
Code:
" (" LINUX_COMPILER ") "
LINUX_CODE_NAME " %s\n";
If you move the position of the LINUX_CODE_NAME in proc_banner in version.c, anywhere else, or if your kernel name isn't formatted properly (without whitespace for the first version) then it breaks the entire display, and Settings.apk will just display "Unavailable."
And the result (coupled with my settings.apk mod I posted earlier) will display this:
left image is the first method (no white space in kernel "name") right image the second method
{
"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"
}
So there you go, an easy way for users to know what kernel version they have installed.
I hope someone finds this useful, and be sure to also thank cmenard for his help in this.
Cheers everyone, =)

Updated the OP really quick.
I spent some time learning basic regex syntax, and found another hack-ish method, and added it to the op.
Cheers, =)

How much time did you spend on this?
It's marginally cleaner than just using CONFIG_LOCALVERSION="-Honity14-bfs"

morfic said:
How much time did you spend on this?
It's marginally cleaner than just using CONFIG_LOCALVERSION="-Honity14-bfs"
Click to expand...
Click to collapse
Apparently both too much and not enough time since I failed to find the CONFIG_LOCAL_VERSION option you mention.
Oh well, not like I was doing anything productive/useful yesterday anyway.
Cheers, =)

morfic said:
How much time did you spend on this?
It's marginally cleaner than just using CONFIG_LOCALVERSION="-Honity14-bfs"
Click to expand...
Click to collapse
s0niqu3 said:
Apparently both too much and not enough time since I failed to find the CONFIG_LOCAL_VERSION option you mention.
Oh well, not like I was doing anything productive/useful yesterday anyway.
Cheers, =)
Click to expand...
Click to collapse
Indeed, i agree with Morfic, it is cleaner.
Well, regardless if you did or didn't do anything productive, this Jocelyn, is very PRODUCTIVE.
So how did you figure this out? I was looking at the source, is there a way to eliminate the build number, (ex. [email protected] #21) that #21, can we get rid of that?

Why not just change the version.c in the init folder only? using that will show anything you want without the name of the machine its been compiled on. That's typical how I set all my kernels like this http://twitpic.com/46apg2

If my regex and assumptions are correct, the you should be able to drop that number by eliminating the parentheses around the group three regex.
Ie change
([^\\s]+)\\s+
To
[^\\s]+\\s+
That should make it ignore the number. I an making the assumption that stuff not between parentheses gets ignored, and thus resulting in the mess that ignores the (gcc...)

[REF] Kernel source code repository for Galaxy S III

Hi everyone.
As you all know, Samsung distributes source code as tarballs which isn't the best way to redistribute kernel source code
git is the best modern way to work with Linux Kernel sources, designed by Linus himself in this purpose.
So, i made an organization on github for that.
https://github.com/sgs3
And yea, that means source code has been released, head on to http://opensource.samsung.com/
Kernel Sources :
https://github.com/sgs3/GT-I9300_Kernel
Branches :
master :- branch you should use(for developers), will contain fixes and more in the future (currently identical to stock_update4)
stock :- Kernel sources from GT-I9300_ICS_Opensource.zip, unmodified
stock_update1 :- Kernel sources from GT-I9300_ICS_Opensource_Update1.zip, unmodified
stock_update4 :- Kernel sources from GT-I9300_ICS_Opensource_Update4.zip, unmodified
If anyone wants to commit any fixes / anything else, fork and shoot a pull request
How to Build :
Get teh sauce:
Code:
git clone git://github.com/sgs3/GT-I9300_Kernel.git
cd GT-I9300_Kernel
git checkout master
Tell it to use our config:
Code:
make ARCH=arm CROSS_COMPILE=/path/to/toolchain m0_00_defconfig
Teh real build:
Code:
make CROSS_COMPILE=/path/to/toolchain
or
Code:
make -j `cat /proc/cpuinfo | grep "^processor" | wc -l` CROSS_COMPILE=/path/to/toolchain
The compiled kernel is arch/arm/boot/zImage

Was about to post this
Will start compiling and have a kernel up and running soon I hope. This time in contrast to the S2, it's time for serious developing.
Here's a direct link to the S3 files: http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-i9300

This is great news guys,
lets hope that we will also have a proper CWM recovery soon.

stickied
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
EDIT: this is the patch in question: http://git.kernel.org/?p=linux/kern...it;h=371a689f64b0da140c3bcd3f55305ffa1c3a58ef. Apparently Sammy took this out again in their sources (according to somebody else, I haven't had time to confirm yet, but I can see the boot partitions do *not* appear on my device), they may have bastardized it further ...

Chainfire said:
stickied
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
Click to expand...
Click to collapse
No CF-Root Kernels for the i9300?

Toss3 said:
No CF-Root Kernels for the i9300?
Click to expand...
Click to collapse
Well it's not needed as much due to the separate recovery, but if there's demand, I'll build CF-Root's... but those are based on Samsung binaries, not source.

Great! I'll go through this when I get the time.

Chainfire said:
Well it's not needed as much due to the separate recovery, but if there's demand, I'll build CF-Root's... but those are based on Samsung binaries, not source.
Click to expand...
Click to collapse
Of course I want a CF kernel

pglmro said:
Of course I want a CF kernel
Click to expand...
Click to collapse
I think everyone of us want a CF-Root-Kernel

Roughnecks said:
I think everyone of us want a CF-Root-Kernel
Click to expand...
Click to collapse
I don't really see the point why we should make that. I have flashed cwm with Odin and then the SuperSu cwm flashable zip available here on xda. Then installed busybox installer from the play store. Much easier to do as letting Cainfire always compile a cf-root kernel for us.
L

great seeing some a class developers here!!
thanks for opening this thread..
and good to know ya'll have a s3 aswell..
grtz!

Great news , hope to see some nice custom kernels soon!

Kernel dev's:
Please share your github if you start then

what?update#1 is already out?
Hope Samsung release a cleaner source this time

sakindia123 said:
what?update#1 is already out?
Hope Samsung release a cleaner source this time
Click to expand...
Click to collapse
Looks like they messed up the first zip, so the quick update
Only change i can see from stock to stock_update1 is the changing of file mode from 0755 to 0644

Samsung releases source code for the Galaxy S III
UPDATE 1 is out.
{
"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"
}

Chainfire said:
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
Click to expand...
Click to collapse
They seem to have hacked it out pretty crudely (certainly the korg patch won't apply cleanly). No device here, can't really test this, but the attached patch should properly allocate any mmc boot partitions.

A couple more patches before I rm
No device here and no idea if I'll ever get one, but I thought I would post couple more cosmetic (yet instrumental) patches for your tree so that my last 15 minutes wouldn't be in vain.
#1: m0_00_defconfig: Run through menuconfig;disable GCC strict checking. Otherwise I get a lot of noise with codesourcery toolchains
#2: Add .gitignore files from korg trees.
Take care

Anyone else get compilation error due to SVN_REV variables in these Makefiles:
drivers/media/video/samsung/mali/Makefile
drivers/media/video/samsung/ump/Makefile
I comment out the lines and replaced them with
Code:
SVN_REV=:0000
I used 0000 because of the comment in the Makefile.
Now, it compiles without error (though untested since I don't own S III)

Nope ... didn't get those errors!

[APK][MOD][Xposed] ResXploit : Theming your android the easiest way!!! No Kidding!!!

This would be my second public-released xposed module...
Original Thread: http://forum.xda-developers.com/showthread.php?t=2400369
I did not expect that my WisdomSky Xploit would be a big hit.
I'm just an Amateur developer who just started delving into android development 3months ago and I didn't expect that much appreciation from my work... XD
But all of these would not be made possible if not because of sir @rovo89 and sir @Tungstwenty and their Xposed Framework, right? That's why I thank them a lot...
REQUIREMENTS
Xposed framework must be pre-installed before installing this.
What does the ResXploit do?
ResXploit has two parts:
the Removable part, terminal
and the main star, engine
The terminal is where you enter the commands(I'll discuss it later). These commands will then be interpreted by the engine and then passed to Xposed framework...
Flow:
TERMINAL >> ENGINE >> XPOSED FRAMEWORK
I have provided a variety of modules:
ResXploit (Terminal + Engine) (RECOMMENDED FOR NEWBIES)
ResXploit Terminal (Terminal Only)
ResXploit Engine (Engine Only)
You might be wondering why I made one which has both terminal and engine... and other two which are separated...
ROM Chefs, Themers and some others would understand directly why...
All the commands are interpreted by the Engine right? so that would mean that once you have entered all the desired commands, the terminal will now end up as useless... so you will just delete so no one can touch the engine...
If you are a ROM Chef or a themer, you can theme all the apps you need to theme using ResXploit and then remove the terminal, so end-user interaction of the engine is prevented after you have released your ROMs to the world.
FOR NEWBIES!
I recommend you to use the ResXploit (Terminal + Engine)...
It is very smart..
I included 99% accurate error-checking system,
line numbering system,
and also Xposed module prioritization(which is first implemented on ResXploit for better module performance).
COMMANDSd
We have five basic commands in the ResXploit, the apk, drawable, string, color, and boolean.
apk - A prerequisite command. This command is very vital whenever you using the ResXploit. This will define the target application by using the package name of the target application. You need to include this before you enter any command or else your command will not know which application is targeted and end up in lost island.
Code:
[B]format[/B]: [I]apk <package name>[/I]
[B]example[/B]: apk com.android.systemui
drawable(also drw) - The most often used command. The command which will change icons/images (png drawables) of an application. You can either overlay the existing image with your favorite color or completely replaced it with a .png image from your sdcard.
Code:
[B]format1[/B]: [I]drawable <target application's drawable name> <image path, no need to include /sdcard> <transparency, 0 to 255>[/I]
[B]example1[/B]: drawable status_background_color my_image/bg.png 255
[B]format2[/B]: [I]drawable <target application's drawable name> <HEX RGB color code> <transparency, 0 to 255>[/I]
[B]example2[/B]: drawable status_background_color #fff00ff 255
string(also str) - This command will change string(text) values of the application. The predefined string values are usually located in res/values/strings.xml of an application, but I guess they are not visible when you view the contents of an application using Archive managers like RootExplorer. But there is a way to identify them. I will include it later.
Code:
[B]format[/B]: [I]string <target application's string value holder name> <replacement string>[/I]
[B]example[/B]: string app_name My App
color(also clr) - This command will change color values of the application. The predefined color values are usually located in res/values/colors.xml of an application, but I guess they are not visible when you view the contents of an application using Archive managers like RootExplorer as well.
Code:
[B]format[/B]: [I]string <target application's color value holder name> <replacement color in HEX RGB Format>[/I]
[B]example[/B]: color holo_background_dark #ffffff
boolean(also bln) - This command will change boolean values of the application. The predefined boolean values are usually located in res/values/bools.xml of an application, but I guess they are not visible when you view the contents of an application using Archive managers like RootExplorer as well.
Code:
[B]format[/B]: [I]string <target application's boolean value holder name> <replacement boolean value, either [B]true[/B] or [B]false[/B] only>[/I]
[B]example[/B]: color allowNumberNotifications true
Some simple examples screenshots:
drawable and string commands in action
{
"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"
}
ResXploit UI screenshots:
If you find my ResXploit module interesting,
Please hit THANKS!!! XD:angel:
Please help me buy a new Android Phone.. Y_Y

Pretty awesome, gonna have to give this a try
Sent from my SPH-L710 using Tapatalk 4

This sounds amazing! are you planning on creating a GUI based frontend?

ReelFiles said:
This sounds amazing! are you planning on creating a GUI based frontend?
Click to expand...
Click to collapse
Maybe not for now.... but if it turns out good in the future, then why not? XD
and also.....
Please refer to the original thread,
this duplicate thread is not updated anymore... XD
the original thread link is mentoned at the very top.....

Interesting, sounds like a concept similar to Ninjamorph.
A couple of quick questions:
Is this able to apply folders or just single png's?
Also do you need extract png's from apks in order to apply or does it extract and apply automatically?
:good:
Edit : just seen the above post referencing other thread, maybe get this removed or locked.

Works perfect on my htc sxl...tnx bro

Any way to replace files in assets directory?

Incredible ... Keep up the good work

[Magisk Debloat Module] Moto G Power Sofia(p)(r)

This is my Moto G Power debloating module. It works on the original ROM. It's still a work in progress, but I've been using it for a while on my Moto G Power 2020 (XT2041-4, US model) and it seems pretty stable. It may work for all Moto G8/G9 as well.
Requirements:
- Root
- Magisk
- Should be flashed only in Magisk (via Modules tab)
Recommendations:
- Make a full backup before installing this module
- Copy the module to your internal storage because if something goes wrong you may have to flash it from inside TWRP
- Since I'm removing YouTube, I suggest installing YouTube Vanced, which removes ads and add some cool features
How to use it:
- Copy the zip module to your internal storage
- Open Magisk
- Go to Modules tab
- Click on 'Install from storage' and find the zip file
- After the installation a reboot button should appear, so click on it and that's it
Troubleshooting:
If you don't like the result, you can open Magisk, go to Modules tab and either disable or remove the module.
If after flashing this module your device gets into boot loop, don't panic. There are at least 2 ways to reverse it without having to factory reset or lose any data.
1- Official way: https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677
2- I find this easier, although it enables all the apps that my module tries to remove: boot into TWRP, install my module and reboot.
What this module does:
It basically uses Magisk to replace a bunch of APKs, RCs and Zips with dummy files (0 kb) so Android cannot load them anymore. This seems the only way to change Android 10 file system because it's read-only. Here's the list of things it removes:
Code:
/system/app/BasicDreams
/system/app/BluetoothMidiService
/system/app/BookmarkProvider
/system/app/Bug2GoStub
/system/app/BuiltInPrintService
/system/app/CarrierDefaultApp
/system/app/com.motorola.android.nativedropboxagent
/system/app/CompanionDeviceManager
/system/app/CtsShimPrebuilt
/system/app/DeskClockGoogle (this is not the clock app!)
/system/app/EasterEgg
/system/app/facebook-appmanager
/system/app/GooglePrintRecommendationService
/system/app/LiveWallpapersPicker
/system/app/MotoAppForecast
/system/app/MotoDolbyV3
/system/app/MotoSignatureApp
/system/app/MotoTimeZoneDataStub
/system/app/PacProcessor
/system/app/PartnerBookmarksProvider
/system/app/PlayAutoInstallConfig
/system/app/PrintSpooler
/system/app/SimAppDialog
/system/app/Traceur
/system/app/WallpaperBackup
/system/app/YTMusic
/system/preinstall/facebook.apk
/system/priv-app/3c_devicemagement-binary
/system/priv-app/3c_notification
/system/priv-app/AmazonAppManager
/system/priv-app/BackupRestoreConfirmation
/system/priv-app/CallLogBackup
/system/priv-app/CtsShimPrivPrebuilt
/system/priv-app/DemoMode
/system/priv-app/DynamicSystemInstallationService
/system/priv-app/EmergencyInfo
/system/priv-app/facebook-installer
/system/priv-app/facebook-services
/system/priv-app/GuideMe
/system/priv-app/InputDevices
/system/priv-app/LMIRescueSecurity
/system/priv-app/LocalTransport
/system/priv-app/ManagedProvisioning
/system/priv-app/MotoHelp
/system/priv-app/MotoSystemServer
/system/priv-app/ONS
/system/priv-app/ProxyHandler
/system/priv-app/SharedStorageBackup
/system/priv-app/TagGoogle
/system/product/app/com.amazon.mShop.android.shopping
/system/product/app/datastatusnotification
/system/product/app/Drive
/system/product/app/Duo
/system/product/app/DynamicDDSService
/system/product/app/embms
/system/product/app/GoogleLocationHistory
/system/product/app/MotoDemoModeFWProxy
/system/product/app/remoteSimLockAuthentication
/system/product/app/remotesimlockservice
/system/product/app/Republic
/system/product/app/talkback
/system/product/app/TimeWeather
/system/product/app/Tycho
/system/product/app/uceShimService
/system/product/app/uimgbaservice
/system/product/app/Videos
/system/product/app/YouTube
/system/product/priv-app/3c_ota
/system/product/priv-app/AMXGlobalContainer
/system/product/priv-app/AndroidAutoStub
/system/product/priv-app/BRApps2
/system/product/priv-app/CarrierConfig
/system/product/priv-app/ConfigUpdater
/system/product/priv-app/CQATest
/system/product/priv-app/daxService
/system/product/priv-app/EasyPrefix
/system/product/priv-app/FilesGoogle
/system/product/priv-app/GoogleFeedback
/system/product/priv-app/GooglePartnerSetup
/system/product/priv-app/GoogleRestore
/system/product/priv-app/HiddenMenu
/system/product/priv-app/ims
/system/product/priv-app/InvisibleNet
/system/product/priv-app/LenovoId
/system/product/priv-app/LifetimeData
/system/product/priv-app/MotoActions
/system/product/priv-app/MotoAppUIRefresh
/system/product/priv-app/MotoCare
/system/product/priv-app/MotoCareInt
/system/product/priv-app/MotoDisplayV6
/system/product/priv-app/myCC
/system/product/priv-app/PAKS
/system/product/priv-app/SlpcSystem
/system/product/priv-app/TelcelContainer
/system/product/priv-app/Turbo
/system/product/priv-app/Velvet
/system/product/priv-app/WallpaperCropper
/system/product/priv-app/Wellbeing
/system/vendor/app/OneApp
/system/vendor/app/SSGTelemetryService/SSGTelemetryService.apk
/system/etc/init/[email protected]
/system/etc/init/[email protected]
/system/etc/init/apexd.rc
/system/etc/init/art_apex_boot_integrity.rc
/system/etc/init/ashmemd.rc
/system/etc/init/atrace.rc
/system/etc/init/audioserver.rc
/system/etc/init/blank_screen.rc
/system/etc/init/bootanim.rc
/system/etc/init/bootstat.rc
/system/etc/init/bpfloader.rc
/system/etc/init/cameraserver.rc
/system/etc/init/[email protected]
/system/etc/init/drmserver.rc
/system/etc/init/dumpstate.rc
/system/etc/init/flags_health_check.rc
/system/etc/init/gatekeeperd.rc
/system/etc/init/gpuservice.rc (scary, but user foobar66 gave the idea)
/system/etc/init/gsid.rc
/system/etc/init/heapprofd.rc
/system/etc/init/hwservicemanager.rc
/system/etc/init/idmap2d.rc
/system/etc/init/incidentd.rc
/system/etc/init/installd.rc
/system/etc/init/iorapd.rc
/system/etc/init/keystore.rc
/system/etc/init/lmkd.rc
/system/etc/init/logd.rc
/system/etc/init/lpdumpd.rc
/system/etc/init/mdnsd.rc
/system/etc/init/mediadrmserver.rc
/system/etc/init/mediaextractor.rc
/system/etc/init/mediametrics.rc
/system/etc/init/mediaserver.rc
/system/etc/init/mtpd.rc
/system/etc/init/netd.rc
/system/etc/init/perfetto.rc
/system/etc/init/perfservice.rc
/system/etc/init/racoon.rc
/system/etc/init/recovery-persist.rc
/system/etc/init/recovery-refresh.rc
/system/etc/init/rss_hwm_reset.rc
/system/etc/init/servicemanager.rc
/system/etc/init/statsd.rc
/system/etc/init/storaged.rc
/system/etc/init/surfaceflinger.rc
/system/etc/init/tombstoned.rc
/system/etc/init/traceur.rc
/system/etc/init/update_engine.rc
/system/etc/init/update_verifier.rc
/system/etc/init/usbd.rc
/system/etc/init/vdc.rc
/system/etc/init/vold.rc
/system/etc/init/wait_for_keymaster.rc
/system/etc/init/wfdservice.rc
/system/etc/init/wifi-events.rc
/system/etc/init/wificond.rc
/system/etc/security/otacerts.zip
Future work:
If you have any suggestion, please feel free to help us. For instance, I still haven't found a way to remove these apps:
- Motorola Message Service
- Motorola Services Main
- Files (not GoogleFiles) it turns out that Files is needed by any app that has to browse files, so not a good idea to remove it
Also, if you want to adapt this module to better address your needs, it's pretty easy to do it. Let's say you don't want to remove YouTube:
- Extract the zip module to a folder
- Go to system/product/app/ and remove YouTube folder
- Create a zip file from inside the main folder (the one that contains common, META-INF, system, etc)
- Install the module again from inside Magisk (you don't need to remove the previous one because it will replace all the settings anyway)
Tip: if you want to change this module, don't try to remove GameMode because you'll end up in a boot loop -- yes, I tried
Thanks to foobar66 for providing some ideas of things that are safe to remove:
[ROM][magisk-based]*** GoogleWiz *** {Pixelize your OnePlus 7T pro}
*** Wiz *** Pixelize your OnePlus 7T pro "Extreme debloat: Go where OnePlus has never gone before" You thought that OnePlus phones were pretty stock Android? Hmmm .... think again ... there's still lots of stuff on these phones that you actually...
forum.xda-developers.com

fulalas said:
This is my Moto G Power debloating module. It works on the original ROM.
Click to expand...
Click to collapse
Very nice! Seems that we share a similar philosophy when it comes to what apps "need" to be on a phone.
I'm currently, and happily, using Resurrection Remix so have no need for this rn, but surely appreciate that I'll have this if I have to go back to stock.
EDIT: I also want to say that I appreciate the thorough explanation of how to modify the debloat.

@TiTiB, thanks for your kind words!
Regarding Resurrection Remix, I haven't tried it yet. Is it as good as the original one regarding battery time? I remember trying some alternative ROMs (like this) on my old Moto G4 Plus and everything was nice, except that the battery didn't last much

fulalas said:
@TiTiB, thanks for your kind words!
Regarding Resurrection Remix, I haven't tried it yet. Is it as good as the original one regarding battery time? I remember trying some alternative ROMs (like this) on my old Moto G4 Plus and everything was nice, except that the battery didn't last much
Click to expand...
Click to collapse
I don't use my phone enough to have any valid input about battery life.

Updated.
Included the following APKs to be removed:
Code:
/system/app/PrintSpooler
/system/priv-app/LMIRescueSecurity
/system/product/priv-app/CQATest
/system/product/priv-app/HiddenMenu
/system/product/priv-app/InvisibleNet
/system/product/priv-app/LifetimeData
/system/product/priv-app/MotoDisplayV6
/system/product/priv-app/PAKS
/system/product/priv-app/SlpcSystem

Past experiences have given me around 13h of screen on time with a custom rom which was around an hour more than stock at the time

Updated.
-Fixed a missing Google Drive file removal.
-Included the following APKs to be removed:
Code:
/system/preinstall/facebook.apk
/system/product/app/Republic
/system/vendor/app/OneApp
/system/vendor/app/SSGTelemetryService/SSGTelemetryService.apk

Crush Moto Action. Can you fix it?

@Ozzrak, I'm not sure what you mean. Could you be more specific?

@fulalas , after applying your module it stops working Moto Actions. Or did you specifically delete it?

@fulalas , thanks, I already figured it out myself.

Updated.
-Included the following APKs to be removed:
Code:
/system/priv-app/3c_devicemagement-binary
/system/priv-app/MotoSystemServer

Does this module remove all core gapps? If so, would installing microG via nanodroid magisk module be able to replace the core gapps?

It removes some of non-critical Google apps, like Duo, YouTube, etc. But It doesn't remove Google Play and Maps, for instance. Take a look at the full list in the first post.

Excellent work! Thanks for sharing it!

I followed the instructions and installed the debloat module in Magisk as described. Upon rebooting I still have icons for Google Duo and YouTube. These are supposed to be removed, correct?
I'm running the original shipped ROM, 10(QPMS30.80-63-6-8-5). Rooted with Magisk. Phone model is XT2041-4. Date on box is 2021-03-18.

Everything was working perfect except I can't make or receive calls. I am on Visible. What would I need to correct to fix that?

I noticed that when I install this module I lose access to my Mobile Network settings. So what typically looks like 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"
}
Looks like this instead:

Huh, something must be up, more than I initially realized, with the unbloater active I seemingly can't reliably send and receive text messages. They seemingly only come in for the first 30 seconds after I've booted my phone.

@danny8, this is really odd. They shouldn't appear anymore indeed. Are you able to open them normally? What about all the others that shouldn't appear after installing this module, like Google Drive, LiveWallpaper, etc?
@BariB523 and EvergreenMetal, I'm afraid you're going to do some trial and error. I would begin removing from the module (read the instruction in the first post) the ones with suspicious names, like CarrierDefaultApp and CarrierConfig, for instance. Sorry for not being able to give a better answer, since I don't have this problem with my carrier.

KoroTweaks Final MagiskModule

------------------------------------------------- > KORO TWEAKS <--------------------------------------------------
{
"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"
}
---------------------------------------------------- > FinalEdition <----------------------------------------------------
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Attention I will not be responsible for the slightest problem on your phone of course if it is fixable I will help you but if it is not I could do nothing for you. At your peril
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Features :
Ram Tweaks - Kernel Tweaks
Fs Tweaks - Blocks Tweaks
Module Tweaks - Ext4 Tweaks
F2FS Tweaks - CPUSET Tweaks
STUNE Tweaks - Proc Tweaks
Random Tweaks - Wakelocks Tweaks
GMS Tweaks - Bloatware Cleaner
Tracing Disable - Cpu Tweaks
Gpu Tweaks - Disable Zram
tune2fs tweaks - VM tweaks
Cpu tweaks - Scheduler Tweaks
Little net Tweaks ( not give major boost)
Block Tweaks - Latency Tweaks
Little Debloater - Tracing Disabler
Force Charge - Thermal Edits
And more
Codes taken from KingTweaks :
if [[ "${gpu_thrtl_lvl}" -eq "1" ]] || [[ "${gpu_thrtl_lvl}" -gt "1" ]]; then
gpu_calc_thrtl=$((gpu_thrtl_lvl - gpu_thrtl_lvl))
else
gpu_calc_thrtl=0
fi
write "/sys/kernel/debug/sched_features" "NEXT_BUDDY"
write "/sys/kernel/debug/sched_features" "NO_TTWU_QUEUE"
Support : Stock/Aosp/Gsi (Universal)
2 Modes Available Switchable :
Battery - Gaming
Needed :
Busybox , Termux, magisk manager
Flash on Magisk manager Busybox and koroTweaks
Reboot
After install Termux apk available on google play store or f-droid
do on it su -c koro
select your mode and its done
no need to reboot after
Credits :
NotZeetaa for his GMS script
Pedro3z0 for his codes
UsifX_EGY for his help

Thanks

WasikFahim said:
Thanks
Click to expand...
Click to collapse
np

It doesn't work. Samsung galaxy tab S7+. Stock firmware. Magisk rooted.

tin2404 said:
It doesn't work. Samsung galaxy tab S7+. Stock firmware. Magisk rooted.
Click to expand...
Click to collapse
show me why it not work plz

Another "tweaks" module?
Im going to give you my general outlook, dont take it personally, id post the same in any "tweaks" thread
For me its a no, because:
1) theyve mostly proven to be snakeoil, at best they cause issues or make devices slower
2) theres compiled binaries of god knows what "tweaks"we have no idea of the content of = security risk.
Without a browseable source of binaries and the "tweaks" contained, i wouldnt recommend anyone installing this.
Pretty much no one should be installing a tweaks module as something thats universal across devices or ROMs without knowing whats in there

ZeruxFR31 said:
show me why it not work plz
Click to expand...
Click to collapse

@tin2404
su -c koro in one go, as one command. Or if you run su first you won't need the -c and can just run koro.

73sydney said:
Another "tweaks" module?
Im going to give you my general outlook, dont take it personally, id post the same in any "tweaks" thread
For me its a no, because:
1) theyve mostly proven to be snakeoil, at best they cause issues or make devices slower
2) theres compiled binaries of god knows what "tweaks"we have no idea of the content of = security risk.
Without a browseable source of binaries and the "tweaks" contained, i wouldnt recommend anyone installing this.
Pretty much no one should be installing a tweaks module as something thats universal across devices or ROMs without knowing whats in there
Click to expand...
Click to collapse
Actually i understand you if you need my code i can give it decrypted but for information i encrypt it for more nooby users for don't **** him device when he creates modules without knowledge i hope you understand me

ZeruxFR31 said:
Actually i understand you if you need my code i can give it decrypted but for information i encrypt it for more nooby users for don't **** him device when he creates modules without knowledge i hope you understand me
Click to expand...
Click to collapse
And i recommand to flash a kernel between flash module its better

ZeruxFR31 said:
Actually i understand you if you need my code i can give it decrypted but for information i encrypt it for more nooby users for don't **** him device when he creates modules without knowledge i hope you understand me
Click to expand...
Click to collapse
You have to balance out what you think youre saving people from, and their right to know what your code is doing on their device. Its a balancing act. I personally wont run any compiled/obfuscated coded on my device, thats just my personally choice, others may have a different viewpoint, and thats their choice too

Going to try battery mode on my OnePlus Nord. )
I`ll feedback later

St.Noigel said:
Going to try battery mode on my OnePlus Nord. )
I`ll feedback later
Click to expand...
Click to collapse
okay

73sydney said:
You have to balance out what you think youre saving people from, and their right to know what your code is doing on their device. Its a balancing act. I personally wont run any compiled/obfuscated coded on my device, thats just my personally choice, others may have a different viewpoint, and thats their choice too
Click to expand...
Click to collapse
its your choise i didn't force for use my module

How to select a mode in Termux?