My first smartphone was the Samsung Galaxy S2. And I was shocked how Samsung "destroys" their own device by adding - sorry for the harsh words - idiotic and useless apps.
Samsung is the main reason why many people (most apple users) are mocking Android.
{
"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"
}
Samsung is the worst manufacturer in adding useless apps. Who needs 23 hubs for social, fitness, books, games, blablabla and 3 app stores? And 2 music players?
Nobody, I guess... That's why I deleted the useless apps from /app and /priv-app after every update and that was awful.
Some weeks ago I made this flashable zip which allows me to delete all unnecessary (at least for me!!!) apps with one flash. I made it for personal use with my OPO and BlissPop. I don't need NFC or CellBroadcastReceiver. Never.
Every ROM is different. Every ROM has same apps in /system but also different ones. That's why I'm sharing a template for the flashable zip, not a ready-2-flash-zip.
Adaptive Junk Remover
1. download the provided zip file for KK / L
2. open it with WinRAR (the best program)
3. browse to \META-INF\com\google\android
4. open the file called updater-script with Notepad++ (also the best program)
5. a) you will see this (for a ROM based on Android 5.0.x // CM12), the delete_recursive tag is necessary because L stores apps in subfolders
b) you will see this (for a ROM based on Android 4.4.x // CM11)
6. you have to add the apps you want to remove, have a look inside your /app and /priv-app folder
7. a) enter the folder name (CM12): delete_recursive("/system/app/FOLDER-NAME"); or delete_recursive("/system/priv-app/FOLDER-NAME");
b) enter the app name (CM11): delete("/system/app/APP-NAME.apk"); or delete("/system/priv-app/APP-NAME.apk");
maybe you have also .odex files, delete them with delete("/system/app/APP-NAME.odex");
8. if you've finished save the file, WinRAR asks to update the zip-file, affirm that (!!!IMPORTANT!!!)
9. flash the zip in your custom recovery
!!!WITHOUT GUARANTEE!!!
delete only apps you know they're safe to remove (link, link, link, etc.)
be aware that some apps share their libs, etc.
if anything goes wrong, for example FCs, simply reflash (dirty) your ROM and delete the FC'ed app from the updater-script of the Junk Remover
if you have questions, feel free to ask
my updater-script for my OPO running BlissPop looks like this, using it after every update, no FC, no other issue
Code:
delete_recursive("/system/app/AntHalService");
delete_recursive("/system/app/BasicDreams");
delete_recursive("/system/app/CMWallpapers");
delete_recursive("/system/app/Eleven");
delete_recursive("/system/app/Email");
delete_recursive("/system/app/FaceLock");
delete_recursive("/system/app/Galaxy4");
delete_recursive("/system/app/HoloSpiralWallpaper");
delete_recursive("/system/app/HTMLViewer");
delete_recursive("/system/app/LiveWallpapers");
delete_recursive("/system/app/LiveWallpapersPicker");
delete_recursive("/system/app/MonthCalendarWidget");
delete_recursive("/system/app/NfcNci");
delete_recursive("/system/app/NoiseField");
delete_recursive("/system/app/OpenCamera");
delete_recursive("/system/app/PhaseBeam");
delete_recursive("/system/app/PhotoPhase");
delete_recursive("/system/app/PhotoTable");
delete_recursive("/system/app/PicoTts");
delete_recursive("/system/tts");
delete_recursive("/system/app/PrintSpooler");
delete_recursive("/system/app/Stk");
delete_recursive("/system/app/Terminal");
delete_recursive("/system/app/VisualizationWallpapers");
delete_recursive("/system/app/WhisperPush");
delete_recursive("/system/priv-app/CellBroadcastReceiver");
delete_recursive("/system/priv-app/CMAccount");
delete_recursive("/system/priv-app/DeviceControl");
delete_recursive("/system/priv-app/Mms");
delete_recursive("/system/priv-app/MmsService");
delete_recursive("/system/priv-app/ScreenRecorder");
delete_recursive("/system/priv-app/Tag");
delete_recursive("/system/priv-app/Velvet");
delete_recursive("/system/priv-app/VoiceDialer");
Nice. Thanks for sharing. You did a great job explaining how to go about this and the script/zip works great. Thanks for taking the time.
oak said:
Nice. Thanks for sharing. You did a great job explaining how to go about this and the script/zip works great. Thanks for taking the time.
Click to expand...
Click to collapse
Thanks for the feedback!
Will need to make one for myself.
Sent from my Nexus 6 using Tapatalk
This worked like a charm. Thanks.
Related
that is, until now! I'm currently running Fresh rom, latest version with Swype built in, so I was having trouble installing my beta swype (didn't care, stock swype works fine anyway, didn't look into it). I wanted to share what I did in the event that it helps someone at some point.
Anyway, I was having TONS of trouble getting the Metamorph themes of swype to work, as it tells you to look for the swype app here:
data/app/com.swype.android.inputmethod.apk
But I simply did NOT have my swype installed there! I tried several things, took a while but here's the method that worked for me, if anyone else is having similar trouble but is too scared to ask about it (being that the given directions make it seem so simple, but you feel dumb when you can't freakin' figure it out!):
1. Go into root explorer, make sure you're in "RW" mode (click "mount RW" at the top if you aren't), and find system/app/ and find "swype.apk," this is where my swype was originally stored
2. Select "swype.apk" and choose "MOVE," and move it to anywhere that you'll remember, somewhere arbitrary that isn't a folder called "app" (this step is in case you screw something up). This is truly a redundant/paranoid step that I chose to do to make SURE that I have the pure, uncopied, original app somewhere safe.
3. Choose COPY and copy the app. Paste this app BACK into system/app.
4. RENAME this app exactly: com.swype.android.inputmethod.apk
5. REBOOT. Make sure swype is still working, it should be. If not, you named something improperly or put something in the wrong place.
NOW you can follow the pre-existing metamorph directions (already available elsewhere, several threads on here). I don't know who has that com.swype.android.inputmethod.apk in their data/app folder, but I never did. Confused the hell out of me. Now my swype looks DOPE, I'm using some naked version, I believe it's the version from Myn's warm, now in my Flipz Fresh rom! Loving it!
Hope this helps someone Photo attached, hopefully img codes work on this site (forgive newbieness plz)
{
"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"
}
good tips, I would also like to note that people that installed swype via apks downloaded elsewhere and sideloaded will have the apk named as your morph listed in the proper position. The reason why it was named swype.apk in system/apps is because since it was included in the Fresh build, he decided to make it a system app. Placing it in system/app iirc prevents it from being subject to market checks. I had to go the other way around cuz i modified a morph and swype would break after i applied it, so i had to apply it to the com.android version then rename and move it in to system/app
....oh the many versions of swype floating out there.
Based on apk manager script I have created a script which gives ease to modify m10 files. Copy script.bat into folder where m10tools binaries exist (at location where m10decoder.exe, m10encoder.exe, etc...).
{
"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"
}
Download Script File Here
Installation:
1. Create folders Decoded, Encoded and m10_files at location where m10tool binaries are placed.
2. Copy script.bat at location where m10tool binaries are placed.
How to use
1. Place you m10 files in m10_files folder.
2. Select desired operation as shown in screen shot.
Change Logs
Code:
[B]Version 1.0[/B]
Initial release
Let me know if anyone needs any help on this
Hmmm... We need something like this impleted in apkmanager... Looks great amresh!
worked like a charm, thanks a ton amresh
Man thats great thanx!
Senergized in 3D
Can't believe I haven't thanked you yet. I've been using this for about a month now, and one thing everyone should know, is this tool has an extra advantage. Contrary to the m10 Editor UI Application, this script uses straight command line which makes all of your sense 3.0 m10 images decode with the same file name every time, where as the UI will give you random file names every time. And this is way simpler
Amresh, This was an ingenious idea and I can't thank you enough!
mpitcher225 said:
Can't believe I haven't thanked you yet. I've been using this for about a month now, and one thing everyone should know, is this tool has an extra advantage. Contrary to the m10 Editor UI Application, this script uses straight command line which makes all of your sense 3.0 m10 images decode with the same file name every time, where as the UI will give you random file names every time. And this is way simpler
Amresh, This was an ingenious idea and I can't thank you enough!
Click to expand...
Click to collapse
Has this program been optimized to work with sense 3..5?
Sent from my A500 using xda premium
i tried to modify the htc love apk. m10 files, but the thing is when i separate the dat and png files the folders are empty...plz help if u can..
sweet, thanks, will give it a shot
{
"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"
}
Overview
This is a more than full-featured APKTool GUI, It has a few options for porting which I'll explain in great detail but for now I'd like to say despite the minimalistic look which will stay lite forever, it does do a lot for efficiency and can be used for things other than MIUI, but is made especially for MIUI.
Notepad++
This deals with edits that need to be made with Notepad++ in general; It will open the selected file from WIP as well as the one from the Rom being ported for easy comparison.
Kernel Options
Pretty Simple, Executing the 'Unpack Boot.Img' Command will automatically split your Ramdisk; which can be found in root\boot, Repack puts everything back together and inserts Boot.img back into your WIP Rom folder.
Backup Options
Use this to make a backup of the current WIP Rom files; any backup files stay present until manually overwritten; saving time since the boot.img and updater-script can be used for any MIUI build generally.
Target
When a Workspace is generated, all APK and JARs will be placed into respective folders for easy access, tick 'Base' to work with your base rom APK and JARs and tick Port to work with your Port rom components
Download: MIUI APKTool 0.10
Handbook and source / Original post
Misc. Notes
This can be compiled If you have AHK installed easily by just pasting the code into a new AHK file.
Are you a fans of MIUI?
ImaxAndroid said:
Are you a fans of MIUI?
Click to expand...
Click to collapse
Huge fan, I'm also a member of the porting team at en.miui.com ;x
Bump, I have recoded this and it is less complex in general, using only variables to keep track of its own settings.
Aapt should be kept in the same directory and folder settings are no longer persistent for the sake of simplicity; however rotating folders are still possible and it works the same as before
I added porting options lol
Bump, I've added more to this and removed the need to have to set folders before each use; Ramdisk stuff has been streamlined to be more 'in the background' and the option to backup Build.prop, Updater-Script and boot.img have been added as well.
The Backup options apply to things inside 'WIP' and when using the Load option, it inserts backup content into WIP. This takes a lot of pain away from multiple ports or multiple attempts when trying to find the right base as far as Updater-Script and Boot.img go.
Lastly the Workspace Generator has been updated to mirror the new dependancies that have appear in MIUI 3.9, this should now support all MIUI JB versions 3.9 and under
Lastly the GUI is less clunky and less obnoxious to use, and faster in general
any tutorial on how to use this?
Will try
{
"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"
}
Install apps over ADB
Install apks on any Android device running any Android version over ADB!
Hi all,
From a long time i was fiddling around with a problem of installing/downloading apps after installing a new ROM.
Thus i came up with an idea of a Batch File to install all of your apks from your system
to your phone in a few tips and taps. Hah! Found my solution .
How does it look?
To see some screenshots, please click below.
Tested on
The script had been tested on Nexus 5x, Nexus 5, Moto G4 but should work on any android device.
Downloads
Google Drive - Here is the link to Drive.
Link Below - You can also find the file below.
Installation instructions
Prerequisites
1. Platform Tools for Windows (ADB),
2. APK files,
3. Target phone connected to PC and
4. A cup of COFFEE or TEA as you like it.
Process
1. Download it from the attachments below or from the drive link above or here.
2. Copy the file to the ADB folder.
3. Execute the file.
4. You can either place your apps in "D:\Apps" folder. (Sllloooowwwww.....)
ORChange the folder location in batch file itself. (Requires some Coding Skills)
ORBatch file will ask you to change the location, if required. (Easy Installation, Pick Me!)
Troubleshooting
I don't think it's needed. But even then if you get any problem do write. I'll be happy to resolve it.
Enjoy, and also don't forget to write anything (Good, Bad or Thanks etc.)!
thank you so much if works like a charm!
Been locking for something similar.
Is it possible to take that script to next level, and make it as, a list of apps, and for them to be downloaded on the phone. I mean give order through ADB for each apps step by step, instead of folder, to be downloaded.
how to add online option like google drive folder in to the script
Hello,
I've just modded the px5 radio for my personal use, so I share it here if it can be useful to others as well. Sorry for the bad picture, it renders way better in real.
I've only tested with 1024*600 resolution.
Ideas of improvement are welcomed!
{
"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"
}
To download the apk (I'm not able to post outside link yet, not enough posts...):
drive.google.com/open?id=1MCMa6yBURbXVhWYpL8B1-XvmvM0PIYBg
Hy m8!
Great work I was also trying to change for myself, but I gave up reverse engineering (takes too long) I am a software developer and I would appreciate, if you could share your source code with me? Background: i want to create a custom style for my old mercedes with new android head unit px5. What do you say? Or explain what to do exactly... On the other hand - promise - I will share with community too!
KR
Milo
miloniko said:
Hy m8!
Great work I was also trying to change for myself, but I gave up reverse engineering (takes too long) I am a software developer and I would appreciate, if you could share your source code with me? Background: i want to create a custom style for my old mercedes with new android head unit px5. What do you say? Or explain what to do exactly... On the other hand - promise - I will share with community too!
KR
Milo
Click to expand...
Click to collapse
This is no rocket sience...
Your unit needs to be rooted!
Search for the related apps on your device, copy them to a stick.
Extract the APK with 7z and search there for the background picture in the folder "res".
Create a background picture in the same size as your screen resolution (1024x600) and name it exactly as the found background picture.
Just now use 7z to open the APK file (do not extract) move to the folder you found the background while it´s just opened in 7z and paste the new file to this folder.
Close the in 7z opened APK and copy it back to your stick.
Open the file path on your device (root rights needed), rename the original APK to may be radio.bak and copy the new one in this folder.
Change the permissions of the file back to 644.
Reboot device and you have the new background in.
This can be done with all related PNG files for the APK, as long you don´t extract it while adding the new pics.
Needs to be done after each update. So store them accordingly.
Edit:
There are different screen resolution folder to search. So have a look where you find the background related to your device.
If you don´t see any changes after reboot, you chosed the wrong folder.