Develop Bugs

[JVP] Automatic brightness fix DIY

I've made this thread to show you how to fix this frustrating bug. After few steps you'll get working light sensor better than in previous GB versions
Files need to be replaced or edited:
- services.jar
- framework-res.apk
- sensors.default.so
Recommended kernel:
- Galaxian*
Based on original Samsung sources
All Voodoo addictions (color fix, sound V9)
CPU frequencies: 100MHz, 200MHz, 400MHz, 800MHz, 1000MHz, 1200MHz, 1300MHz, 1400MHz.
CONFIG_HZ=500
CWM 3.0.0.5 based on, and fully compatible with CF-ROOT
Light sensor polling 1s instead of 2s
Compatible with RFS and EXT4
Much more I can't remember
What needs to be done:
framework-res.apk edit
1. Get apk manager (attached)
2. Put framework-res.apk in "place-apk-here-for-modding" folder
3. Run apk manager, decompile with dependancy (option 10)
4. Drag twframework-res.apk from your ROM into the script, or extract it somewhere and type path to it
5. Go into projects\framework-res\res\values\arrays.xml
6. Replace two sections:
<integer-array name="config_autoBrightnessLevels">
<item>30</item>
<item>300</item>
<item>600</item>
<item>1500</item>
<item>1500</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>80</item>
<item>150</item>
<item>200</item>
<item>255</item>
</integer-array>
Click to expand...
Click to collapse
7. Delete .bak file if you got one after changes
8. Go back to script and select compile
9. Say y
10. Say y
11. Delete resources.arsc from keep folder
12. Enter in script
13. U'll find unsignedframework-res.apk in "modding" folder
14. Use ADB
Code:
adb push unsignedframework-res.apk /data/local/tmp/framework-res.apk
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/framework/framework-res.apk
cp /data/local/tmp/framework-res.apk /system/framework/
rm /data/local/tmp/framework-res.apk
reboot
services.jar replace/edit
Attached services.jar should be compatible with all JVP releases as long as author didn't modified it. If you are not sure you can always edit your own version by doing:
1. Get apk manager (attached)
2. Put services.jar in "place-apk-here-for-modding" folder
3. Rename it to services.apk
4. Run apk manager, decompile (option 9)
5. Go into projects\services.apk\smali\com\android\server\
6. Replace PowerManagerService.smali file with the one from my services.jar
7. Delete .bak file if you got one after changes
8. Go back to script and select compile
9. Say n
13. U'll find unsignedservices.apk in "modding" folder
14. Rename it to services.jar
14. Use ADB
Code:
adb push services.jar /data/local/tmp/
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/framework/services.jar
cp /data/local/tmp/services.jar /system/framework/
rm /data/local/tmp/services.jar
reboot
sensors.default.so replace
1. Use ADB
Code:
adb push sensors.default.so /data/local/tmp/
adb shell
su
mount -o rw,remount /dev/block/stl9 /system
stop
rm /system/lib/hw/sensors.default.so
cp /data/local/tmp/sensors.default.so /system/lib/hw/
chmod 644 /system/lib/hw/sensors.default.so
rm /data/local/tmp/sensors.default.so
reboot
GALAXIAN KERNEL:
1. Go to the Market place
2. Install SGS kernel flasher
3. Extract zImage.7z to your internal SD card
4. Select zImage and flash
5. Be happy
New version of sensors.default.so! Now all 4 steps are working!
BTW. With those files you will now loose BLN!

Thank you very much in providing this fix.

Thks
This is what I have been waiting for....
I will recompile my services.jar n framework-res.apk and incorporate them into my custom rom.
Thank you so much!

i do not get it =) what is this fixing Oo

$omator said:
i do not get it =) what is this fixing Oo
Click to expand...
Click to collapse
It fixes the Auto brightness issue in some kernels.

i guess when auto brightness is checkedit is not reacting or reacting wrong?

Im guessing this only works on deodexed?

This is a fix of the moth !
THANK YOU SIR !
btw., what kernel is this? your own ?
Simce I can't find Galaxian anywhere on the forum.
Btw. where are the attached binaries from? Extract from original JVP kernel ?

$omator said:
i guess when auto brightness is checkedit is not reacting or reacting wrong?
Click to expand...
Click to collapse
In some kernels the brighness is reversed or totally wrong.
This has fixed it.

@ Brotuck
Will you try and include this in your GingerMod Rom? (...does it need it?)

eternal-intent said:
@ Brotuck
Will you try and include this in your GingerMod Rom? (...does it need it?)
Click to expand...
Click to collapse
I already updated my GM22 @ damians site.
It also uses a slightly different value, tested it today worked fine !

Brotuck said:
I already updated my GM22 @ damians site.
It also uses a slightly different value, tested it today worked fine !
Click to expand...
Click to collapse
Cool.
Well, I'm off to check it out...
And to the OP thanks, I'm interested to see what effect this has...it's not that I'm lazy, I just still lack confidence in my adb (dis)ability or I'd be more inclined to try and do it myself.

CWM can ask

ok now i see what is going on here =)
-provided sensors.default.so is 1:1 with stock JVP one
Click to expand...
Click to collapse
-arrays.xml is tweaked when compared to stock - and my guess OP made an error here as
<!-- Array of output values for LCD backlight corresponding to the LUX values
in the config_autoBrightnessLevels array. This array should have size one greater
than the size of the config_autoBrightnessLevels array.
-->
Click to expand...
Click to collapse
those are stock values from JVP below
<integer-array name="config_autoBrightnessLevels">
<item>30</item>
<item>2000</item>
<item>6000</item>
<item>11000</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>32</item>
<item>70</item>
<item>116</item>
<item>177</item>
<item>253</item>
</integer-array>
Click to expand...
Click to collapse
Click to expand...
Click to collapse
-at the services.jar few more tweeks that i do not see much sense in =)
i would realy like to see explanation of those changes
Click to expand...
Click to collapse

Ill look at this properly, but couldn't you put this in a CWM flashable package? Thanks if you can.
Sent from my ever changing Galaxy S

CWM flashable package, please

The biggest "problem" is that you need to change values in the framework.
And that one is connected to the theme you use.
Battery color / lockscreens stuff like that.
So making 1 general CWM is a problem....
If you encounter brightness problems, like not responding to changes or bright light in the dark (when it should be darker)
Then but only then consider this mod, if you do not know how to do it, then ask the theme maker.

ill rephrase my question =)
why those fixes (left stock, right this fix/tweak)
ALL_BRIGHT from 15 to 255
ANIM_STEPS from 10 to 50
AUTOBRIGHTNESS_ANIM_STEPS from 10 to 50
LIGHT_SENSOR_DELAY from 2000 to 1000

@$omator: it`s working! i think this is the only relevant answer!
you know a better way? then do it and start your own thread!

I'd like to try this fix but I can't because each time >compile< gets me an error in APK Manager! Something like "unknown source" and "could not exec command". Does anyone here have any success with this fix and Bezke JVP-ROM?

[TOOL] Nightly Updater | 1.5 | Make Your Nexus Perfect | Backup | AROMA | Manta

I only have the NEW Nexus 7 and Nexus 4, so I am relying on you all to test...
Although it should work swimmingly!
{
"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"
}
Make Your Nexus Perfect
WHAT'S NEW?
> VER 1.5 | SEPT 10 2013
-> Quick Install quickened to 4 clicks as opposed to 6
-> Backup/Restore Menu Added
-> Backup/Restore User Apps and be able to remove backups
-> Backup/Restore Anything using keep.txt and be able to remove backups
-> How To section updated with info on Backup/Restore Menu
-> junk.txt Updated with Media and Face Unlock files
-> On the horizon: App deletion in AROMA installer
PREREQS
Nexus Device that has a system app you do not want
Grade school diploma (i.e. ability to read)
THE SKINNY
WHAT IS NIGHTLY UPDATER
Nightly Updater is an AROMA installer for those that
yearn to have the cleanest device. Since I first
owned an HTC Droid Eris, I have been wiping bloatware
off of my device. Flash foward to my latest devices -
LG Nexus 4 and the 2013 Asus Nexus 7 and there ain't
much bloatware... But, all AOSP ROMs tend to come with
at least one or two apps that I can do without (and
sometimes a lot more). Nightly Updater is a simple
tool that allows users to remove unwanted system
applications in an easy manner. NU also allows users
to customize which apps are removed.
HOW DOES IT WORK
Nightly Updater works by relying on scripts that
read txt files. When customizing your script, the
installer looks for junk.txt in the "NU" folder of
your virtual (i.e. internal) SD card. Each line that
has not been "commented out" (i.e. does not have a
"#" at the front of it) or any terms (i.e. app
descriptions) that follow a "#" are removed from the
script. This leaves Nightly Updater with a clean text
file that only has the applications you want to remove.
Review:
Custom Script is called: junk.txt
Custom Script goes here: /sdcard/NU/junk.txt
#Chrome.apk -- NOT DELETED FROM DEVICE
Chrome.apk -- DELETED FROM DEVICE
Chrome.apk #Google Browser -- AFTER "#" IGNORED
HOW DO I ADD MY OWN APPS
You can add your own apps in three ways: [1] name (without
apk), [2] name (with apk), or [3] file path.
[1] Name (without ".apk")... Just type:
Code:
Chrome
The installer will automatically know it is looking for an apk and
delete Chrome.apk.
[2] Name (with ".apk")... Just type:
Code:
Chrome.apk
I think you know what it does.
[3] Full File Path... Now, you can get a little funkier and do the entire
file path like:
Code:
/data/app/Chrome.apk
This comes in
handy for files like pre-loaded wallpapers and
ringtones you may want to remove. Be cognizant of
where the files you are removing are located! This
will become very important when telling Nightly
Updater where to scan.
By the way, Nightly Updater also recognizes wildcards.
This is great for those user apps that end up having
unpredictable file names. For example:
Code:
/data/app/com.google.android.youtub*.apk
com.google.android.youtube*
These are both ways of erasing YouTube regardless of
the "-X" at the end of the file name.
WHAT'S UP WITH SCANNING
When using a Custom Script, Nightly Updater asks
where you would like to scan for apps. By default,
Nightly Updater recommends you only scan in the
System/App folder - which is where (shocker) system
apps are located. Remember, most junk apps are located
in System/App. However, Nightly Updater has also given
the option to scan Data/App. Some developers will put
apps in the Data/App folder, so it may be useful to
remove apps from there. But NORMALLY, these are only
the apps you chose to install. The final option is
to scan EVERYWHERE. Be very cautious with this command!
Remember that it is matching what you write in
junk.txt with the scan parameter. If you accidentally
wrote "system" as an app you wanted to remove instead
of SystemTuner.apk (with full scan on)... you would
erase your system folder... that's REALLY BAD!!!
Now, if you only check this option when you are using
full path and double check your junk.txt file so that
you did not make any mistakes... YOU ARE GOOD!!!
When in doubt, post your junk.txt here and I will
check it over for you
WHAT'S THE DEFAULT SCRIPT
If you download junk.txt from the OP at XDA, then
you have seen the Default Script. The Default
Script is meant to remove apps that MOST people
would consider expendable. If you are nervous to
tinker with your own Custom Script, try running
the Default Script first. If the script deleted
an app you need or did not delete at app you want
to destroy - hit me up and I will walk you
through the steps.
MORE DIRECTIONS ARE IN THE INSTALLER
DOWNLOADS
Check the "Downloads" Tab
NU-1.5.zip - Nightly Updater Installer
junk.txt - Customizable Removal Script
keep.txt - Customizable Backup Script
BUGS
Installer will occasionally hang when you press "< Back" - Reboot Device to fix temporarily
You tell me
HOW YOU CAN HELP
Give me feature ideas
Come up with more pre-loaded apps to be added to junk.txt
SPECIAL THANKS
Patrics83 and the whole ROM Cleaner team for the inspiration of this amazing tool!!! :good:​
XDA:DevDB Information
Nightly Updater, a Tool/Utility for the Google Nexus 10
Contributors
swagstr
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2013-09-10
Created 2013-09-09
Last Updated 2013-09-10

This is a great idea! I've been doing this with shell scripts for the last few months, something I run after installing a new ROM.
One question, does the app work with system apps? The example showed /data/app/*. Is it the scam that does /data/app/* and /system/app?
Also - a nice enhancement would be able to delete an app's data/cache (but not the app) after installing a ROM.
Here's a sample from my script:
Spoiler
#!/system/bin/sh
# Mount /system rw
busybox mount -o remount,rw /system
# Variables to common directories
ei=/system/etc/init.d
tw=/sdcard/_Backup/Tweaks
sa=/system/app
# Copy bootanimation
cp $tw/../bootanimations/bootanimation-GooglePlay.zip /system/media/bootanimation.zip
chmod 755 /system/media/bootanimation.zip
# Setup init.d if needed
mkdir $ei
chmod 755 $ei
# Copy over useful scripts
cp $tw/02log $ei
chmod 755 $ei/02log
# Change build.prop to support TWC streaming app
sed -i 's/release-keys/Nexus 10/' /system/build.prop
sed -i 's/test-keys/Nexus 10/' /system/build.prop
# Remove data for problematic apps
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
rm -rf /data/data/com.android.deskclock/*
rm -rf /data/data/com.tmobile.thememanager/*
# Remove unwanted apps
rm $sa/Accuweather*.apk
rm $sa/Apollo.apk
rm $sa/BlueBalls.apk
rm $sa/Books.apk

sttovo said:
This is a great idea! I've been doing this with shell scripts for the last few months, something I run after installing a new ROM.
One question, does the app work with system apps? The example showed /data/app/*. Is it the scam that does /data/app/* and /system/app?
Also - a nice enhancement would be able to delete an app's data/cache (but not the app) after installing a ROM.
Here's a sample from my script:
Spoiler
#!/system/bin/sh
# Mount /system rw
busybox mount -o remount,rw /system
# Variables to common directories
ei=/system/etc/init.d
tw=/sdcard/_Backup/Tweaks
sa=/system/app
# Copy bootanimation
cp $tw/../bootanimations/bootanimation-GooglePlay.zip /system/media/bootanimation.zip
chmod 755 /system/media/bootanimation.zip
# Setup init.d if needed
mkdir $ei
chmod 755 $ei
# Copy over useful scripts
cp $tw/02log $ei
chmod 755 $ei/02log
# Change build.prop to support TWC streaming app
sed -i 's/release-keys/Nexus 10/' /system/build.prop
sed -i 's/test-keys/Nexus 10/' /system/build.prop
# Remove data for problematic apps
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
rm -rf /data/data/com.android.deskclock/*
rm -rf /data/data/com.tmobile.thememanager/*
# Remove unwanted apps
rm $sa/Accuweather*.apk
rm $sa/Apollo.apk
rm $sa/BlueBalls.apk
rm $sa/Books.apk
Click to expand...
Click to collapse
Most definitely works with system apps. Just add "Apollo" and scan system... /system/app/Apollo.apk is deleted! I really like your script too! Smart idea to back up init.d and boot animation!
Sent from my Nexus 4 using Tapatalk 4

swagstr said:
I really like your script too! Smart idea to back up init.d and boot animation!
Click to expand...
Click to collapse
Ok - will give this a shot when I flash again.
Please feel free to take whatever you want !!!

sttovo said:
Ok - will give this a shot when I flash again.
Please feel free to take whatever you want !!!
Click to expand...
Click to collapse
Good to hear! :good:
Also, if any of you adventurous five people out there that downloaded this bad boy want to post some results for the Manta... that would be nice (As I do not have one)

Question for you… I want to delete all the folders under a certain folder, the OS command would be like this:
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
Looking at the help in the junk.txt file, I'm not sure how to do this, seems I can do one file or one folder, not multiple folders?
# /path/to/file/file.txt > Deletes file.txt
# /path/to/folder/ > Deletes folder ... REMEMBER the trailing "/"

sttovo said:
Question for you… I want to delete all the folders under a certain folder, the OS command would be like this:
rm -rf /data/data/com.android.providers.contacts/*
rm -rf /data/data/com.android.providers.media/*
Looking at the help in the junk.txt file, I'm not sure how to do this, seems I can do one file or one folder, not multiple folders?
# /path/to/file/file.txt > Deletes file.txt
# /path/to/folder/ > Deletes folder ... REMEMBER the trailing "/"
Click to expand...
Click to collapse
Code:
/data/data/com.android.providers.contacts/*
Should do the trick. Still the same scripting you used to use, just easier The script does rm -rf already.
Sent from my Nexus 4 using Tapatalk 4

swagstr said:
Code:
/data/data/com.android.providers.contacts/*
Should do the trick. Still the same scripting you used to use, just easier The script does rm -rf already.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Sorry, it only does rm -f currently. So for now add the "*" and it will delete everything in the folder for ya! If it doesn't break anything I will add the recursive command for folders.

Hey y'all! Working on a sizable update that is trying include several things requested from different devices. Looking for a little help on the testing side. First few that hit me up will get it.
Sent from my Nexus 4 using Tapatalk 4

BIG WARNING! DO NOT use the Data Wipe in version 1.5 and below. The script does not exclude the "media" folder... As some of you know... That's the SD CARD! I just did it and it SUCKED lol It will be fixed in the next version along with many new updates
Sent from my Nexus 4 using Tapatalk 4

Yo. Working diligently on the backup/restore feature. Next update will be sick. Standby
Sent from my Nexus 4 using Tapatalk 4

[TOOL][v1.2.0] Batch Deodexing Tools using Android Device

[Tool/Utility][v1.2.0]Apktool Mobile Batch Deodexing - Run Batch Deodex Jobs Using Your Android Device!
*** Disclamer
Your device is shipped without root for a reason. Modifying system files that are normally off limits carries the risk of being caught in a situation where you will be unable to fix the damage unless you plan ahead.
It is wise to not proceed unless you have a means of restoring your device in the event of a catastrophic event and that you are confident in your ability to restore any issues you create.
I am not and will not be responsible for any harm that may come to your device or to your sanity as a result of **** up.
For more on what's expected, new members should help themselves to the video below.
Description
A toolset for performing batch deodexing straight from your device. Comes installable as a flashable zip and can easily be modified by advanced users to suit their needs. Just drop all your odex and corresponding archives into a folder and run one simple terminal command (or use Linux Script Handler within your File Manager) and deodezed versions will be outputted to a separate folder.
I wrote this because Apktool Mobile lacks any batch features.
COMPATIBLE FOR ALL ANDROID DEVICES RUNNING ICS OR LATER!
Project is just listed here because I had to choose a location specific to a certain device when creating the project. Mods, feel free to move if desired.
Learn more about deodexing and the differences between an odexed system and deodexed system
Installed Files/Directories:
/sdcard/bdt - Directory with our smali and baksmali jars as well as directories to place batch jobs in as well as output folders. There is a readme in each folder describing it's function.
/data/misc/bdt - Directory which contains the Java Runtime Environment as well as all dependent libraries.
/system/bin - Two scripts are installed here. The first is "bdt" and contains all path variables in case you need to edit a path (ex. you download newer smali/baksmali versions to use, or change the name of the bdt directory on your /sdcard). This also contains wrapper functions athat do all the work. The second file is "batch-deodex" and once you have placed your odex (and corresponding apk/jar) files into the /sdcard/bdt/files-to-deodex folder open a command prompt and run this script to deodex all the odex files into dex files and then insert into the corresponding archive.
{
"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"
}
Installation Instructions and Usage
Download the latest version from one of the hosts in the downloads section and simply flash it in recovery. You could always manually extract the contents but then you'd also have to chmod quite a bit to set the permissions.
To uninstall, flash the uninstall zip that's also in the downloads section, or manually delete /system/bin/bdt, /system/bin/batch-deodex, /data/misc/bdt folder, and /sdcard/bdt folder.
Batch baksmali/smali
To run a batch decompile, move your odex (or deodexed apk or jars) files into /sdcard/bdt/files-to-deodex and fire a command prompt up and type:
Code:
su
. /system/bin/bdt # Import paths and functions
batch-baksmali
The source folders will be outputted to /sdcard/bdt/smali-source.
To compile a batch of deodexed source folders we just do essentially the same thing. Open up a command prompt and type:
Code:
su
. /system/bin/bdt
bbdth-smali
Doing so will create a dex file for each source folder and this will be outputted to /sdcard/bdt/dex-out.
Batch deodexing
Performing a batch deodex works much the same way. Copy all the odex files and their corresponding apk or jar into /sdcard/bdt/files-to-deodex then open a command prompt up and type:
Code:
su
# no need to import anything for this
batch-deodex
Just that easy. The script may take a while depending on how many files you're deodexing just as with the other scripts so if running a lot be patient.
The deodex script moves all odex files to ../files-to-baksmali and then calls batch-backsmali. Then the script calls batch-smali to create the dex files. After that's done it enumerates through the dex files and finds each one's corresponding archive and once it does it uses the
Code:
zip -jq {archive} classes.dex
to insert classes.dex into the archive without extracting anything or changing any compression settings, etc.
Once complete you'll have your deodexed archives and the script cleans up all other directories. The other two scripts don't do this.
Known Issues
-- Discovered that some ROMs are telling me that my scripts don't exists when they very well do, so of you are seeing a "sh: {scriptname}: The file or directory cannot be found" then just run by using the Linux Script Handler within your File Manager until I figure this out or until the ROM dev gets in touch.
-- I just discovered this error while preparing these test screenshots. It didn't effect the deodexing process though but I'll look into fixing this tomorrow. UPDATE: Haven't looked into this yet as it has no effect on the outcome. I think it's occurring because on the final loop when running a batch and when all is finished it still runs one last time, thinking it's looking for a jar file. Once I get these other minor details done I'll publish on github. Actually there is published code there now, but ir needs to be removed and updated.
Downloads
Batch Deodex Tools 1.2.0 - Box
Batch Deodex Tools 1.2.0 - Dropbox
Uninstall ZIP for 1.1.0
Changelog
Code:
1.2.0 Released: -- 08/21/14
-- fixed an issue causing the /sdcard/BDT folder to not be properly flashed
-- some editing made to the scripts in preparation for uploading to github
1.1.0 Released: -- 06/26/14
-- turned into a stand alone project
-- optimized the scripts
-- flashable in recovery
-- also created flashable zip to uninstall
1.0.1 Released: -- 06/21/14
-- initial release
TO DO
-- Migrate the JRE off /data/... to prepare for Android L. Was going to move to /data/app-lib where it probably should have been to begin but no point now, so will remain in /data/misc/bdt for the time. Rwas more in the Addendum in second post
-- Add Box, Dropbop, and Mega hosts as well. Well having just a Drive and Box host should accommodate the demand. If the demand increases I'll adjust accordingly.
-- Publish code to github.
-- Scratched making this into an APK... Having it as is makes it easier for advanced users to make modifications (use custom files, etc) on the fly
Thanks To/Credits
Code:
* Brut.all for giving us apktool and much more
*
XDA:DevDB Information
Batch Deodex Tools - Android, Tool/Utility for the LG G2
Contributors
MidnightHarvester
Version Information
Status: Stable
Current Stable Version: 1.2.0
Stable Release Date: 2014-08-21
Created 2014-06-22
Last Updated 2014-08-21

Reserved
APPENDUM
Consider this a diary. Dates are when the thoughts or discoveries hit me, not release dates
Aug 15 - After modifying the tookset so it"s Android L ready by moving the JRE to /system/{wherever}, after flashing now the BDT directory doesn't get flashed to the sdcard. I'll need to do a little fiddling with the updater script, then release it once it's working. Granted you can just manually extract and copy that directory over easily but I'd prefer a fully working flaahable..
Aug 19 - Noticed there has been updated smali and baksmali jars, so either an incremental update and most likely just a patch will be worked I n and releaaed. Because of the update I'm also looking at any other files that may have been updated.
Aug 20 - I've discovered that on some devices (specifcally, CloudyG3 1.3), that t
here arr some issues running the scripts via terminal as apparently ... they don't exist. Executing them via Linux Script Handler within a File Manager should work until I figure this out)
Aug 20 - Releases will be migrated over time to my Box account, probably Dropbox account, as well as Mega. Archived releases will also be uploaded, and the OP will be updated as each is moved.
Aug 21 - Fixed a bug preventing the /sdcard/bdt directory from being installed on flash. Also made a few revisions to the code, nothing spectacular. Also uploaded to Box and Dropbox and ditched the Drive host. Incremental update to 1.2 0.

Good job buddy. Keep it up. Will give a try it soon.
Sent from my GT-I9100 using Tapatalk 2

Thanks! I'll be publishing an update in a day or so. I'm creating a stand alone project that won't require root. Right now root is required because the scripts need to access the JRE bin that's located in the data directory of apktool. I'm moving JRE lib (and Java binary) and smali and baksmali jars into a flashable zip.
It'll also be a lot easier to maintain this way. I completely killed my phone yesterday while cleaning up the scripts. After doing a batch deodex as it is now it will clean up the working directories and delete
everything except the deodexed archives.
I modified the paths hoping to create less work in the long run and after testing the modified script by phone rebooted back up and I got "unable to find setup" message and a blank screen. I must have left a "/" off of a path and ended up wiping everything in /sdcard/ ?
The error on boot was caused by the fact I always delete the LG setup app as I never anticipate deleting my SD card. So I was stuck at a black screen with nothing to restore since I wiped the SD card.
Eventually I realized I could pull the notification bar down still, and make it into settings by long pressing a quick toggle. Once I discovered I could open Google Now after enabling it in search settings I was in my way since I could use that to open Chrome and Root Explorer, etc.
I ended up restoring my system back and just wiped /data as well since I already wiped my SD card. Then spent the rest of the day restoring my device and luckily I had most everything backed up onto Drive.
Needless to say no changes were published in yesterday. I can imagine the backlash I would have gotten if I did lol. If I had a penny for each time I've mucked my device up while working on something I'd have, well maybe a dollar but still that's a lot
It shouldn't take long to get the standalone build out. I don't plan on turning the standalone build into an apk though as its easy enough to run via terminal emulator or file manager and take up far less space.
Sent from my VS980 4G using Tapatalk

I'll find another host to upload the install zip to as well as the Drive host in the OP. The zip is too large to attach here. I hope this simplification over installation appeals to more ?

Version 1.1.0 is now live. Installation boils down to just flashing the install zip in recovery. Read OP for additional information on how to use it.

Dang man! You beat me to it hahaha! I had started on this as a personal project for myself earlier today. However, I am wanting to just implement the process strictly through the recovery and by locating/finding all .odex files in my system to later deodex and place back accordingly all without me touching a thing but just running the script. I'm currently digging through your work right now to see if anything may be helpful for what I am aiming to do. Nevertheless, greatly appreciate you sharing this project.

How do you make an odexed apk into am installable apk? I wanna take the LG QVoice apk from an odexed rom and be able to install it like a normal app without having to add it to /system/app or /system/priv-app. Would just deodexing the apk do that?

Skizzy034 said:
How do you make an odexed apk into am installable apk? I wanna take the LG QVoice apk from an odexed rom and be able to install it like a normal app without having to add it to /system/app or /system/priv-app. Would just deodexing the apk do that?
Click to expand...
Click to collapse
You would most likely need to deodex that app and then install it via /data/app.
Make sure that system app you are referring to doesn't use any lib files or other dependencies. Some system apps do and it would be needed to port them over to your device for them to work (and possibly some work on the app itself once decompiled).
Sent from my C525c using Tapatalk

Modding.MyMind said:
You would most likely need to deodex that app and then install it via /data/app.
Make sure that system app you are referring to doesn't use any lib files or other dependencies. Some system apps do and it would be needed to port them over to your device for them to work (and possibly some work on the app itself once decompiled).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Yea I didn't think of lib files for that app. It makes sense it would need it. Thanks.

Modding.MyMind said:
Dang man! You beat me to it hahaha! I had started on this as a personal project for myself earlier today. However, I am wanting to just implement the process strictly through the recovery and by locating/finding all .odex files in my system to later deodex and place back accordingly all without me touching a thing but just running the script. I'm currently digging through your work right now to see if anything may be helpful for what I am aiming to do. Nevertheless, greatly appreciate you sharing this project.
Click to expand...
Click to collapse
That's an awesome idea bro. You'd need the jre in /data/misc/jdr somewhere. You may be able to run it off the scars in recovery since you can set permissions to the /sdcard mount there but not sure.
Create a script that 'finds' all odex files system wide and corresponding archive files and use the run_program edify script command to run the script so that you can deodex everything from recovery with one slide of a button.
There's not too much that would have to be changed in the script other than changing some of working directory variables as you go. Be careful in the batch-deodex script if borrowing from that as that deletes all odex, apk, and jar files in the /BDT/*/ except for the readme files.
Edit: If you need any advice or help on that project hit me up, as I could probably get it working by the end of the day. Well sooner not this day as my son is here but tomorrow.. Sorry I didn't comment the script that much but there wasn't really much to comment, so I mainly just commented the paths.

MidnightHarvester said:
That's an awesome idea bro. You'd need the jre in /data/misc/jdr somewhere. You may be able to run it off the scars in recovery since you can set permissions to the /sdcard mount there but not sure.
Create a script that 'finds' all odex files system wide and corresponding archive files and use the run_program edify script command to run the script so that you can deodex everything from recovery with one slide of a button.
There's not too much that would have to be changed in the script other than changing some of working directory variables as you go. Be careful in the batch-deodex script if borrowing from that as that deletes all odex, apk, and jar files in the /BDT/*/ except for the readme files.
Click to expand...
Click to collapse
Thanks. I had already set up my project folder along with my deodex script before I came across this thread (what were the odds lol). Was having issues getting the script to work at all until I looked at yours and notice you were exporting the LD_LIBRARY path. I implemented that idea in my script and now I'm getting a few failures for linking executables based on certain commands such as grep for example.
The script is a combination of premade works from different people which I have put together as followed. Currently, the script is a bit rough on what I am aiming to do but my goal for now is to get it to successfully find and deodex all necessary files. Once accomplished, I will proceed forward.
Script:
PHP:
#!/sbin/sh
cd $(dirname "$0")
DEODEXED_APK="/data/DEODEXED.log"
if [ ! -f $DEODEXED_APK ]; then
busybox touch $DEODEXED_APK;
fi;
prop="/system"
smalibaksmali_dir="/data/local/tmp/smali"
java_dir="/data/local/tmp/jvm/java-7-openjdk-armhf/jre/bin/java"
#tmp="$(dirname "$1")"
export LD_LIBRARY_PATH="/data/local/tmp/jvm/java-7-openjdk-armhf"
# Deodexes every .odex file
DEODEX() {
local API="$(busybox grep "ro.build.version.sdk" "$prop/build.prop" | busybox cut -d'=' -f2)"
echo "Detected API level $API" >> $DEODEXED_APK
busybox find "$prop" -type f -iname "*.odex" | while read line; do
local FILE="$(basename "$line")"
local FILEDIR="$(dirname "$line")"
echo "Deodexing $FILE" >> $DEODEXED_APK
echo "Disassembling $FILE..." >> $DEODEXED_APK
$java_dir -Xmx512m -jar $smalibacksmali_dir/baksmali-2.0.2.jar -a "$API" -d "$prop/framework" -x "$FILEDIR/$FILE"
if [[ $? -ne 0 ]]; then
echo "ERROR DEODEXING $FILE, ABORTING!" >> $DEODEXED_APK
rm -rf out
return 1
fi
echo "Assembling into classes.dex..."
$java_dir -Xmx512m -jar $smalibacksmali_dir/smali-2.0.2.jar -a "$API" -o classes.dex out
if [[ ! -e classes.dex ]]; then
echo "ERROR DEODEXING $FILE, ABORTING!" >> $DEODEXED_APK
rm -rf out
return 1
fi
FILE="$(busybox echo "$FILE" | busybox rev | busybox cut -d'.' -f2- | busybox rev)"
local FOUND=0
for EXTENSION in "jar" "apk"; do
if [[ -e "$FILEDIR/$FILE.$EXTENSION" ]]; then
echo "Packing back into $FILE.$EXTENSION..."
zip -rq "$FILEDIR/$FILE.$EXTENSION" classes.dex
rm -f classes.dex
FOUND=1
break
fi
done
if [[ "$FOUND" -eq 0 ]]; then
echo "ERROR, No output found?!"
rm -rf out
rm -f classes.dex
return 1
fi
rm -f "$line"
rm -rf out
done
echo "Deodexing finished"
}
# Start Processing Here
DEODEX
Sent from my C525c using Tapatalk

Saved while I read script after kid stops jumping on me lol
LD_LIBRARY_PATH threw me off to. Somewhere in java or bad small or small expects it to point to the data/data/per.pqy.apktool/lix files.

MidnightHarvester said:
Exporting LD_LIBRARY_PATH and pointing that to wherever you have the lib files stored which in apktool are in /data/data/per.pqy.apktool/lix is key cause either java or baksmali or small reference that Android environment variable.
That took me a while too until I realized what I needed to do. You can cut down on size quite a bit and copy the lib files in /data/misc/bdt in my project as those are the only ones needed for smali and baksmali. With that figured out you'll have it done in no time. You could always flash these tools and then make a script like
Code:
# import my 'bdt' script
. /system/bin/bdt
# copy all odex, apks, and jars into files-to-deodex - could
# use lath variables instead of full pathnames
cp /system/app/. *odex /sdcard/BDT/files-to-deeodex
cp /system/app/. *apk /sdcard/BDT/files-to-deeodex
cp /system/priv-app/. *odex /sdcard/BDT/files-to-deeodex
cp /system/priv-app/. *apk /sdcard/BDT/files-to-deeodex
cp /system/framework/. *odex /sdcard/BDT/files-to-deeodex
cp /system/framework. *apk /sdcard/BDT/files-to-deeodex
# call batch-deodex function
batch-deodex
Then make sure all the deoxed archives are in the deodexed-out directory and if check a few make sure classes. dex are in them lol. Then if running from recovery, copy the new deodexed archives into appropriate places and set permissions (recursively unless you're insane ).
Sounds a lot like what you're doing though. Also gives me an idea for version 2 which also gives the option to deoxed the entire system and then create a flushable zip with all the deodexed archives inside. Will probably work on that tomorrow after my son is gone. Keep me posted ed on the progress on your work though as I haven't had much in out back regarding this.
Click to expand...
Click to collapse
I like your idea about making a flashable zip once it is done. I have it working now.
I made a small typo which resolved my earlier problem.
I used "smalibaksmali_dir" as my variable which pointed to the smali directory.
However, later in my script I spelled 'bak' with a 'c' - smalibacksmali_dir.
I will keep you posted man. I was shocked when i found your thread because prior to I had spoken with a relative about my project and how it appeared no one had done this. Then I found you lol. Kudos for your work bro.
Sent from my C525c using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 06:58 PM ----------
Here is a screenshot with my personal script/project running.
Sent from my C525c using Tapatalk

@MidnightHarvester, my script is working great now. However, I noticed that this bogs down the device greatly. To deodex the Rom from the device will take WAY TOO LONG then if you were to do so using a descent computer. However, if merely deodexing an app here or an app there then it's fine and tolerable but not for all *.odex files at once lol.
There has to be some way to make this move along faster. Otherwise, the wait begins for phones with better processors and more ram.
Sent from my C525c using Tapatalk

Modding.MyMind said:
@MidnightHarvester, my script is working great now. However, I noticed that this bogs down the device greatly. To deodex the Rom from the device will take WAY TOO LONG then if you were to do so using a descent computer. However, if merely deodexing an app here or an app there then it's fine and tolerable but not for all *.odex files at once lol.
There has to be some way to make this move along faster. Otherwise, the wait begins for phones with better processors and more ram.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that the scripts are only utilizing one thread (unless I'm mistaken). Is there a way in bash to start a new thread or at least call on a binary and pass over a callback function? I'll have to look into it.
When I deodexing my /system/priv-app folder I just let it run overnight. There isn't anything really in the script I can do to speed things up much as the majority of the work is being used during the baksmali and smali calls.
That's one reason I didn't echo any output like your script did which I really wanted to but I've found that things tend to run faster without output being sent to stdout. Might not be a huge hit but...
Maybe if I an get it to deodex in recovery nobody would be competing for resources? Definitely keep updated on the thread as this isn't anywhere near done yet.
I'm glad I found somebody else working on this. For a while I thought no one was that interested since there has been PC tools to do this for ages. Problem is for some (like myself) is that THIS is my PC .
I'm trying to think on how to speed things up and drawing a blank. There aren't enough odex files in all of /system for there to be issued with looping. I think the baksmaling and smaling just take time. Take a look at Matt's old Privacy Blocker app (same Matt that developed xUltimate deodex tools on PC). It takes ages to baksmali and smali there as well.
My first early version though was even worse. I actually was decompiling resources as well in the archive and creating a smali folder and moving the decompiler source as well into there and recompiling the entire apk/jar lol. Don't ask me why.
I need to borrow an idea from you as well and let the user set API level. Normally omitting it should be fine (defaults to latest doesn't it?) but having the choices might help of anyone comes across a picky app.
In the meantime if deodexing am entire folder I'd recommend just doing it at night while you sleep. If you can, use a tool to enable all four cores and set all cores to performance mode and leave the Ax plugged in. *shrugs* I have AIDE installed so if I can get into the baksmali/smali source code maybe I can at least have a look.
Edit: I'm running a multithreading test now. You can run a command in another thread by placing '&' after the command. If it works I'll update.

@MidnightHarvester, I too use my device as it were my own computer which is why I make up the things which I do lol. Seems we have much in common. I actually learned about the idea of using multithreads with '&' just the other night as I was researching for ways to optimize my script. Another method is to use 'wait' which will put any future commands on hold until the current one is finished. That should out less stress on the cpu. Another idea is to limit the use of pipes. The more pipes being implemented the more usage the cpu has to dish out.
I believe flashing and running this in the recovery may speed this up as you mentioned that it would required less resources being used during operations, but the question is how much would the improvement be lol.
Keep me updated with using multithreads and feel free to take away whatever you find to be useful from my deodex script.
Expect many future changes to it to optimize it as much as possible.
In addition, using 'while read line' can increase the performance on speed if the following commands afterwards are not causing an overhaul.
Sent from my C525c using Tapatalk
---------- Post added at 03:10 PM ---------- Previous post was at 03:04 PM ----------
I will be pushing my project to my github later on today. Will be easier to keep up with any changes I make. Will take note in README.md that the project is still in development and to use with GRAVE caution lol.
Sent from my C525c using Tapatalk
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
It's ashame I don't currently have any way to build the smali/baksmali sources from my phone.
Need to look in to it and see if any flags could optimize the final build to produce a more proficient workload in performance.
Sent from my C525c using Tapatalk

So, I am working on getting my project to work in the recovery. Looks like some troubleshooting is in store.
From my recovery.log:
Code:
about to run program [/tmp/deodex.sh] with 1 args
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
Detected API level
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "sort"; caused by library "libc.so" not found
Deodexing finished
CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "busybox"; caused by library "libc.so" not found
run_program: child exited with status 1
Sent from my C525c using Tapatalk
---------- Post added at 05:33 PM ---------- Previous post was at 05:00 PM ----------
Resolved my problem. Export path for sbin was being overwritten by the script so it prevented busybox from being used. To resolve it you just need to insure that sbin is included to the path as well.
Edit: this was tested with TWRP
PHP:
export LD_LIBRARY_PATH="/sbin":"/tmp/jvm/java-7-openjdk-armhf"
Sent from my C525c using Tapatalk

:cyclop
Modding.MyMind said:
I like your idea about making a flashable zip once it is done. I have it working now.
I made a small typo which resolved my earlier problem.
I used "smalibaksmali_dir" as my variable which pointed to the smali directory.
However, later in my script I spelled 'bak' with a 'c' - smalibacksmali_dir.
I will keep you posted man. I was shocked when i found your thread because prior to I had spoken with a relative about my project and how it appeared no one had done this. Then I found you lol. Kudos for your work bro.
Sent from my C525c using Tapatalk
---------- Post added at 07:54 PM ---------- Previous post was at 06:58 PM ----------
Here is a screenshot with my personal script/project running.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
No probs cyclops. Between family I don't get a chance to get on hereuch but that's all changing here Very soon. I really glad you're taking off where i left off. I saw that there's a GUI out now I haven't read the thread yet so not sure if it's your work or not, but I'm glad others are running with it. Beauty of open source. I rewrote a lot and published to github under GPL but unfortunately during the rewriting I broke something and haven't been back to fox it yet.
I need to as yje code is streamlined as well as being on github open where all can see and make commits. I would get on that but it seems the GUI version has taken off and this is more for legacy but who knows
I also noticed someone else had a btch deodex script published on github though no as robust but I should have borrowed off him instead of reinventing the wheel. Too bad I didn't see that until later.
Inteied my luck at multithreading the shell commands but that would require a LOT of counters keeping track of example which processes are still decompiling and which are recompiling to avoid collisions, so I lwdr it be for now. And now that the GUI is out maybe ibcan lend a hand there if needed.
Is the GUI just a command line GUI or an actual app?I'll look when done reading. If it's an actual app multithreading would be much easier and i wouldn't mind helping out on the team. If its a shell GUI like old Windows apktool versions I commend you. Takes patience to mundnely write out the interface
Either way glas there's interest and happy others with more time to devote can carry on.

@MidnightHarvester
Hello sir,
I'm trying to decompile settings.apk with apktool for android. It won't do it correctly, and I'm wondering if it's because it should be deodexed first. The only 2 I've been able to recompile are htc-resources.apk and framework-res.apk on HTC Evo 3D 4.0.3ics
That's first question, will be able to recompile settings after deodex?
I don't understand this command,
. /system/bin/bdt
bbdth-smali
Are these on one line, separate?
I'm fairly new to modding, will you help me please?
The commands listed, when pasted into terminal, errors a lot. Using SManager to run works, but what is got from it isn't a deodexed app.-
When running batch-deodex(I'm using bdt from v.1.1.0 because it throws out several errors with bdt from v.1.2.0, I haven't looked through it, so I'm not sure if it's just not echo ing them), well, first I put the settings.apk in files-to-deodex folder, create odex of it in apktool(is this right thing to do?) Settings.odex is created in same folder, then ran batch-deodex.
The exact same settings.odex is placed into files-to-baksmali. And same settings.apk is placed in deodexed-out. In the dex-out folder are same 2 files called classes.dex and Settings.dex. and in the smali-source is Settings folder with a boat load of smalis.
After it's done:
exec sh '/system/bin/batch-deodex'
in/batch-deodex' <
rm failed for -rf, No such file or directory
rm failed for -f, No such file or directory
cp: can't stat '/sdcard/BDT/files-to-deodex/*.jar': No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
And here's the log
Error occured while loading boot class path files. Aborting. org.jf.util.ExceptionWithContext: Cannot locate boot class path file /system/framework/conscrypt.odex at org.jf.dexlib2.analysis.ClassPath.loadClassPathEntry(ClassPat h.java:217) at org.jf.dexlib2.analysis.ClassPath.fromClassPath(ClassPath.jav a:161) at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:59) at org.jf.baksmali.main.main(main.java:274)
What am I doing wrong?
How do I get to having deodexed app?
Sent from above using xparent tapatalk blue

[KERNEL] Anykernel

ANYKERNEL
tuna (maguro / toro / toroplus)​[#WARRANTY]
It is difficult to update all Roms frequently, and it does not always makes sense to compile, download and flash a whole rom, if only some kernel changes are applied.
This kernel will include changes before we add them official to our kernel source on Unlegacy-Android (most of the time security bugfixes)!
Android 5.1, Android 6.0 and Android 7.x
This Kernel should work on all Android 5.1, Android 6.0 and Android 7.xRoms
Android 4.4
On Android 4.4 we need a different kernel, 4.4 Kernel includes "KitKat" tag on zip name.
What else to say
Kernel compiled using GCC 4.7
Anykernel based on Anykernel2 by @osm0sis ( https://github.com/osm0sis/AnyKernel2 ) - it will dump your boot.img and replace the zImage and add proper kernel modules.
Roms with default libion
LineageOS (unofficial)
lineage-13.0_maguro-6.0.1-20180130-2235.zip and newer
lineage-13.0_toro-6.0.1-20180130-2258.zip and newer
lineage-13.0_toroplus-6.0.1-20180130-2323.zip and newer
OmniRom (unofficial)
OmniRom 4.4: omni_tuna-4.4.4-20180128-0005.zip and newer
OmniRom 6.0: omni_tuna-6.0.1-20180128-0334.zip and newer
OmniRom 7.x: omni_tuna-7.1.2-20180128-1348.zip and newer
SlimRoms (unofficial)
Slim6: Slim_tuna-6.0.1-20180128-2356.zip and newer
Slim7: Slim_tuna-7.1.2-20180131-1640.zip
Unlegacy-Android:
All official Unlegacy-Android builds starting on 15th feburary use the default libion
On older Roms, using TI's libion, you can use attached kernel from here.
[#DONATETOME]
XDA:DevDB Information
(tuna) Anykernel, Kernel for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/Unlegacy-Android/android_kernel_samsung_tuna/tree/staging
Kernel Special Features: Testing before applying on our source official, CVE fixes
Version Information
Status: Testing
Created 2017-06-23
Last Updated 2018-05-09

Reserved
As requested, here's my setup to compile tuna kernel.
01.05.2020
Follow https://github.com/andi34/android_build-bot/blob/manifest/README.md and https://github.com/andi34/android_build-bot/blob/kernelcompile/README.md
What do you need
Kernel Source (you can get our latest kernel source on SlimRoms, OmniRoms or CyanogenMods github, "tuna kernel")
GCC ( https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7 )
pvr source, added to omap4-common device repo and hardware_ti_omap4 repo (can be found on SlimRoms, OmniRoms or CyanogenMods github)
you can use my scripts put below (update some paths, marked red )
AnyKernel2 Source from osm0sis (update for tuna needed)
build-gcc4.7.env
Code:
export CROSS_COMPILE=[COLOR="Red"]'/home/andi/android2/kernelcompile/arm-eabi-4.7/bin/arm-eabi-'[/COLOR]
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm
export ARCH=arm
export STRIP=[COLOR="Red"]/home/andi/android2/kernelcompile/arm-eabi-4.7/bin/arm-eabi-strip[/COLOR]
alias 'stm'='$STRIP --strip-unneeded *.ko'
compile-tuna.sh
Code:
#!/bin/bash
readonly red=$(tput setaf 1) # red
readonly grn=$(tput setaf 2) # green
readonly ylw=$(tput setaf 3) # yellow
readonly blu=$(tput setaf 4) # blue
readonly cya=$(tput setaf 6) # cyan
readonly txtbld=$(tput bold) # Bold
readonly bldred=$txtbld$red # red
readonly bldgrn=$txtbld$grn # green
readonly bldylw=$txtbld$ylw # yellow
readonly bldblu=$txtbld$blu # blue
readonly bldcya=$txtbld$cya # cyan
readonly txtrst=$(tput sgr0) # Reset
err() {
echo "$txtrst${red}$*$txtrst" >&2
}
warn() {
echo "$txtrst${ylw}$*$txtrst" >&2
}
info() {
echo "$txtrst${grn}$*$txtrst"
}
setbuildjobs() {
# Set build jobs
JOBS=$(expr 0 + $(grep -c ^processor /proc/cpuinfo))
info "Set build jobs to $JOBS"
}
info "Kernel source path: $KERNELSOURCE"
info "PVR Source path: $PVRSAUCE"
info "Working directory: $WORKINGDIR"
info "resulting zImage and modules stored at: $WORKINGOUTDIR"
setbuildjobs
info "Moving to kernel source"
cd $KERNELSOURCE
info "Import toolchain environment setup"
info "Toolchain: $TOOLCHAIN"
source $SAUCE/build-$TOOLCHAIN.env
info "Create a buid directory, known as KERNEL_OUT directory"
# then always use "O=$SAUCE/tuna" in kernel compilation
info "create working directory"
mkdir -p $WORKINGDIR
warn "Make sure the kernel source clean on first compilation"
make O=$WORKINGDIR mrproper
warn "Rebuild the kernel after a change, maybe we want to reset the compilation counter"
echo 0 > $WORKINGDIR/.version
info "Import kernel config file: $DEFCONFIGNAME"
make O=$WORKINGDIR $DEFCONFIGNAME
info "Change kernel configuration if needed using:"
info " make O=$WORKINGDIR menuconfig "
info "lets build the kernel"
make -j$JOBS O=$WORKINGDIR
if [ -f $WORKINGDIR/arch/arm/boot/zImage ]; then
info "Copying the resulting zImage and modules to: $WORKINGOUTDIR"
info "Creating directory..."
mkdir -p $WORKINGOUTDIR
mkdir -p $WORKINGOUTDIR/modules
cp $WORKINGDIR/arch/arm/boot/zImage $WORKINGOUTDIR/
find $WORKINGDIR/ -type f -name *.ko -exec cp {} $WORKINGOUTDIR/modules/ \;
info "Files moved!"
info "Pointing KERNELDIR to KERNEL_OUT directory"
export KERNELDIR=$WORKINGDIR
warn "Make sure the PVR source clean."
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Building the PVR module..."
make -j8 -C $PVRSAUCE/build/linux2/omap4430_android TARGET_PRODUCT="blaze_tablet" BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.1
info "Copying the resulting PVR module to: $WORKINGOUTDIR"
cp -fr $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/pvrsrvkm_sgx540_120.ko
mv $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/
warn "Don't leave any module objects in PVR source!"
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Properly stripping the kernel modules for smaller size (implified as stm command inside build.env)..."
cd $WORKINGOUTDIR/modules
stm
info "####################"
info "# Done! #"
info "####################"
else
warn "####################"
warn "# FAILED! #"
warn "####################"
fi
cd $SAUCE
tuna_k.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.7"
DEFCONFIGNAME=tuna_kitkat_defconfig
WORKINGDIR=$SAUCE/tuna-kitkat
WORKINGOUTDIR=$WORKINGDIR-bin
. `dirname $0`/compile-tuna.sh
tuna_m.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.7"
DEFCONFIGNAME=tuna_defconfig
WORKINGDIR=$SAUCE/tuna-marshmallow
WORKINGOUTDIR=$WORKINGDIR-bin
. `dirname $0`/compile-tuna.sh

Hey together!
We started preparing a common 3.0 omap4 kernel.
I have started applying some small stuff to our current kernel (also reverts some previous commits) which needs testing.
The kernel should work on all L, M and N Roms. Please let me know if you face any new issues.

Android-Andi said:
Hey together!
We started preparing a common 3.0 omap4 kernel.
I have started applying some small stuff to our current kernel (also reverts some previous commits) which needs testing.
Click to expand...
Click to collapse
Thanks for your hard work. I flashed your kernel onto DU 11.5 (Android 7.12). It boots fine and I'm writing this post with this configuration. I will test it during the next days. First difference: Nightlight now works...

Android-Andi said:
Want to support development? You can consider donating, we've spent countless of hours with this
Click to expand...
Click to collapse
@Android-Andi @Ziyan Thank you for your work! I have donated $10 and I hope others will join me to support our developers

Android-Andi said:
Please let me know if you face any new issues.
Click to expand...
Click to collapse
It's running very well but I'm getting battery drain cause of missing deep-sleep-cycles.

@guest4711 maguro?

On toro or toroplus issues i need a dmesg always because i own a maguro only.

Android-Andi said:
@guest4711 maguro?
Click to expand...
Click to collapse
Yes, good old maguro (with baseband I9250XXLJ1, see #3).

@guest4711 attached kernel reverts "cpufreq: interactive: sync with p-android-omap-3.0-dev", let's see if this fixes your issue.

double, ignore

Android-Andi said:
@guest4711 attached kernel reverts "cpufreq: interactive: sync with p-android-omap-3.0-dev", let's see if this fixes your issue.
Click to expand...
Click to collapse
Ok, I'll test it. Simple dirty flashing without any wiping?

guest4711 said:
Ok, I'll test it. Simple dirty flashing without any wiping?
Click to expand...
Click to collapse
Yeah if it's not that i have another idea. My maguro was almost empty, only could quick test wifi, camera, audio yesterday. Charging it now and going to work on it later again.

Android-Andi said:
Yeah if it's not that i have another idea. My maguro was almost empty, only could quick test wifi, camera, audio yesterday. Charging it now and going to work on it later again.
Click to expand...
Click to collapse
Ok. Quick tries to enter deep sleeping show "some devices failed to suspend" in dmesg, see attached log.

guest4711 said:
Ok. Quick tries to enter deep sleeping show "some devices failed to suspend" in dmesg, see attached log.
Click to expand...
Click to collapse
Would it help to log the same with "DU kernel" and post it here? Or do you need other logs too?

guest4711 said:
Would it help to log the same with "DU kernel" and post it here? Or do you need other logs too?
Click to expand...
Click to collapse
One more to test.

Android-Andi said:
One more to test.
Click to expand...
Click to collapse
Keep quite, please - the cpus are sleeping...

One more attached. Almost spend the whole day with it.
Have fun with it!

Android-Andi said:
One more attached. Almost spend the whole day with it.
Have fun with it!
Click to expand...
Click to collapse
Thank you. Installed and running, but need a while for testing it.
Have a nice weekend!

Another one, adds a bunch of zram changes (not enabled - shouldn't hurt) and core parts from galaxy tab2 (shouldn't hurt tuna, but we need to test).

Themes / Apps / Mods [MOD/magisk/root] GoogleWiz - my magical Magisk module (for devs/sharing !!!)

I'm posting this here for the benefit of the (developer) community.
Attached is my personal "magical" Magisk module for P6P.
I strongly suggest that you DO NOT INSTALL this ... first read below ... If you don't understand what is written below, stop reading and go back playing with your phone ;-)
What is this module doing:
- it "hides" a lot (> 80) of system APKs which I do not use (e.g. NFC, Pixel Tips, Security Hub, MusicFX, ...) - so these literally "disappear" from your phone (Magisk hiding); this works by "bind-mounting" an empty directory over the APKs' file system
- it has a bash shell for "su"
- ad blocking (hosts file, mounted as /etc/hosts)
- it has a series of init.d (mounted as /etc/init.d) and service.d (mounted as /etc/services.d) scripts that do various things (e.g. kernel tuning, disable various debugging, disable swap, run sqlite optimizer, charling limit, ext4 tweaks ...), some things will NOT be relevant to you (e.g. there are scripts that install obf maps for OSMAND)
- a number of binaries (e.g. bash, busybox, xmlstarlet, find, (g)parted, ...)
- a number of scripts (mounted in /system/bin) for my personal usage (e.g. a script to make all my settings "stick")
- enables VoLTE (check properties in system.prop file)
So, you need to unzip this module and check the stuff inside, modify as per your liking !!!
This module is a (long lived) decendent from an old (2018) Magisk based ROM on Galaxy S8 (https://forum.xda-developers.com/t/...iz-pixelize-your-s8-end-of-life-crj5.3750641/). That ROM was quite popular as it turned the Galaxy S8 into a Pixel like phone. For me personally it was a journey to learn how to develop Magisk modules and gradually became bigger and bigger ...
You CAN install it ... but it may NOT be to your liking (!!!) ... then just uninstall it from Magisk ... no harm done (except that you will have my settings) - check out the script LS99execonce to understand this
Devs: feel free to (re)use for whatever purpose ... sharing for the benefit of the community ... if you do use it, no need to mention me (but you can of course) ;-)
Most of the code is "sh" scripting (and a few "bash" scripts).
If you do run it, there will be logging info in /data/googlewiz, just do:
Code:
> adb shell
$ su
# cat /data/googlewiz/*
... and
# cat /data/LS00* (init.d scripts logging)
# cat /data/LS99* (services.d scripts logging)
Hopefully some of this can help you in developing your own magisk module.

Which file in your module lists which app get disabled/hidden?
I would prefer to go through them manually first

Unzip the module, then check all the directories which have an ".replace" file, e.g. on linux do:
Code:
> cd mydir
> unzip googlewiz.zip
> find . -name '.replace'
That wil show you the paths of the APKs which are hidden.
Sorry, I'm not a Windows guy ...
This is the list:
Code:
./system/product/app/YouTubeMusicPrebuilt/.replace
./system/product/app/SoundAmplifierPrebuilt/.replace
./system/product/app/VoiceAccessPrebuilt/.replace
./system/product/app/SafetyRegulatoryInfo/.replace
./system/product/app/PixelWallpapers2021/.replace
./system/product/app/talkback/.replace
./system/product/app/Videos/.replace
./system/product/app/VZWAPNLib/.replace
./system/product/app/DiagnosticsToolPrebuilt/.replace
./system/product/app/LocationHistoryPrebuilt/.replace
./system/product/app/MicropaperPrebuilt/.replace
./system/product/overlay/DisplayCutoutEmulationCorner/.replace
./system/product/overlay/CellBroadcastServiceOverlay/.replace
./system/product/overlay/CellBroadcastReceiverOverlay/.replace
./system/product/overlay/NavigationBarModeGesturalExtraWideBack/.replace
./system/product/overlay/DisplayCutoutAvoidAppsInCutout/.replace
./system/product/overlay/DisplayCutoutNoCutout/.replace
./system/product/overlay/FontNotoSerifSource/.replace
./system/product/overlay/NavigationBarModeGesturalNarrowBack/.replace
./system/product/overlay/OneHandedModeGestural/.replace
./system/product/overlay/NavigationBarModeGesturalWideBack/.replace
./system/product/overlay/NavigationBarMode3Button/.replace
./system/product/overlay/DisplayCutoutEmulationDouble/.replace
./system/product/overlay/DisplayCutoutEmulationWaterfall/.replace
./system/product/overlay/DisplayCutoutEmulationTall/.replace
./system/product/overlay/DisplayCutoutEmulationHole/.replace
./system/product/priv-app/Showcase/.replace
./system/product/priv-app/HotwordEnrollmentXGoogleFUSION/.replace
./system/product/priv-app/ScribePrebuilt/.replace
./system/product/priv-app/OTAConfigNoZeroTouchPrebuilt/.replace
./system/product/priv-app/OemDmTrigger/.replace
./system/product/priv-app/BetterBug/.replace
./system/product/priv-app/PartnerSetupPrebuilt/.replace
./system/product/priv-app/PixelLiveWallpaperPrebuilt/.replace
./system/product/priv-app/HelpRtcPrebuilt/.replace
./system/product/priv-app/DCMO/.replace
./system/product/priv-app/TipsPrebuilt/.replace
./system/product/priv-app/DreamlinerPrebuilt/.replace
./system/product/priv-app/AppDirectedSMSService/.replace
./system/product/priv-app/ConnMO/.replace
./system/product/priv-app/SafetyHubPrebuilt/.replace
./system/product/priv-app/CbrsNetworkMonitor/.replace
./system/product/priv-app/WellbeingPrebuilt/.replace
./system/product/priv-app/MaestroPrebuilt/.replace
./system/product/priv-app/CarrierMetrics/.replace
./system/product/priv-app/DiagMon/.replace
./system/product/priv-app/DreamlinerUpdater/.replace
./system/product/priv-app/DMService/.replace
./system/product/priv-app/HotwordEnrollmentOKGoogleFUSION/.replace
./system/app/GooglePrintRecommendationService/.replace
./system/app/PacProcessor/.replace
./system/app/BasicDreams/.replace
./system/app/NfcNci/.replace
./system/app/EasterEgg/.replace
./system/app/PartnerBookmarksProvider/.replace
./system/app/BookmarkProvider/.replace
./system/app/WallpaperBackup/.replace
./system/app/LiveWallpapersPicker/.replace
./system/app/BluetoothMidiService/.replace
./system/app/HTMLViewer/.replace
./system/system_ext/app/EmergencyInfoGoogleNoUi/.replace
./system/system_ext/priv-app/GoogleFeedback/.replace
./system/system_ext/priv-app/QuickAccessWallet/.replace
./system/system_ext/priv-app/MyVerizonServices/.replace
./system/system_ext/priv-app/obdm_stub/.replace
./system/system_ext/priv-app/StorageManagerGoogle/.replace
./system/system_ext/priv-app/WallpaperPickerGoogleRelease/.replace
./system/system_ext/priv-app/OBDM_Permissions/.replace
./system/system_ext/priv-app/LLKAgent/.replace
./system/system_ext/priv-app/PixelNfc/.replace
./system/priv-app/BuiltInPrintService/.replace
./system/priv-app/Traceur/.replace
./system/priv-app/LocalTransport/.replace
./system/priv-app/ManagedProvisioning/.replace
./system/priv-app/AppDirectedSMSService/.replace
./system/priv-app/TagGoogle/.replace
./system/priv-app/CellBroadcastLegacyApp/.replace
./system/priv-app/CallLogBackup/.replace
./system/priv-app/SharedStorageBackup/.replace
./system/priv-app/MmsService/.replace
./system/priv-app/MusicFX/.replace
./system/priv-app/BackupRestoreConfirmation/.replace

foobar66 said:
Unzip the module, then check all the directories which have an ".replace" file, e.g. on linux do:
Code:
> cd mydir
> unzip googlewiz.zip
> find . -name '.replace'
That wil show you the paths of the APKs which are hidden.
Sorry, I'm not a Windows guy ...
This is the list:
Code:
./system/product/app/YouTubeMusicPrebuilt/.replace
./system/product/app/SoundAmplifierPrebuilt/.replace
./system/product/app/VoiceAccessPrebuilt/.replace
./system/product/app/SafetyRegulatoryInfo/.replace
./system/product/app/PixelWallpapers2021/.replace
./system/product/app/talkback/.replace
./system/product/app/Videos/.replace
./system/product/app/VZWAPNLib/.replace
./system/product/app/DiagnosticsToolPrebuilt/.replace
./system/product/app/LocationHistoryPrebuilt/.replace
./system/product/app/MicropaperPrebuilt/.replace
./system/product/overlay/DisplayCutoutEmulationCorner/.replace
./system/product/overlay/CellBroadcastServiceOverlay/.replace
./system/product/overlay/CellBroadcastReceiverOverlay/.replace
./system/product/overlay/NavigationBarModeGesturalExtraWideBack/.replace
./system/product/overlay/DisplayCutoutAvoidAppsInCutout/.replace
./system/product/overlay/DisplayCutoutNoCutout/.replace
./system/product/overlay/FontNotoSerifSource/.replace
./system/product/overlay/NavigationBarModeGesturalNarrowBack/.replace
./system/product/overlay/OneHandedModeGestural/.replace
./system/product/overlay/NavigationBarModeGesturalWideBack/.replace
./system/product/overlay/NavigationBarMode3Button/.replace
./system/product/overlay/DisplayCutoutEmulationDouble/.replace
./system/product/overlay/DisplayCutoutEmulationWaterfall/.replace
./system/product/overlay/DisplayCutoutEmulationTall/.replace
./system/product/overlay/DisplayCutoutEmulationHole/.replace
./system/product/priv-app/Showcase/.replace
./system/product/priv-app/HotwordEnrollmentXGoogleFUSION/.replace
./system/product/priv-app/ScribePrebuilt/.replace
./system/product/priv-app/OTAConfigNoZeroTouchPrebuilt/.replace
./system/product/priv-app/OemDmTrigger/.replace
./system/product/priv-app/BetterBug/.replace
./system/product/priv-app/PartnerSetupPrebuilt/.replace
./system/product/priv-app/PixelLiveWallpaperPrebuilt/.replace
./system/product/priv-app/HelpRtcPrebuilt/.replace
./system/product/priv-app/DCMO/.replace
./system/product/priv-app/TipsPrebuilt/.replace
./system/product/priv-app/DreamlinerPrebuilt/.replace
./system/product/priv-app/AppDirectedSMSService/.replace
./system/product/priv-app/ConnMO/.replace
./system/product/priv-app/SafetyHubPrebuilt/.replace
./system/product/priv-app/CbrsNetworkMonitor/.replace
./system/product/priv-app/WellbeingPrebuilt/.replace
./system/product/priv-app/MaestroPrebuilt/.replace
./system/product/priv-app/CarrierMetrics/.replace
./system/product/priv-app/DiagMon/.replace
./system/product/priv-app/DreamlinerUpdater/.replace
./system/product/priv-app/DMService/.replace
./system/product/priv-app/HotwordEnrollmentOKGoogleFUSION/.replace
./system/app/GooglePrintRecommendationService/.replace
./system/app/PacProcessor/.replace
./system/app/BasicDreams/.replace
./system/app/NfcNci/.replace
./system/app/EasterEgg/.replace
./system/app/PartnerBookmarksProvider/.replace
./system/app/BookmarkProvider/.replace
./system/app/WallpaperBackup/.replace
./system/app/LiveWallpapersPicker/.replace
./system/app/BluetoothMidiService/.replace
./system/app/HTMLViewer/.replace
./system/system_ext/app/EmergencyInfoGoogleNoUi/.replace
./system/system_ext/priv-app/GoogleFeedback/.replace
./system/system_ext/priv-app/QuickAccessWallet/.replace
./system/system_ext/priv-app/MyVerizonServices/.replace
./system/system_ext/priv-app/obdm_stub/.replace
./system/system_ext/priv-app/StorageManagerGoogle/.replace
./system/system_ext/priv-app/WallpaperPickerGoogleRelease/.replace
./system/system_ext/priv-app/OBDM_Permissions/.replace
./system/system_ext/priv-app/LLKAgent/.replace
./system/system_ext/priv-app/PixelNfc/.replace
./system/priv-app/BuiltInPrintService/.replace
./system/priv-app/Traceur/.replace
./system/priv-app/LocalTransport/.replace
./system/priv-app/ManagedProvisioning/.replace
./system/priv-app/AppDirectedSMSService/.replace
./system/priv-app/TagGoogle/.replace
./system/priv-app/CellBroadcastLegacyApp/.replace
./system/priv-app/CallLogBackup/.replace
./system/priv-app/SharedStorageBackup/.replace
./system/priv-app/MmsService/.replace
./system/priv-app/MusicFX/.replace
./system/priv-app/BackupRestoreConfirmation/.replace
Click to expand...
Click to collapse
Np, I am a Linux user too
And you are sure that you can safely disable all that stuff?
I see several packages that I had disabled in AFWall+ and I noticed that some things got broken.

Utini said:
Np, I am a Linux user too
And you are sure that you can safely disable all that stuff?
I see several packages that I had disabled in AFWall+ and I noticed that some things got broken.
Click to expand...
Click to collapse
I don't have broken things. But I don't use certain things either, e.g. NFC, one handed mode, pixel tips, live wallpapers, eSIM ... all of these (and more) I have disabled ... but you have to judge for yourself!!!

I probably won't be using this, but this is awesome. I've done similar for one of my very old LG phones and tablets. More of the traditional bloatware, that is.

Like you, I've been disabling all of those same apks, pretty much every one you disabled except for NFC for the rare time I actually use it. I've done that probably for the last ten years on all my devices. You do see a slight speed increase and maybe some better battery life by disabling all of those. On my S21 Ultra I think I had about 135 apk's disabled. Great module.

Hello from Germany...
One of these settings prevents the correct display for some apps.
Here is an example from SwiftKey.
Do you know which one it could be?
In the first picture googlewiz is switched off.
The second one shows the different colors on the same keyboard.
In the third picture you can no longer see the enter button.
It seems to be something about black and white.
If I switch off dark mode with googlewiz switched on, it works without any problems.
greetz

V-Ripper said:
Here is an example from SwiftKey.
Click to expand...
Click to collapse
Hmmm ... could either be the (a) force dark setting or (b) the gesture pill removal (overlay).
Try the following:
Code:
> adb shell
$ su
# cmd overlay disable com.android.shell:NavBarFrameHeightOverlay
Then check SwiftKey again. Please report if OK or not.

I've been using this for a couple of days now & seems to be working brilliantly, thanks @foobar66!
I have highly modified the package to fit my usage - I have removed: adblocking (as I use adaway), your personal settings, the charge limit, some binaries & I have unfrozen some system apks, etc.
The module still is freezing 37 system apks & is also still running: block dev tweaks, ext4 tweaks, kernel tweaks, scheduling tweaks, swap off script, no log script, stop daemon script & swapiness script.
Everything seems to be running very well! I especially love the green "[email protected]" instead of "raven" when using shell

DanielF50 said:
Everything seems to be running very well! I especially love the green "[email protected]" instead of "raven" when using shell
Click to expand...
Click to collapse
Simple bash prompt ;-);-)
Actually, the hosts file in the magisk module is an (old) version of the AdAway one ...

Below is my most recent list of 'hidden' APKs (stuff that I don't use) ... but please check for yourself.
Code:
/system/app/BasicDreams/BasicDreams.apk
/system/app/BluetoothMidiService/BluetoothMidiService.apk
/system/app/BookmarkProvider/BookmarkProvider.apk
/system/app/CompanionDeviceManager/CompanionDeviceManager.apk
/system/app/EasterEgg/EasterEgg.apk
/system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
/system/app/HTMLViewer/HTMLViewer.apk
/system/app/LiveWallpapersPicker/LiveWallpapersPicker.apk
/system/app/NfcNci/NfcNci.apk
/system/app/PacProcessor/PacProcessor.apk
/system/app/PartnerBookmarksProvider/PartnerBookmarksProvider.apk
/system/app/SimAppDialog/SimAppDialog.apk
/system/app/Stk/Stk.apk
/system/app/WallpaperBackup/WallpaperBackup.apk
/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk
/system/priv-app/BuiltInPrintService/BuiltInPrintService.apk
/system/priv-app/CallLogBackup/CallLogBackup.apk
/system/priv-app/CellBroadcastLegacyApp/CellBroadcastLegacyApp.apk
/system/priv-app/InputDevices/InputDevices.apk
/system/priv-app/LocalTransport/LocalTransport.apk
/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk
/system/priv-app/MmsService/MmsService.apk
/system/priv-app/MtpService/MtpService.apk
/system/priv-app/MusicFX/MusicFX.apk
/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk
/system/priv-app/TagGoogle/TagGoogle.apk
/system/priv-app/Traceur/Traceur.apk
/product/app/DiagnosticsToolPrebuilt/DiagnosticsToolPrebuilt.apk
/product/app/DevicePolicyPrebuilt/DevicePolicyPrebuilt.apk
/product/app/LocationHistoryPrebuilt/LocationHistoryPrebuilt.apk
/product/app/MicropaperPrebuilt/MicropaperPrebuilt.apk
/product/app/PixelWallpapers2021/PixelWallpapers2021.apk
/product/app/SafetyRegulatoryInfo/SafetyRegulatoryInfo.apk
/product/app/SoundAmplifierPrebuilt/SoundAmplifierPrebuilt.apk
/product/app/SSRestartDetector/SSRestartDetector.apk
/product/app/talkback/talkback.apk
/product/app/Videos/Videos.apk
/product/app/VZWAPNLib/VZWAPNLib.apk
/product/app/VoiceAccessPrebuilt/VoiceAccessPrebuilt.apk
/product/app/YouTubeMusicPrebuilt/YouTubeMusicPrebuilt.apk
/product/priv-app/AppDirectedSMSService/AppDirectedSMSService.apk
/product/priv-app/BetterBug/BetterBug.apk
/product/priv-app/CarrierMetrics/CarrierMetrics.apk
/product/priv-app/CarrierWifi/CarrierWifi.apk
/product/priv-app/CbrsNetworkMonitor/CbrsNetworkMonitor.apk
/product/priv-app/ConnMO/ConnMO.apk
/product/priv-app/DCMO/DCMO.apk
/product/priv-app/DiagMon/DiagMon.apk
/product/priv-app/DMService/DMService.apk
/product/priv-app/DreamlinerPrebuilt/DreamlinerPrebuilt.apk
/product/priv-app/DreamlinerUpdater/DreamlinerUpdater.apk
/product/priv-app/EuiccGoogle/EuiccGoogle.apk
/product/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
/product/priv-app/GoogleRestorePrebuilt/GoogleRestorePrebuilt.apk
/product/priv-app/HelpRtcPrebuilt/HelpRtcPrebuilt.apk
/product/priv-app/HotwordEnrollmentOKGoogleFUSION/HotwordEnrollmentOKGoogleFUSION.apk
/product/priv-app/HotwordEnrollmentXGoogleFUSION/HotwordEnrollmentXGoogleFUSION.apk
/product/priv-app/Iwlan/Iwlan.apk
/product/priv-app/MaestroPrebuilt/MaestroPrebuilt.apk
/product/priv-app/OemDmTrigger/OemDmTrigger.apk
/product/priv-app/OTAConfigNoZeroTouchPrebuilt/OTAConfigNoZeroTouchPrebuilt.apk
/product/priv-app/PartnerSetupPrebuilt/PartnerSetupPrebuilt.apk
/product/priv-app/PixelLiveWallpaperPrebuilt/PixelLiveWallpaperPrebuilt.apk
/product/priv-app/SafetyHubPrebuilt/SafetyHubPrebuilt.apk
/product/priv-app/SCONE/SCONE.apk
/product/priv-app/ScribePrebuilt/ScribePrebuilt.apk
/product/priv-app/SetupWizardPrebuilt/SetupWizardPrebuilt.apk
/product/priv-app/Showcase/Showcase.apk
/product/priv-app/TipsPrebuilt/TipsPrebuilt.apk
/product/priv-app/WellbeingPrebuilt/WellbeingPrebuilt.apk
/product/overlay/CellBroadcastReceiverOverlay/CellBroadcastReceiverOverlay.apk
/product/overlay/CellBroadcastServiceOverlay/CellBroadcastServiceOverlay.apk
/product/overlay/DisplayCutoutAvoidAppsInCutout/AvoidAppsInCutoutOverlay.apk
/product/overlay/DisplayCutoutEmulationCorner/DisplayCutoutEmulationCornerOverlay.apk
/product/overlay/DisplayCutoutEmulationDouble/DisplayCutoutEmulationDoubleOverlay.apk
/product/overlay/DisplayCutoutEmulationHole/DisplayCutoutEmulationHoleOverlay.apk
/product/overlay/DisplayCutoutEmulationTall/DisplayCutoutEmulationTallOverlay.apk
/product/overlay/DisplayCutoutEmulationWaterfall/DisplayCutoutEmulationWaterfallOverlay.apk
/product/overlay/DisplayCutoutNoCutout/NoCutoutOverlay.apk
/product/overlay/FontNotoSerifSource/FontNotoSerifSourceOverlay.apk
/product/overlay/NavigationBarMode3Button/NavigationBarMode3ButtonOverlay.apk
/product/overlay/NavigationBarModeGesturalExtraWideBack/NavigationBarModeGesturalOverlayExtraWideBack.apk
/product/overlay/NavigationBarModeGesturalNarrowBack/NavigationBarModeGesturalOverlayNarrowBack.apk
/product/overlay/NavigationBarModeGesturalWideBack/NavigationBarModeGesturalOverlayWideBack.apk
/product/overlay/OneHandedModeGestural/OneHandedModeGesturalOverlay.apk
/product/overlay/BuiltInPrintService__auto_generated_rro_product.apk
/product/overlay/NfcNci__auto_generated_rro_product.apk
/product/overlay/Traceur__auto_generated_rro_product.apk
/product/overlay/SafetyRegulatoryInfo__auto_generated_rro_product.apk
/product/overlay/ManagedProvisioningPixelOverlay.apk
/product/overlay/SettingsOverlayGLU0G.apk
/product/overlay/PixelSetupWizardOverlay.apk
/product/overlay/PixelSetupWizardOverlay2019.apk
/product/overlay/PixelSetupWizard__auto_generated_rro_product.apk
/product/overlay/SimAppDialog__auto_generated_rro_product.apk
/system_ext/app/EmergencyInfoGoogleNoUi/EmergencyInfoGoogleNoUi.apk
/system_ext/priv-app/EuiccSupportPixel/EuiccSupportPixel.apk
/system_ext/priv-app/EuiccSupportPixelPermissions/EuiccSupportPixelPermissions.apk
/system_ext/priv-app/GoogleFeedback/GoogleFeedback.apk
/system_ext/priv-app/LLKAgent/LLKAgent.apk
/system_ext/priv-app/MyVerizonServices/MyVerizonServices.apk
/system_ext/priv-app/OBDM_Permissions/OBDM_Permissions.apk
/system_ext/priv-app/obdm_stub/obdm_stub.apk
/system_ext/priv-app/PixelNfc/PixelNfc.apk
/system_ext/priv-app/PixelSetupWizard/PixelSetupWizard.apk
/system_ext/priv-app/QuickAccessWallet/QuickAccessWallet.apk
/system_ext/priv-app/ShannonRcs/ShannonRcs.apk
/system_ext/priv-app/StorageManagerGoogle/StorageManagerGoogle.apk
/system_ext/priv-app/UwbService/UwbService.apk
/system_ext/priv-app/WallpaperPickerGoogleRelease/WallpaperPickerGoogleRelease.apk
/vendor/overlay/NfcNci__auto_generated_rro_vendor.apk
/vendor/overlay/Traceur__auto_generated_rro_vendor.apk

DanielF50 said:
I've been using this for a couple of days now & seems to be working brilliantly, thanks @foobar66!
I have highly modified the package to fit my usage - I have removed: adblocking (as I use adaway), your personal settings, the charge limit, some binaries & I have unfrozen some system apks, etc.
The module still is freezing 37 system apks & is also still running: block dev tweaks, ext4 tweaks, kernel tweaks, scheduling tweaks, swap off script, no log script, stop daemon script & swapiness script.
Everything seems to be running very well! I especially love the green "[email protected]" instead of "raven" when using shell
Click to expand...
Click to collapse
Bye the way, if you do:
Code:
> adb shell
$ su
# gset mysettings
You will have a txt file /sdcard/mysettings ... if reflects your settings in {global/system/secure} namespace. If you ever need to reinstall your pone you can just command line 'source' that file to restore your settings.
Code:
> adb shell
$ su
# source /sdcard/mysettings
But please note that not all settings form the Settings app are stored in those namespaces! So it's not a 100% restore.

And ... bye the way ... you can check log files from the 2 main Magisk scripts (post-fs-data.sh and service.sh):
Code:
> adb shell
$ su
# data /data/googlewiz/*
The log files for the /etc/init.d/ scripts:
Code:
# cat /data/LS00*
And the log files for the /etc/services.d/ scripts:
Code:
# cat /data/LS99*

Wait, EXT4 tweaks? I thought we only had F2FS?

Nope ... mostly system/ro file systems on ext4/
I have not checked lately how relevant the ext4 tweaks still are ... come from a long history since the Galaxy S4 (lol).
Anyway ...
Code:
# ls -l /sys/fs/ext4/
# ls -l /sys/fs/f2fs/
F2FS for /data (of couse) since there is writing there.
And check /etc/vendor/fstab.*
Code:
system /system ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_system,logical,first_st
age_mount,readahead_size_kb=128
system_ext /system_ext ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_system,logical,first_st
age_mount
product /product ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_system,logical,first_st
age_mount
vendor /vendor ext4 ro,barrier=1 wait,slotselect,avb=vbmeta_vendor,logical,first_st
age_mount
vendor_dlkm /vendor_dlkm ext4 ro,barrier=1 wait,slotselect,avb=vbmeta,logical,first_stage_mou
nt
/dev/block/platform/14700000.ufs/by-name/boot /boot emmc defaults slotselect,avb=boot,first_stage_mount
/dev/block/platform/14700000.ufs/by-name/efs /mnt/vendor/efs ext4 defaults,noatime,rw wait,check,formattable
/dev/block/platform/14700000.ufs/by-name/efs_backup /mnt/vendor/efs_backup ext4 defaults,noatime,rw wait,check,formattable
/dev/block/platform/14700000.ufs/by-name/modem_userdata /mnt/vendor/modem_userdata ext4 defaults,noatime,rw wait,check,formattable
/dev/block/platform/14700000.ufs/by-name/modem /mnt/vendor/modem_img ext4 ro,defaults,context=u:object_r:modem_img_file:s0,barrier=1 wait,slotsele
ct
/dev/block/platform/14700000.ufs/by-name/misc /misc emmc defaults wait
/dev/block/platform/14700000.ufs/by-name/metadata /metadata ext4 noatime,nosuid,nodev,data=journal,commit=1 wait,check,formattable,first_
stage_mount,metadata_csum
/dev/block/platform/14700000.ufs/by-name/pvmfw /pvmfw emmc defaults wait,slotselect,avb=pvmfw,first_stage_mount
/dev/block/platform/14700000.ufs/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,reserve_root=32768,resgid=1065,fsync_mode=noba
rrier,inlinecrypt,compress_extension=apk,compress_extension=apex,compress_extension=so,atgc,checkpoint_merge latemount,wait,check,quota,formattable,sysfs_path=/dev/s
ys/block/bootdevice,checkpoint=fs,reservedsize=128M,fileencryption=::inlinecrypt_optimized+wrappedkey_v0,metadata_encryption=:wrappedkey_v0,keydirectory=/metadata/vold/
metadata_encryption,fscompress,readahead_size_kb=128
/dev/block/platform/14700000.ufs/by-name/vbmeta /vbmeta emmc defaults slotselect,first_stage_mount
/dev/block/zram0 none swap defaults zramsize=3221225472,max_comp_streams=8,zram_backin
gdev_size=512M
/devices/platform/11110000.usb* auto vfat defaults voldmanaged=usb:auto

foobar66 said:
Simple bash prompt ;-);-)
Actually, the hosts file in the magisk module is an (old) version of the AdAway one ...
Click to expand...
Click to collapse
Ah yes, the app just gets new updated everyday so I use that to keep up-to-date
foobar66 said:
Bye the way, if you do:
But please note that not all settings form the Settings app are stored in those namespaces! So it's not a 100% restore.
Click to expand...
Click to collapse
Great info, thanks!
foobar66 said:
And ... bye the way ... you can check log files from the 2 main Magisk scripts (post-fs-data.sh and service.sh):
Click to expand...
Click to collapse
Yes, I used these commands to confirm which parts I was running

foobar66 said:
Hmmm ... could either be the (a) force dark setting or (b) the gesture pill removal (overlay).
Try the following:
Code:
> adb shell
$ su
# cmd overlay disable com.android.shell:NavBarFrameHeightOverlay
Then check SwiftKey again. Please report if OK or not.
Click to expand...
Click to collapse
Hello.
I'll try this tomorrow.
Should googlewiz be activated when trying?

V-Ripper said:
Hello.
I'll try this tomorrow.
Should googlewiz be activated when trying?
Click to expand...
Click to collapse
No because you are just disabling an overlay which is already there.

just a suggestion/feedback as someone who has self created modules that do some of the same things, plus over 30 years in IT:
way too many things in ONE script...personally i separate mine out, not least because you can identify points of failure far easier....
i know it seems a good idea to "everything at once", but it rarely is, and its an even worse idea when you choose to share it, its like trying to herd cats when trying to sort out user issues....
also golden rule of android #1:
never apply something which one person says works 100% and magically for them to your own device
case in point ive just left my S20+ 5G for pixel life again, and previously i had a debloat list (for use with a friends officially listed debloat magisk module) that had 169 package son it. For years i declined to give anyone my personal debloat list, because even with the disclaimer "this works for me, as i dont use any Samsung apps and replace them with Google ones, and never use device function you might" i just know some kiddie will blanket use it and then come crying when it all goes wrong, and i personally dont need that level of drama in my life. I did give my list to the 2 devs i respect and know will treat it carefully, but i would never give it to an end user...i wont even tell end users which packages i hide in magisk or other apps like Hide My Applist, because people just wont make the mental leap to consider things rationally and think for even 30 seconds, "this may be personal to him and wont work for me". Sad but true