I created a flashab;e zip or flashing TB after a fresh install.
There are two options to create ZIP to install TB as user or system app.
I see that there is an additional file in the flashable zip when i select to install it as a system app.
/system/lib/libtitanium.so
My question is
What is the diffeence between installing tB as user/system and whats the use of the additional .so file.
.so library is a native compiled (binary) library. What is it used for? I don't know, some faster functions of Titanium. Why is it in one ZIP and not it another? Because user .apk has its libs included and they're unpacked by system automatically into its own /data/data/<appname>/lib directory, while system app is expected to have its libs with the rest of system libs, and it doesn't unpack anything.
When the app is installed in /system, it doesn't take place in /data, and (AFAIK) it automatically inherits system permissions. That's about the only difference I'm aware of.
Jack_R1 said:
.so library is a native compiled (binary) library. What is it used for? I don't know, some faster functions of Titanium. Why is it in one ZIP and not it another? Because user .apk has its libs included and they're unpacked by system automatically into its own /data/data/<appname>/lib directory, while system app is expected to have its libs with the rest of system libs, and it doesn't unpack anything.
When the app is installed in /system, it doesn't take place in /data, and (AFAIK) it automatically inherits system permissions. That's about the only difference I'm aware of.
Click to expand...
Click to collapse
Bang on, thanks
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
Related
(Preface for noobs : /system and /data are two different partitions. Freeying up /system won't get you more intrenal memory, but /data does. Old apks rest in /system and updated versions placed in /data. You can replace the old apks using newer versions)
I heared Titanium Backup PRO does something like, but you can do this with any File Explorer with ROOT access. Its works 100% for Android Gingerbread 2.3.x , try on other versions.
### Do it on your own risk, I am not responsible for anything ###
1. Update the desired app to the latest version from Google Play Store
2. Open File Manager, Enable ROOT_ACCESS, remount /System as writable
3. Goto /system/app and backup the desired apk to sdcard
4. Goto /data/app and copy updated apk
5. Paste into /System/app
6. Note down the filename of old apk and delete the old apk
7. Rename the new apk into the old filename
8. You may encounter a FORCE CLOSE if the app was running in background
9. The updated apk in /data/app will be removed automatically
10.Restart your device, Done!
I replaced Playstore, Maps, Google Search ect..
Example: For PlayStore, updated apk will be com.android.vending-1.apk, and old apk is vending.apk
Hit thanks it it works, Thanks
thanks, nice guide! All is ok (PlayStore, Terminal Emulator), but if I merge last version of "Google Play Service", then Gmail or Maps shows the message "Unknown issue with Google Play services" when I open them... do you know how to solve? thanks in advance
p.s. configuration in signature
Better use Link2SD. It makes the integration of updates into system seamless. Rebooting the device is optional (restart only if you encounter errors).
thank you for your suggestion! I tried TitaniumBackup but it gives me the same error, then now I'm trying with Link2sd and it works well, BUT the new apk file is in system/app instead of system/priv-app, and its name is "com.google.android.gms-1.apk" instead of "PrebuiltGmsCore.apk"... can this create some problems in future?
EDIT: I tried moving to the priv-app folder and renaming the apk to be identical as before and it seems to work... for now...
It's the package name, it won't create any problems. There is no need to rename the app to match the old one. Default location when converting to system app is in /system/app. I don't know if you can change the location, but you can move it manually to /system/priv-app thru root explorer. Just restart the device afterwards to eliminate FC errors.
Hi,
I am trying to build my own custom ROM(JellyBean) and observed that any apk that is placed in the /system/app(adb push somefile.apk /system/app) folder gets a corresponding .dex file in the /cache/dalvik-cache. But when I install this apk using "adb install some.apk", an entry in the /data/app folder gets added with the corresponding package name.
1) If an apk is pushed in the /system/app folder is it being cached for some performance benefit? Will there also be some part of this apk residing in the RAM after it is pushed?
2) Will this .dex file in the dalvik-cache folder ever get deleted?
3) Does installing an app(and not running it) still cause some memory to be occupied in the RAM/Cache? I have observed that installing around 120 apps on my device causes it to be less responsive.
I have tried to find a thread with these questions but not much luck. Any insights would be appreciated.
Thanks!!
.dex still exists after a cache wipe
I did a dalvik cache wipe and after a reboot this .dex is recreated. Looks like this .dex will never be deleted.
You may have tried to move some APKs to /system/app/ and end up with continuous crashes, usually resulting in abandoning your plan to save some otherwise wasted space (or preventing to accidentally uninstall all keyboards...)
This is often said to be a permissions issue, yet that's not enough for some packages: those with external libraries.
Copy the APK to /system/app/, then `chmod 644` it as usual.
You can also install to /preload and symlink to system
On your computer (easier but not required), open the APK (as a renamed ZIP).
Go to ./lib/{architecture}/, where on the Ace2 this is lib/armeabi-v7a.
Extract all the (.so) files here and put them in /system/lib.
There's no step 5!
Ryccardo said:
You may have tried to move some APKs to /system/app/ and end up with continuous crashes, usually resulting in abandoning your plan to save some otherwise wasted space (or preventing to accidentally uninstall all keyboards...)
This is often said to be a permissions issue, yet that's not enough for some packages: those with external libraries.
Copy the APK to /system/app/, then `chmod 644` it as usual.
You can also install to /preload and symlink to system
On your computer (easier but not required), open the APK (as a renamed ZIP).
Go to ./lib/{architecture}/, where on the Ace2 this is lib/armeabi-v7a.
Extract all the (.so) files here and put them in /system/lib.
There's no step 5!
Click to expand...
Click to collapse
Thank you very much :good:
All of the above is still true if you want to package apps in CWM format, but people who just are tight on /data (and don't want to repartition) can just use the convert to system app in Link2SD, which now actually works on apps with libraries
Ive made a few changes the the apktool for android. First off it will be installed to they system partition. The apktool data folder will also be in system partition, so don't forget to set it when you start the app. Reason being is the emulated SD doesn't allow executing of files. If you want to use the app to unpack/repack and tweak your boot.img. Make a working directory in the apktool folder and place the boot.img in it then unpack and tweak. You have to options so choose the "common" unpack and repack when it asks.
I wanted to make this a universal system install. So before you flash just mount your system partition because the script will not. Won't hurt nothing it just simply won't install unless system is mounted.
It will work on whatever ROM you're using to save any questions. here's the link flash it and modify some apps right on your phone. Its fully tested and it works great
https://docs.google.com/file/d/0B0xIhMfx77oQVlJVY0J0bHJFRFE/edit?usp=docslist_api
Sent from my One Mini
A reference to ware the file system in oxygen lays for apps.
User app= /data/app (the folders for each user app are not labeled after what they are.)
System apps (in OxygenOS))=/system/product/priv-app or /system/product/app
It depends which type of system app you intend to make to app. Either directory works.
So I like viper4android and will use it as an example.
1 download this version ViPER4Android-FX_2_7_1_0.apk
2: install it as a user app. It should work now but need the rootless driver install in twrp for it 1st.
3: boot 2 twrp, mount all partitions (works better). Flash the zip, reboot to system.
4: verify the app functions add the Ulta low buffer module or what ever else need to be hooked to the app were Systemizing.
5: everything set use a app like Sdmaid to get the actual directory name that oxygenOS installed it to. Just the 1st two letters works for this to ID it in twrp (ware we won't be able to check.
6: boot to twrp. Mount all partitions. open a file manager it has. Go-to the app's directory under /data/app/... That apps directory. Open that directory and move the next directory to...
/System/product/priv-app or /app.
7: you don't have to but you can now use the file manager in twrp to verify that the app folder moved there and rename it to a better ID if you want. Also you better compare the app's permissions to another system app in that directory and match it up.
Reboot and if the directions were followed, you have systemized an app.
This works better than a systemized app, or a magisk/twrp module. Why cause twrp work is the hands-on management.
The droidware I recommend is.
Sdmaid (lookup apps given directory name.)
Orangefox (dual boot) cause I use it.
A file manager to check you work helps. Need root authority. I recommend the one I'll linkup.
In other roms and OSs the system directory for system app placement is just /system/app or prive-app.
Don't forget to mount the partitions before any working in twrp. I realized that about flashing and twrps modules running while I'm editing my system.
Sorry not adding links or apps good luck with it.
One other thing the boot animation.zip file for changing in located /system/product/media on Oxygen 11.
Ohh yeah theirs a app on play store called partitions manage. You can save any partition live while running you OS to a .omg file. If I do that after Systemizing some apps. It makese a system.img with them included. No more work to redo.
Well gonna go get beer or white pirate stuff. Lol
Mod edit: removed references to warez app.