Is someone know if there is a repertory with all the samy libs used in Galaxy to be sure to remove useless libs
in the cleaning apps there is only few libs and much apps
thank's
what do you mean lib?
anyway you can make a repertory yourself by backing up and then remove the useless one
I want a list of libraries in rom / system / lib and to know what these libs to remove or not. If I delete an apk, I delete the libs that come with
Related
I was wondering how to make a system apk such as idk the browser into a regular installable apk so that someone with no knowledge of pushing apks can install it along side their apk.
Generally system apps are just normal apps, only installed on a system partition. If you pull a system apk from a device, then you should be able to install it normally on any other device.
There are exceptions from this rule:
You can't install an app if you have it installed already. Many system apps are installed on most devices by default and this is the reason, why you can't install e.g. Browser.apk pulled from other device - most probably you have it installed already.
There are 2 solutions: you could remove system app before installation of new one or just replace it - but this isn't what you want. To create normal, installable apk you would have to modify its package name as I did with Google Maps.
Some system apps use system internals, private APIs or privileges, some additional libraries, etc. For example Settings.apk changes internal settings of OS - you can't do that in normal apk.
You can't easily move/install such apps, they're integrated with system.
thanks for this long great reply. So lets say I pulled my dialer apk changed the package name, could I install it on a friends phone NOT on the system partition ?
I'm trying to pull the dialer apk from gingerbread and port it into a normal apk using apk tool, but once and changed the package name and all that and compile it I go to install it on my phone but it says that it could not open it as an apk file. Any ideas?
Newklearx3 said:
thanks for this long great reply. So lets say I pulled my dialer apk changed the package name, could I install it on a friends phone NOT on the system partition ?
Click to expand...
Click to collapse
I think not. Note that Phone.apk is only one app that can dial, you can't add such feature to your own app, so most probably it uses private APIs to do that. It's integrated-with-system one. Same for Settings.apk and PackageManager.apk, but you should be able to pull Browser.apk, Launcher.apk, MMS.apk, Gmail.apk, Talk.apk, etc., change their package name and install on another device.
Ahh, there is one more group: SenseUI, Motoblur, etc. apps, which use additional framework resources: images, colors, texts. They won't work on a device lacking this framework, but it should be possible to make these apps framework-independent by copying all dependencies to app itself. Not that easy, but possible
Brut.all said:
I think not. Note that Phone.apk is only one app that can dial, you can't add such feature to your own app, so most probably it uses private APIs to do that. It's integrated-with-system one. Same for Settings.apk and PackageManager.apk, but you should be able to pull Browser.apk, Launcher.apk, MMS.apk, Gmail.apk, Talk.apk, etc., change their package name and install on another device.
Ahh, there is one more group: SenseUI, Motoblur, etc. apps, which use additional framework resources: images, colors, texts. They won't work on a device lacking this framework, but it should be possible to make these apps framework-independent by copying all dependents to app itself. Not that easy, but possible
Click to expand...
Click to collapse
Dude, you're amazing! So how would I go about porting the gingerbread dialer to workable installable apk?
I might be doing something wrong but I pulled the launcher and changed the package name and still the same error
Okay, i guess I'm not. I copied the apk ( unmodded ) from the rom zip and placed it on my SD card to install it and the same error, so there must be something wrong.
figured out it was the sdk version, got it to show up but wont install now.
im also interested in porting specific development apk, lets say.. CM Settings into a non Cyanogen. Tried that once by pulling CM*.apk and push it to other non Cyanogen but got cant be installed message.. any hints on this?
phoezies said:
im also interested in porting specific development apk, lets say.. CM Settings into a non Cyanogen. Tried that once by pulling CM*.apk and push it to other non Cyanogen but got cant be installed message.. any hints on this?
Click to expand...
Click to collapse
Use logcat as a start to see dependencies
XDA App
WHAT IS AN ODEX FILE?
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
THEN COMES DEODEX
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
HOW THIS WORKS
For the more geeky amongst us, Android OS uses a Java-based virtual machine for running applications, called the Dalvik Virtual Machine. A deodexed, or .dex file contains the cache used by this virtual machine (referred to as Dalvik-cache) for a program, and it is stored inside the APK. An .odex file, on the other hand, is an optimized version of this same .dex file that is stored next to the APK as opposed to inside it. Android applies this technique by default to all the system applications.
Now, when an Android-based system is booting, the davlik cache for the Davlik VM is built using these .odex files, allowing the OS to learn in advance what applications will be loaded, and thus speeds up the booting process.
By deodexing these APKs, a developer actually puts the .odex files back inside their respective APK packages. Since all code is now contained within the APK itself, it becomes possible to modify any application package without conflicting with the operating system’s execution environment.
ADVANTAGES & DISADVANTAGES
The advantage of deodexing is in modification possibilities. This is most widely used in custom ROMs and themes. A developer building a custom ROM would almost always choose to deodex the ROM package first, since that would not only allow him to modify various APKs, but also leave room for post-install theming.
On the other hand, since the .odex files were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times. However, this is true only for the first ever boot after deodexing, since the cache would still get built over time as applications are used. Longer boot times may only be seen again if the dalvik cache is wiped for some reason.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
Source From www.addictivetips.com
This looks to be a copy and paste from the description here.
If you are not the original author its usually a wise idea to acknowledge the original author/source.
And optimized dex files (odex files) may also depended on the framework classes interfaces. This means that you may end up with bootloops or FCs if you change the interface of framework files. The odex files have therefore been given a signature that all files must match.
Deodexed apks can on the other hand be used on several roms as they may only be depended on the resources in the framework-res.apk file.
So you can have an odexed framework with deodexed apks! But if you want to change the interfaces in the Framework then it is easier to deodex all instead of re-odex all.
Sent from my GT-N7000 using xda premium
Thanks for it! For me more clear now.
I need to verify this, So on an ODEXED STOCK ROM, Can I make changes like
editings png's inside System APK files,
Decompile and compile framework-res.apk,
Make changes to the framework-res.apk to enable crt screen effect ... ?
Clears another thing up for me...
Thank you for your post.
Sorry guys for posting a stupid question, but i'm not clear on one point.
I have the htc one S [s3]. How can I understand if /system/framework/framework-res.apk (and/or) framework-htc-res.apk are already deodexed? (in a practical manner)
I mean...since is an apk and I'm not seeing any framework-res.odex are they already deodexed?
Can I straightly modify it?
Thx in advance!
Hi... Cant cant i something? So what is better of them?
Sent from my GT-N7000 using xda premium
Emothic_Reagan said:
Hi... Cant cant i something? So what is better of them?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Is not that one is better than the other. They have different characteristiocs. Odexed are smaller and faster while deodexed are easily customizable but needs more space.
Guys I still need somebody to answer my question...plz...anybody?
I have at last a working 2.3.5 Android on my U8800 Pro. But, I want to clean up the bundled applications that I do not need. In order to do so, I want to find out which apks as well as what other changes I need to do in order to clean up those apps. I know that this is in the http://forum.xda-developers.com/showthread.php?t=1420728 thread, but I want more details for more applications.
What I want to know is:
I suppose that it is not just enough to remove the apk file from the /system/apps/<appname>.apk , is it? If not, what other actions must I perform?
Should I remove the relevant lines from the /system/filelist.lst file?
Where are the application's temporary/user data stored? In /data/data? Should I remove them too?
If I move the /system/app/<file>.apk to /data/app/<file>.apk, how can I stop the application from starting during boot-up in the first place?
Important note: I will not root the phone. Everything will be performed from the pink screen and the mounting of /dev/sd?{12,13} on my Linux box.
In my B521 setup the APKs that I need your help in order to understand what applications or services/widgets are represent, are:
OMACP.apk
ApkBatchInstall.apk
GenieWidget.apk
DeskClock.apk
DownloadProvider.apk
DownloadProviderUI.apk
HwOUC.apk
MagicSmokeWallpapers.apk
MyCalendar.apk
MyRichpad.apk
RichPad.apk
Service-MultiSNS.apk
SocialExt.apk
SmartcardService.apk
RichPad.apk
UpdaterSolutionEx.apk
What information I am looking for is something like this:
Gallery3D.apk: The image gallery application.
PicoTts.apk: Pico Text-to-Speech
Please for your help. After that list is completed, I will write a list of all applications (apks) that are bundled and how to remove them, I promise
true that the odex offers lower booting time (when the dalvik VM first loads) and stuff but reducing the internal memory usage?? i mean wth??
it states here on this webpage - addictivetips(dot)com/what-is-odex-and-deodex-in-android-complete-guide/
In Android file system, applications come in packages with the extension .apk.These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
Click to expand...
Click to collapse
To all the newbies- a final solution to the deodex blues!
incase you guys dont know about deodex this is what it is
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity.
Click to expand...
Click to collapse
so here it is and there you go you are now running around finding posts to help you deodex to get you the ultimate themeing experience well theres this guide i found out in the question and answers sub-section
Anyone can help me to install Cyanogen MMS apk on touchwiz lollipop , on I9505 ?
Btw, I managed to install Trebuchet on touchwizz and is fully working, but I need that MMS apk too.
Even a backup made with titanium backup would help me.
Thanks !
And please don't reply if you are a noob.
Are you trying to install them like regular apps, or are you copying them to /system/app or /system/priv-app as appropriate?
Strephon Alkhalikoi said:
Are you trying to install them like regular apps, or are you copying them to /system/app or /system/priv-app as appropriate?
Click to expand...
Click to collapse
I copied it to both locations, I restarted my phone and now what?
Maybe I must copy it in a specific folder, but I don't know exactly where.
If you copied them to the proper locations Android should have updated on a reboot. Make sure the permissions are properly set. Other than that, if it's not working, e.g. force closing, then the app likely needs a supporting library not found in the Touchwiz ROM.
Strephon Alkhalikoi said:
If you copied them to the proper locations Android should have updated on a reboot. Make sure the permissions are properly set. Other than that, if it's not working, e.g. force closing, then the app likely needs a supporting library not found in the Touchwiz ROM.
Click to expand...
Click to collapse
Ok. What is the proper folder? If you know it.
I did not find anything with sms
I mentioned the proper locations in post 2. MMS goes into /system/priv-app. The MMS directory, as all apps are now stored in their own directories, should have permissions rwxr-xr-x and the app itself should have permissions rw-r--r--.