Related
Status: Online *
If you've updated any stock apps, the updated versions won't be removed.
Now that I have my own Galaxy S3, I figured it was time to add that to the Chlorine mix.
Basically it's a web based tool that will generate a CWM compatible update.zip to remove pre-installed apps (bloat).
As always, backup and be confident with restoring your phone via download mode or CWM.
Android Chlorine
---
SGS Chlorine
SGS2 Chlorine
SGS3 Chlorine
---
SGS Chlorine (mobile)
SGS2 Chlorine (mobile)
SGS3 Chlorine (mobile)
What this does:
This is a little bit of PHP that will generate a customised CWM3 compatible update.zip which will remove specific apks (and associated .odexes).
Usage:
* Choose which APKs you want the update.zip to remove and hit the Generate button.
- You can also select a preset to save some clicking.
* Copy the generated .zip file to your phone.
* Apply it with CWM.
Thanks:
The SGS list of APKs was grabbed from the public google docs spreadsheet.
The SGS2 APK list was grabbed from this public google docs spreadsheet
The SGS3 APK list was grabbed from this public google docs spreadsheet. XDA thread
Notes:
* Requires busybox for mounting /system.
* The APK list shouldn't let you remove anything 'vital' to booting the phone (Only green "yes" marked items are in the list). If there's any bloat that does need to be added to the database, let me know. Likewise if you remove something that borks your phone.
* If you have any particular ideas for good presets, also let me know and I'll see to adding them.
* Stock apps that have been updated (either via play store or in app updates) will not be "fully" removed. You can manually remove the updates though.
reserved
reserved2
Just quickly trying this on wanamlite 1.5 to remove chaton will post back
EDIT: the good news of is that it still boots, the bad that chaton is still installed i have siyah 1.3.7 busybox and wanamlite 1.5
If you want more details just ask
Regards
Jack
first time uninstalling chatON it didnt delete the program but only the update from chatON, second time i uninstalled chatON it uninstalled the app itself
-other method-
use titanium backup to freeze/uninstall all bloatware.. works fast with tickbox and voila
Eplusz said:
first time uninstalling chatON it didnt delete the program but only the update from chatON, second time i uninstalled chatON it uninstalled the app itself
-other method-
use titanium backup to freeze/uninstall all bloatware.. works fast with tickbox and voila
Click to expand...
Click to collapse
Just tried reflashing a couple of times and am sorry to say it remains installed, but thanks for the second method.
Regards
Jack
If u could make your "site" read all your installed apps and not only bloatware,this would be a very handy and cool tool
I can also confirm that ChatON is NOT deleted after running this a couple of times. It doesn´t matter whether or not more apps, other than ChatON, is included in the .zip.
leetal said:
I can also confirm that ChatON is NOT deleted after running this a couple of times. It doesn´t matter whether or not more apps, other than ChatON, is included in the .zip.
Click to expand...
Click to collapse
Are the other apps being deleted, or is nothing being removed?
Eplusz said:
first time uninstalling chatON it didnt delete the program but only the update from chatON, second time i uninstalled chatON it uninstalled the app itself
-other method-
use titanium backup to freeze/uninstall all bloatware.. works fast with tickbox and voila
Click to expand...
Click to collapse
It 'sounds' like, ChatON shoves some crap into /data/app. (updates) which are causing it to linger around. I wasn't able to check /data/app without su.
I'll confirm in a few days when I have a chance to root, test and so on.
Eplusz said:
-other method-
use titanium backup to freeze/uninstall all bloatware.. works fast with tickbox and voila
Click to expand...
Click to collapse
Of course, this way has been around for ages. I always found maintaining the titanium backup list was more effort though. If you're flashing multiple roms frequently.
zodiaxe66 said:
Great idea. But there is already an app that can do this "app2zip" where u can backup all your apps in a flashable zip.
If u could make your "site" read all your installed apps and not only bloatware,this would be a very handy and cool tool
u should check out the app its in the market
Click to expand...
Click to collapse
...what? They do different things. app2zip takes your apps and packages them into a CWM flashable restore zip. This removes stock apps. Titanium Backup also can do both tasks. (Remove and restore).
The idea with this is that you create a CWM update that removes everything you want removed. You put it on your SD card and keep it there and use it when you upgrade. Perhaps that wasn't explained well enough in this post. I explain better in the original post for the SGS.
Am I only guy here who think that this UTILITY=APP need to be in "Galaxy S III Themes and Apps"
sargorn said:
Are the other apps being deleted, or is nothing being removed?
Click to expand...
Click to collapse
S Suggest won´t remove, likewise ChatON. I haven´t tested other apps as of now so i can´t tell =)
Great work with the webb-app! Keep it updated and it´ll be a blast!
leetal said:
S Suggest won´t remove, likewise ChatON. I haven´t tested other apps as of now so i can´t tell =)
Great work with the webb-app! Keep it updated and it´ll be a blast!
Click to expand...
Click to collapse
Hmm, downloading a custom rom at the moment to have a peek in what it sticks in /data/app. (one someone mentioned they were using earlier).
I haven't rooted/flashed anything custom on my Galaxy S3 yet as I only got it a week ago and I didn't want to have anything 'unofficial' for the first week or so just in case I had any issues and needed to return it.
I did just factory reset again though, and ChatON is updated by Play Store and S Suggest asks to auto update itself when it starts up. So again it might be a situation where the updates are dumping themselves into /data/app/.
sargorn said:
Hmm, downloading a custom rom at the moment to have a peek in what it sticks in /data/app. (one someone mentioned they were using earlier).
I haven't rooted/flashed anything custom on my Galaxy S3 yet as I only got it a week ago and I didn't want to have anything 'unofficial' for the first week or so just in case I had any issues and needed to return it.
I did just factory reset again though, and ChatON is updated by Play Store and S Suggest asks to auto update itself when it starts up. So again it might be a situation where the updates are dumping themselves into /data/app/.
Click to expand...
Click to collapse
What I suspected is accurate, I just tested myself. If you happen to have updated any of the stock apps (either via the Play store or an in app update) they will still remain.
However, you can go to the application manager in settings and hit the "remove updates" button. It will say uninstall failed but it will remove the apk from /data/app. Rebooting will remove the icons from the home screen.
Also, if you happen to remove a widget that is in use on the home screen (Accuweather/clock) TWLauncher will complain until you remove the 'dead' widget.
I "may" end up adding something that will remove the updates from /data/app. I'll have to think about how to do it. Until then you can use the workaround above.
sargorn said:
Of course, this way has been around for ages. I always found maintaining the titanium backup list was more effort though. If you're flashing multiple roms frequently.
...what? They do different things. app2zip takes your apps and packages them into a CWM flashable restore zip. This removes stock apps. Titanium Backup also can do both tasks. (Remove and restore).
The idea with this is that you create a CWM update that removes everything you want removed. You put it on your SD card and keep it there and use it when you upgrade. Perhaps that wasn't explained well enough in this post. I explain better in the original post for the SGS.
Click to expand...
Click to collapse
Yeah i know,don't even know how i came to my own conclusion.(yes i do, interrupted by my kids) i just read it again and your explanation is pretty clear. I just turned everything up side down.
Sorry m8
First post corrected
sargorn said:
Status: Online *
If you've updated any stock apps, the updated versions won't be removed.
Now that I have my own Galaxy S3, I figured it was time to add that to the Chlorine mix.
Basically it's a web based tool that will generate a CWM compatible update.zip to remove pre-installed apps (bloat).
As always, backup and be confident with restoring your phone via download mode or CWM.
Android Chlorine
---
SGS Chlorine
SGS2 Chlorine
SGS3 Chlorine
---
SGS Chlorine (mobile)
SGS2 Chlorine (mobile)
SGS3 Chlorine (mobile)
What this does:
This is a little bit of PHP that will generate a customised CWM3 compatible update.zip which will remove specific apks (and associated .odexes).
Usage:
* Choose which APKs you want the update.zip to remove and hit the Generate button.
- You can also select a preset to save some clicking.
* Copy the generated .zip file to your phone.
* Apply it with CWM.
Thanks:
The SGS list of APKs was grabbed from the public google docs spreadsheet.
The SGS2 APK list was grabbed from this public google docs spreadsheet
The SGS3 APK list was grabbed from this public google docs spreadsheet. XDA thread
Notes:
* Requires busybox for mounting /system.
* The APK list shouldn't let you remove anything 'vital' to booting the phone (Only green "yes" marked items are in the list). If there's any bloat that does need to be added to the database, let me know. Likewise if you remove something that borks your phone.
* If you have any particular ideas for good presets, also let me know and I'll see to adding them.
* Stock apps that have been updated (either via play store or in app updates) will not be "fully" removed. You can manually remove the updates though.
Click to expand...
Click to collapse
Nice information and thanks for sharing. I just generated a test .zip file and below is the updater-script that is generated;
ui_print("Android Chlorine");
run_program("/sbin/busybox", "mount", "/system");
delete("/system/app/Bluetooth.apk");
delete("/system/app/Bluetooth.odex");
delete("/system/app/BluetoothAvrcp.apk");
delete("/system/app/BluetoothAvrcp.odex");
delete("/system/app/BluetoothTest.apk");
delete("/system/app/BluetoothTest.odex");
delete("/system/app/ChromeBookmarksSyncAdapter.apk");
delete("/system/app/ChromeBookmarksSyncAdapter.odex");
delete("/system/app/GoogleQuickSearchBox.apk");
delete("/system/app/GoogleQuickSearchBox.odex");
delete("/system/app/GoogleSearchWidget");
delete("/system/app/GoogleSearchWidget.odex");
delete("/system/app/Maps.apk");
delete("/system/app/Maps.odex");
delete("/system/app/MyFiles.apk");
delete("/system/app/MyFiles.odex");
delete("/system/app/Street.apk");
delete("/system/app/Street.odex");
delete("/system/app/YouTube.apk");
delete("/system/app/YouTube.odex");
run_program("/sbin/busybox", "umount", "/system");
Alternatively you may easily remove all the unnecessary files simply using Root Explorer (if your phone is rooted of-course) and deleting files from "/system/app/", in this case you also have the chance to backup the files before deleting. Make sure you enable r/w in Root Explorer.
Cheers...
jaykhan said:
Alternatively you may easily remove all the unnecessary files simply using Root Explorer (if your phone is rooted of-course) and deleting files from "/system/app/", in this case you also have the chance to backup the files before deleting. Make sure you enable r/w in Root Explorer.
Cheers...
Click to expand...
Click to collapse
"Easily" can be quite subjective, no? If you remove said files in Root Explorer you don't get the additional information included as to what each file is. Also, making backups of files from a rom you just installed seems somewhat redundant. If you want those files back, pull them out of the rom and push them to the phone? Or just don't delete them to start with.
Last time I checked Root Explorer also cost money on the Play Store and while it has features which scope well beyond this project, it's still more expensive than using this is. (free).
thanks for the chlorine man..!
For Kitkat, the Core gapps by @BaNkS works perfectly, it's as slim as it can be. It's also odexed for those wanting to test ART. So rather than do the same work twice I thought I'll just link to his thread here:
http://forum.xda-developers.com/showthread.php?t=2012857
If you are looking for JB minimal gapps, look below.
It seems there is a lot of confusion about which minimal gapps to flash or where to get them, so I decided to make a thread for the ones I have linked to in the main CM10 and CM10.1 threads in the past.
/system/app Contents:
Code:
1. ChromeBookmarksSyncAdapter.apk
2. GoogleBackupTransport.apk - [COLOR="Red"]Can be deleted but after a Data wipe and fresh flash you will be unable to restore things that Google backs up to its server like WiFi passwords, wallpapers. Personally I don't use this backup and restore because I don't trust that data with Google anymore.[/COLOR]
3. GoogleCalendarSyncAdapter.apk
4. GoogleContactsSyncAdapter.apk
5. GoogleFeedback.apk - [COLOR="red"]Can be deleted. Some feedback mechanism when apps crash. I have never used it or even seen it myself, so I delete it before flashing the gapps.
[/COLOR]6. GoogleLoginService.apk
7. GoogleServicesFramework.apk
8. MediaUploader.apk - [COLOR="red"]Can be deleted. This enables sharing pics to Picasa in the stock Gallery. Personally I remove it.[/COLOR]
9. NetworkLocation.apk
10. Phonesky.apk (Play Store 4.4.21)
11. SetupWizard.apk
There are versions for 4.1 and 4.2, and 4.3 ROMs, and they should work on any device.
They don't contain any app that can be downloaded from the Play Store, like Gmail, Hangouts etc. But it contains everything necessary to use all Google services. It is based on the first minimal gapps for CM10 by Quarx. The old talk app is available as addons for each version, but they are not tested by me. If they stop working then let me know here (specifying which version, like 4.1, 4.2, 4.3 etc)
In case anyone wants to use Google TTS voice instead of Pico TTS, look here.
Find them here
Updated with new Play Store 4.1.10. CM10 version works on the latest SlimBean too.
http://www.androidpolice.com/2013/05/29/download-latest-google-play-store-4-1-10/
thanks a lot for this tejus!
just a question, I am using now the minimal gapps edited I found on the cm10.1 thread that is the only one with working swype stock keyboard for me, also in your minimal gapps package swype stock keyboard is working oob?
thanks again!
moly82 said:
thanks a lot for this tejus!
just a question, I am using now the minimal gapps edited I found on the cm10.1 thread that is the only one with working swype stock keyboard for me, also in your minimal gapps package swype stock keyboard is working oob?
thanks again!
Click to expand...
Click to collapse
I'll be happy if you can test it and tell me, I'm unable to test at the moment
But if I were to guess I'd say it does work because it contains a lib file related to the keyboard. It was in the original 4.2.2 Gapps, so I had kept it as it is. I think the gapps you found on CM10.1 thread might have been mine...
tejus.k.v said:
I'll be happy if you can test it and tell me, I'm unable to test at the moment
But if I were to guess I'd say it does work because it contains a lib file related to the keyboard. It was in the original 4.2.2 Gapps, so I had kept it as it is. I think the gapps you found on CM10.1 thread might have been mine...
Click to expand...
Click to collapse
I think so too..! also, I downloaded your new gapps minimal package, and compared the content of the app folder with the one I have, it seems exactly the same, except talk that is not present (not a big problem, I always remove it as well )
btw I will try your new package soon and report about they keyboard!
one last thing, but that could be very important! please see this:
http://forum.xda-developers.com/showthread.php?t=2300849
it is about the media app always running (download service process). after some research on the internet, it seems this app appears only after installing the gapps.
if that is the case, do you know what app could create this process, and if you find it, could be removed safely from the package?
that affects a lot of people, and if can be removed could be a great thing I guess! also, most important, some people reports less battery consumption when that service is not running! unfortunately it is a system app so it can be not greenified ;(
byeeeee
moly82 said:
I think so too..! also, I downloaded your new gapps minimal package, and compared the content of the app folder with the one I have, it seems exactly the same, except talk that is not present (not a big problem, I always remove it as well )
btw I will try your new package soon and report about they keyboard!
one last thing, but that could be very important! please see this:
http://forum.xda-developers.com/showthread.php?t=2300849
it is about the media app always running (download service process). after some research on the internet, it seems this app appears only after installing the gapps.
if that is the case, do you know what app could create this process, and if you find it, could be removed safely from the package?
that affects a lot of people, and if can be removed could be a great thing I guess! also, most important, some people reports less battery consumption when that service is not running! unfortunately it is a system app so it can be not greenified ;(
byeeeee
Click to expand...
Click to collapse
I'm sure nothing more can be deleted from these gapps without causing problems/disabling certain core features.
MediaUploader.apk is the only one that seems to be related, see here. But deleting this will disable Share via SMS, MMS, Email etc in the stock Gallery app. So not a good idea to delete this. If you personally don't use the stock Gallery then you can try deleting it using a root explorer and see if it fixes your problem.
tejus.k.v said:
I'm sure nothing more can be deleted from these gapps without causing problems/disabling certain core features.
MediaUploader.apk is the only one that seems to be related, see here. But deleting this will disable Share via SMS, MMS, Email etc in the stock Gallery app. So not a good idea to delete this. If you personally don't use the stock Gallery then you can try deleting it using a root explorer and see if it fixes your problem.
Click to expand...
Click to collapse
thanks! I will try as I don't use stock gallery. I hope it will remove sharing options only from stock gallery, and not for other apps (such as quickpic and others).
unfortunately I can not remove it.. when I try to delete the file /system/app/mediauploader.apk it says it can not be deleted (of course I am rooted, root access enabled in the file manager, and already kicked the app from running..)
will try to remove it from the package and reinstall from scratch..!
here is what I found out after a reinstall from scratch
I used your minimal package, but removed from it both phonesky.apk (play store) and mediauploader.apk
so far so good.. everything seems working fine!
I confirm swype keyboard works, but also sharing options are still available in gallery and all other apps! plus, it seems to me I don't see anymore media (downloadservice process) always in running apps, at least so far!
so it seems mediauploader.apk is not really needed actually and can be removed.. I will let you know if some problems will arise later, or I will notice something wrong
only thing is that in the sharing options I don't see anymore picasa, but that's not a problem for me, I don't use it!
as per the play store, I see two good points in removing it from the gapps package: I use app2zip to save all my apps, so now I can backup also play store with app2zip, and it won't conflict with another version of the app in /system
plus, being stored in /data, I can greenify it!! (also play store used to appear often in running processes..)
of course this way I will not be informed about updates, but I prefer to check manually when I wish to do so, instead of having the app often running even when I am not using it
thanks for your help and I hope this will be useful for some other people also
EDIT: media downloadservice is back again so it was not related to mediauploader... what the hell can be that??
it seems to me it appeared after running gmail for the first time.. but I will have to confirm that after some more investigations..
moly82 said:
EDIT: media downloadservice is back again so it was not related to mediauploader... what the hell can be that??
it seems to me it appeared after running gmail for the first time.. but I will have to confirm that after some more investigations..
Click to expand...
Click to collapse
Hmm okay..either way I think everything that can be removed has been removed from these gapps...mediauploader can be deleted by whoever wants to after downloading.
I am wondering whether to also upload (separately) the old Talk apk's for whoever wants it, IMHO hangouts is kind of slow.
tejus.k.v said:
Hmm okay..either way I think everything that can be removed has been removed from these gapps...mediauploader can be deleted by whoever wants to after downloading.
I am wondering whether to also upload (separately) the old Talk apk's for whoever wants it, IMHO hangouts is kind of slow.
Click to expand...
Click to collapse
I am in the tweaking days.. I searched many lists of apps/services on the web and trimmed down a lot cm build and also removed a few more things from your package.. I will reinstall from scratch and test if everything will work in a few minutes.. I keep fingers crossed.. will report back soon!
as per the talk app, I have always removed it from the package or later with a root explorer app as I don't use it.. btw I think many people may want it so probably if talk is not available anymore in the market could be good to upload it separately I guess
ok I did many attempts, reinstalls etc (play store really pissed me off.. actually I found out it can not be installed in /data, if you do so it seems to work but then when you try to update an app it FC....!!! so I had to do many attempts and in the end I integrated it again in the package as you did in orgin ) this is some general information I found out that can be useful for people who wants to trim things up:
1. ChromeBookmarksSyncAdapter.apk --> I didn't remove it, but if you don't import bookmarks from other PCs you can probably remove it
2. GoogleBackupTransport.apk --> I removed it, it is for google backup service (app, wifi passwords etc) that I never used
3. GoogleCalendarSyncAdapter.apk --> I didn't remove it, but if you don't sync calendars with gcalendar you can probably remove it
4. GoogleContactsSyncAdapter.apk --> I didn't remove it, but if you don't sync contacts with gmail you can probably remove it
5. GoogleFeedback.apk --> I removed it, and I have no problems so far (it is probably for reporting to google when an app FC, store feedbacks still work even without this)
6. GoogleLoginService.apk --> should not be removed, to login you google account
7. GoogleServicesFramework.apk --> should not be removed, needed for gapps and/or play store
8. MediaUploader.apk --> I removed it, it is just for picasa uploading/sharing option
9. NetworkLocation.apk --> should not be removed, it is for finding your location using mobile network instead of GPS
10. Phonesky.apk (Play Store 4.1.10) --> should not be removed if you want to use play store (if placed in /data problems arise!!)
11. SetupWizard.apk --> should not be removed, first boot wizard
also, as I don't use gtalk at all, I removed libgtalk_jni.so and libgtalk_stabilize.so inside "lib" folder..
my conclusion is that I can just confirm for most cases your package is perfect, so it is probably better to leave it exactly like this, and just in case people have different needs can modify it.. the info I added above should be helpful in this case!
bye!
ps. doing all these attempts I can now understand how long it could have taken for you to find the smallest and most stable configuration for the gapps, so I can just say MANY THANKS TO YOU!! :good:
pps. looking at different lists on the web, and also with some findings I did by myself, I gathered information about almost all the apk's present in the cm builds, if that can be useful for someone I could open a new thread and prepare a list similar to the one above (file name and what the app does, to know if it is safe to remove it or not) .. believe me there are many lists on the web but to find out (almost) all the apps and their purposes you must look at many of them and make a mix!! also some were not present in any list at all and I had to personally find what they do!
moly82 said:
ok I did many attempts, reinstalls etc (play store really pissed me off.. actually I found out it can not be installed in /data, if you do so it seems to work but then when you try to update an app it FC....!!! so I had to do many attempts and in the end I integrated it again in the package as you did in orgin ) this is some general information I found out that can be useful for people who wants to trim things up:
1. ChromeBookmarksSyncAdapter.apk --> I didn't remove it, but if you don't import bookmarks from other PCs you can probably remove it
2. GoogleBackupTransport.apk --> I removed it, it is for google backup service (app, wifi passwords etc) that I never used
3. GoogleCalendarSyncAdapter.apk --> I didn't remove it, but if you don't sync calendars with gcalendar you can probably remove it
4. GoogleContactsSyncAdapter.apk --> I didn't remove it, but if you don't sync contacts with gmail you can probably remove it
5. GoogleFeedback.apk --> I removed it, and I have no problems so far (it is probably for reporting to google when an app FC, store feedbacks still work even without this)
6. GoogleLoginService.apk --> should not be removed, to login you google account
7. GoogleServicesFramework.apk --> should not be removed, needed for gapps and/or play store
8. MediaUploader.apk --> I removed it, it is just for picasa uploading/sharing option
9. NetworkLocation.apk --> should not be removed, it is for finding your location using mobile network instead of GPS
10. Phonesky.apk (Play Store 4.1.10) --> should not be removed if you want to use play store (if placed in /data problems arise!!)
11. SetupWizard.apk --> should not be removed, first boot wizard
also, as I don't use gtalk at all, I removed libgtalk_jni.so and libgtalk_stabilize.so inside "lib" folder..
my conclusion is that I can just confirm for most cases your package is perfect, so it is probably better to leave it exactly like this, and just in case people have different needs can modify it.. the info I added above should be helpful in this case!
bye!
ps. doing all these attempts I can now understand how long it could have taken for you to find the smallest and most stable configuration for the gapps, so I can just say MANY THANKS TO YOU!! :good:
pps. looking at different lists on the web, and also with some findings I did by myself, I gathered information about almost all the apk's present in the cm builds, if that can be useful for someone I could open a new thread and prepare a list similar to the one above (file name and what the app does, to know if it is safe to remove it or not) .. believe me there are many lists on the web but to find out (almost) all the apps and their purposes you must look at many of them and make a mix!! also some were not present in any list at all and I had to personally find what they do!
Click to expand...
Click to collapse
Oh it didn't take me long because, like I said in op, it is based on quarx's minimal gapps. He spent time figuring out what to remove, thanks should go to him
I'll add a link to your post in the op.
Sent from my MB526 using xda app-developers app
just for your info, after some more attempts i found out the process: media > DownlodService is related to both gapps and Downloadprovider.apk
if I remove Downloadprovider.apk, that process doesn't appear anymore, but I get gapps FC's (and very probably will not be possible to download anymore things from the browser and/or play store)
so in conclusion it seems to me we have to live with that process running, and that is not possible to really get rid of it safely..
EDIT: also, it seems to me it starts appearing when you run gmail for the first time.. so if you use gmail I guess we must live with that process always running even if you disable automatic sync like I always do
wow did you change your nick? I didn't know it was possible! :silly:
moly82 said:
wow did you change your nick? I didn't know it was possible! :silly:
Click to expand...
Click to collapse
Oh and since you seem to like to disable as many unnecessary apps as possible, you can try and disable 'ApplicationsProvider.apk'. It will only break Google Now searches for apps that are installed on your device AFAIK. I've disabled it on CM10.1 and I don't use GNow, haven't noticed anything amiss.
thanks my dear will remove it immediately and see what happens thanks!
EDIT: I went for removing it and actually i noticed i have already deleted it lol! i will post the list of all the apps i usually remove before flashing a rom soon maybe someone could be interested
EDIT 2: this could become the tuning thread..
.. here is what i remove always from the cm10.1 and minimal gapps package zips:
<<From cm10.1 ROM zip..>>
/system/media/video/*
/system/tts/*
/system/usr/srec/*
/system/fonts/DroidSansFallback.tff
/system/fonts/MTLmr3m.tff
/system/fonts/NanumGothic.tff
in /system/media/audio i only leave alarms, notifications and ringtones i need (six in total) and remove all the others
*for the part above, credits go to @Nbsss, see here: http://forum.xda-developers.com/showpost.php?p=41074866
below is my contribute..
in /system/app i delete all the following: (with some explanations for each app)
Apollo.apk (music app)
ApplicationsProvider.apk (somewhere I saw that that it "Provides the list of installed apps to Market", but market is working fine here even without that, and I can also correctly see the list of my installed apps)
AudioEffectSettings.apk (relevant settings, I don't use them, if removed settings will FC if you try to open those audio effect settings)
BackupRestoreConfirmation.apk (for synced google settings, I never used it)
BasicDreams.apk (wallpaper)
CellBroadcastReceiver.apk (relevant settings, I don't use them, if removed settings will FC if you try to open those cell broadcast settings)
CMFileManager.apk (I use ES File manager instead)
CMUpdater.apk (I have never used updater, just flash flash new roms when they come out)
DSPManager.apk (I don't use it)
Email2.apk (I only use gmail)
Exchange2.apk(I only use gmail)
Galaxy4.apk (wallpaper)
HoloSpiralWallpaper.apk (wallpaper)
HwaSettings.apk (I always leave HWA on for all apps an never had any problems, so no need for this)
InputDevices.apk (never understood what is this for exactly, but removing it is safe here)
LiveWallpapers.apk (to choose between live wallpapers, I don't use them)
LiveWallpapersPicker.apk (to choose between live wallpapers, I don't use them)
MagicSmokeWallpapers.apk (wallpaper)
NoiseField.apk (wallpaper)
PhaseBeam.apk (wallpaper)
PhotoTable.apk (wallpaper)
PicoTts.apk (no need, maps+audio directions work perfectly fine even without this)
Provision.apk (setup wizard, not used, using the one inside the gapps package instead)
QuickSearchBox.apk (google search box, I don't use it)
Stk.apk (sim toolkit app, I don't use it)
Term.apk (old version of terminal emulator, I always install the latest one from play store instead)
ThemeChooser.apk (I never change themes)
ThemeManager.apk (I never change themes)
VideoEditor.apk (it used to always crash, at least in previous builds, btw I don't use it)
VisualizationWallpapers.apk (wallpaper)
VoiceDialer.apk (I don't use it)
VpnDialogs.apk (I don't need it)
<<From minimal gapps zip..>>
GoogleBackupTransport.apk (for google backup service that I never used)
GoogleFeedback.apk (it is probably for reporting to google when an app FC, store feedbacks still work even without this)
MediaUploader.apk (it is just for picasa uploading/sharing option)
libgtalk_jni.so and libgtalk_stabilize.so inside /lib, as I don't use gtalk/hangouts
.. doing like that i remain with more than 80Mb free in /system
byeeee
Tnx moly82 for your useful list.
I use this script http://forum.xda-developers.com/showthread.php?t=1827817 made for Galaxy S3 for cleaning my Defy +. Instead ROMCleaner_user.txt file from that page, I use a custom one made for Defy with options proposed by U in previous post. I'll atached the file to this post so anyone can use it.
But according to personal preference can be changed very easy with Notepad++ .
does this work for all phones like my desire s?
Px80 said:
does this work for all phones like my desire s?
Click to expand...
Click to collapse
Sure it does, nothing device specific in this. Just goo.im gapps with lots of stuff removed.
Sent from my MB526 using xda app-developers app
System: Android 2.3.3 (Gingerbread) - Discontinued May 2, 2014
About:
This is a fork of the DSC ROM, which is based on the Olleh KT 407 ROM. Its genesis came about as a result of a request by lordofazeroth (here) asking to delete all unnecessary apps from /system/app in the next release. My answer was matter of fact: to do it himself rather than asking _n0p_ to do it. This was because I had already created a private version of DSC for my needs and felt that if people really wanted apps out they should take them out themselves.
However, thinking back on it, lordofazeroth's request wasn't wholly out of line. While getting rid of some apps, e.g. HTML Viewer, made no sense, one thing that did make sense was removing the Google apps from /system/app. This was in keeping with Google's direction regarding the apps. Starting around the time Gingerbread was released, Google began to remove most of the Google apps from new versions of Android and making them available for download via the Play Store. Looking in an ICS Google apps package for AOSP ROMs, the only Google apps remaining in the package that could also be downloaded from the Play Store are Google Talk (now known as Hangouts) Google Search, and Voice Search. I fully expect that future Google Apps packages for AOSP ROMs would only contain the Play Store, Google Services Framework, the minor apps that aren't on the Play Store (Google Gallery, News & Weather), and support files.
While getting rid of the apps from /system/app made sense, a lot of people still associate a complete Android experience with having the apps and didn't want to lose them. Fortunately, the DSC ROM has a solution in the form of a firstboot.zip whose contents are extracted and installed while the system boots the first time. It was a simple matter to move the Google apps currently in /system/app to the firstboot.zip and have them installed when the ROM is installed. This makes the end user expecting the Google apps preinstalled happy because the apps are present. And if an end user doesn't wish a particular app to be installed, e.g. Maps, they can completely uninstall it and not be left with the original version in the ROM.
So, based on this idea, I put together my own version of the DSC ROM with this shift in design and am releasing it to the public. Since the ROM is essentially DSC with a few minor changes, it should function as well as DSC does. It's hoped that if _n0p_ releases a new version of DSC that this design change can be folded back into DSC.
Differences between DSC and the Traveller DSC fork:
DSC 2.3's updates are included in the ROM, thus no need to apply patches after installing the ROM.
The DSC 2.3 kernel was replaced with the swap-enabled version of the same kernel (as of version 2.3.4).
SuperSU replaces SimpleSU. SimpleSU's binary isn't recognized as valid by certain apps, e.g. Busybox Free.
The Traveller ICS Theme and the Stargate boot animation are now the default. wway's Gingertrue theme and Ace32's boot animation are available as a flashable theme zip.
Zeam has been replaced with HoloLauncher.
The CM7 File Manager app has been added to /system/app.
Gmail, Hangouts, Maps, Quick Search, Voice Search, and YouTube are all in dsc_firstboot.zip instead of being embedded in the /system directory.
All Google apps, including the Play Store, were updated to their latest available versions.
Google Play Services and Google Street View are new to the ROM. If after uninstalling Google Play Services the app reappears in your app drawer, then Google has pushed the app back to the device. Please do not complain on the forums about this, as it is expected behavior and not a fault of the ROM or device.
Antutu CPU Master Free, WiFi Reassociate, Superdim, System Panel, and ClockSync were all removed from the ROM. In using DSC I have never encountered a problem that required any of these apps, and I replaced Antutu with the XDA version of SetCPU. All should be available through the Play Store if desired or needed, except for the XDA version of SetCPU.
Ghost Commander was removed because the CM7 File Manager app was included in /system/app. Ghost Commander should still be available through the Play Store.
The Streak FM Radio app was replaced by the March 11th version of Spirit FM Free. The limitations of the Streak FM Radio app are well known (no volume control). The Spirit FM Free app is apparently limited to either Blended Audio or Mono sound - it's not clear which - but at least the volume can be controlled. The March 11th version of Spirit FM Free is also the last version that supports the Dell Streak.
ZRAM Status was added to monitor ZRAM usage in the ROM (as of version 2.3.5).
Bugs:
Google Maps may cause excessive battery drain. Freeze Maps or uninstall it if this issue is encountered.
Arabic and Hebrew text in Aroma may appear backwards due to lack of right to left support.
Touchscreen support in Aroma is erratic. Scrolling using the touchscreen does not function, and it may require a few taps to get selections to properly register. As an alternative, the volume controls and the camera button can be used to navigate and select items. This is likely a hardware issue and not fixable in Aroma.
Tips:
Disable notifications in SuperSU for a clean look and to speed up the boot process.
SuperSU will receive updates from the Play Store. To save storage space convert the update to a system app.
Undervolting the CPU using the DSC CPU Voltage Configuration app is highly recommended to maximize battery life.
HoloLauncher has the ability to hide apps in the app drawer. If you know you're never going to use a particular system app, e.g. the email client, hide it instead of deleting it from the ROM.
Customize dsc_firstboot.zip to meet your needs. For example, if you use Google Earth, rename the APK file to com.google.earth.apk and add it to dsc_firstboot.zip.
Google Car Home was left in /system/app because if uninstalled it cannot be downloaded from the Play Store.
The original release of the Hangouts 2.0 app (from Android 4.4) had a bug which allowed it to work on Gingerbread. If wishing to use Hangouts in place of the stock Messaging app, set the app to not be automatically updated in the Play Store or you will lose SMS capability when the app updates.
Changelog:
2.4.6:
UPDATE: Hunderteins has released another SSL Ciphers update, this time around to boost speed and security of HTTPS connections by implementing new encryption and authentication algorithms.
UPDATED APPS: Google Play Services, Hangouts and YouTube.
Older Revisions:
2.4.5:
UPDATE: OpenSSL firmware updated to fix the Heartbleed bug.
UPDATED APPS: Google Play, Google Play Services, Hangouts, Maps, SuperSU, and YouTube.
2.4.4
UPDATE: HoloLauncher updated to 2.11. Now has a color theming option similar to what is available in KitKat.
BUG FIX: Hebrew language in Aroma now displays.
BUG FIX: Grammar fixes for some screen text in Aroma.
Because 2.4.4 is being released so soon after 2.4.3, I'm leaving 2.4.3's updates visible as well as providing a patch for current users to install rather than downloading the entire ROM and installing it again.
2.4.4 Update.zip - 819.16 KB
2.4.3
NEW: PDroid for Arabic users now available.
UPDATES: SuperSU, Flash Player, YouTube, Hangouts, Google Play Services, and AFWall+. The release of Flash Player included here is the final release from Adobe. There will be no further bug fixes or updates.
UPDATE: Aroma Installer updated to 2.70RC2. This update restores touch support to the installer, which was missing in 2.51 as well as allowing the user to quit the installer at any point prior to installing Traveller DSC or its features.
BUG FIX: Fixed the issue with Arabic support not properly installing. For Arabic support to work the base ROM (and any added features) must be installed prior to installing Arabic support. This means you will have to run Aroma twice to enable Arabic support. The first time will be to install the ROM. After installing the ROM and letting everything in dsc_firstboot.zip install, reboot into the recovery and run Aroma the second time. Select the Arabic menu choice and install those options on top of Traveller DSC.
After selecting Arabic in the Language & Keyboard options in Settings, the very first time the power button is used to shut down the Streak the device will hot reboot and attempt to cycle through the boot animation. It will fail and then hot reboot a second time. This second time the device should boot to the launcher.
2.4.2
UPDATE: Play Store updated to 4.5.10.
UPDATE: Clock font changed to the version used in Android 4.4, resolving an issue with a portion of the clock being cut off when the pattern lock is used.
UPDATE: Common fonts used in both Android 2.3.3 and 4.4 were updated to the Android 4.4 versions.
2.4.1
BUG FIX: Replaced the tabbed browser with the original stock browser to resolve a force close issue with Voice Search. Clearly the tabbed browser wasn't quite ready for prime time.
2.4.0
NEW: Installation is done via the Aroma Installer. There is no touch support for the Streak, so the volume controls and the power button must be used to navigate. As a result of this change, all the various modifications available have been rolled into the zip file, meaning there will be no separate downloads needed for this version of Traveller DSC. The increase in size of the zip file also means that MediaFire cannot be used. Dev-Host will be used instead.
NEW: A new version of the zRAM app was compiled from its sources, with a black background and with memory readouts expressed in MB rather than bytes. It is now also a system app.
NEW: The stock browser is now a version of Lightning Browser compiled from source, with a custom dark theme to fit the rest of the ROM.
UPDATED APPS: AFWall+, Google Play Services, HoloLauncher, SuperSU, and YouTube.
UPDATE: Roboto Condensed is now the default font, for that Android 4.4 look.
UPDATE: Arabic patch users can now fully benefit from the SSL Cipher improvements due to a fix in framework.jar.
BUG FIX: In QuickPanel, the Auto-brightness indicator can now be clearly distinguished from the maximum brightness indicator.
BUG FIX: The "System Updates" option in Settings > About phone now links to this thread instead of the DSC thread.
BUG FIX: The "Build Version" option finally had a version bump, to 2.4.
NOTE: Gingertrue users will not have the new browser installed. While the browser is available for download here, it may not install. Gingertrue users wishing to use the tabbed browser will need to convert it to a system app using an app like Apps2ROM. The other option would be to install a copy of Lightning Browser.
NOTE: The browser may force close after exiting. The cause is unknown at this time, but may also affect Lightning Browser, since the former was compiled from the source of the latter.
2.3.10
SuperSU reverted to 1.65. See explanation here.
Fixed bugs caused by developer error when adding ciphers patch.
Default wallpaper was changed.
Changelog for versions prior to 2.3.10 was removed.
Links:
Flashing Instructions
407 ROM [Dev-Host Links Removed]
Mega
ROM Download
DSC "Flash Me Before Installing" Pack
How to add your files to the Traveller DSC ROM
While the Traveller DSC ROM does change several things in the system, notably replacing SimpleSU and Zeam with SuperSU and HoloLauncher, its biggest "selling point" if you will is the ability to customize the app package that is installed with the base ROM. The DSC ROM includes a zip file located in /system/etc named "dsc_firstboot.zip". After DSC is installed and the system rebooted, during the Google account setup and for a short period of time afterwards a script is run that installs all the apps found in dsc_firstboot.zip.
The base DSC ROM included in its dsc_firstboot.zip the following apps: Adobe Flash, AnTuTu CPU Master Free, WiFi Reassociate, DSP Manager, Ghost Commander, Maps, YouTube, Droidwall, Dell Swype, DSC Wallpapers, Superdim, SystemPanel, ClockSync, and Streak FM Radio. Many of the Google apps remained in the ROM. For Traveller DSC, as already mentioned in the first post in the thread, all the Google apps except for the Play Store and Car Home were pulled from the ROM and stored instead in dsc_firstboot.zip. This is because all of these apps had new versions in the Play Store and thus there seemed to be no reason to keep old versions in /system/app. At the same time I changed up the apps package.
Traveller DSC includes in dsc_firstboot.zip the following apps: Adobe Flash, DSP Manager, Maps, GMail, Google Play Services, Quick Search, Street View, Voice Search, YouTube, Droidwall, Spirit FM Free, Dell Swype, zRAM Status, and DSC Wallpapers.
Traveller DSC encourages customization. I want you to make this ROM your own. If you want to delete the Google apps, go ahead. If you want to do what I did and add Google Music, you can do that too. This brief tutorial explains how. But keep in mind the following: dsc_firstboot.zip cannot be larger than the remaining space in the /system partition. If the file is too large the Streak may freeze at the Dell logo or end up in a boot loop. If this happens, remove apps until the file is smaller than the remaining space in the /system partition, then install the ROM again.
Tools required - PC: WinZip, WinRAR (preferred) or 7-Zip. Do not use the built-in Windows zip utility as it corrupts the zip file.
Tools Required - Streak: An app backup utility such as App Backup & Restore.
Optional - PC users with Chrome: APK Downloader extension.
Extract dsc_firstboot.zip from the Traveller DSC ROM.
On the Streak back up the installed app you want to add using an app backup utility. Ideally, when backing up the app you do not want its user-friendly name, but the name Android associates with the app, e.g. com.google.android.gm.apk instead of GMail.apk. There is a means to get the Android name of the app, using the Play Store on the PC.
Connect the Streak to the PC and download the backed-up app to a directory of your choosing.
Rename the app if necessary. See below.
Open up dsc_firstboot.zip with WinZip, WinRAR, or 7-Zip. Simply drag and drop the new app into the dsc_firstboot.zip window. The file will be compressed and added to the rest.
To add the new dsc_firstboot.zip to the ROM, open up the ROM's zip file, navigate to /system/etc, then simply drag and drop the new zip file into the directory. The ROM's zip file will update itself, overwriting the old zip file with the new one.
Copy the new ROM file to the Streak and install the ROM.
If the app on the Streak carries a friendly name, open up a browser window on the PC and head to the Play Store. Search for the app in the Play Store and look at the URL. The Android name of the app is found within the URL. For example, if wanting to embed Kongregate Arcade into dsc_firstboot.zip you would find it in the Play Store. The URL would be play.google.com/store/apps/details?id=com.kongregate.android.kongarcade. The Android name is found after /details?id= in the URL, thus the Android name for Kongregate Arcade would be com.kongregate.android.kongarcade. Rename the apk file from Kongregate Archade.apk to com.kongregate.android.kongarcade.apk and then follow steps 5-7 above.
If using Chrome, use the APK Downloader extension and download a copy of the app directly from the Play Store to eliminate the need to use a backed-up version of the app on the Streak. Google recently changed things and now all files downloaded from the Play Store using APK Downloader have a filename consisting of a random number, so it's necessary to give the downloaded file the correct name. When the Windows prompt appears asking for a location to save the file in, rename the downloaded file to the name referenced in the URL, e.g. com.kongregate.android.kongarcade.apk. From there, follow steps 1, 5, 6, and 7.
NOTE: This tutorial may be revised from time to time in order to clarify details or simply to make things easier to understand.
hello, thanks for the rom. i came from cm7 based rom. if i want to try this rom, can i just flash the zip just like usually ? I read instruction link, confused about flash_me, just seems lots of step to flash a DSC rom. My baseband already 406.
Thanks.
Sent from my Dell Streak 5
Powered by INDOSAT
The provided baseband files improve the voice quality but are not essential to getting the ROM to work. As this is merely a tweaked version of DSC I put out as a proof of concept, everything you know about DSC still applies.
I'm not sure what's the difference between the pdroid version and basic.....I don't know which one to try
Sent from my Dell Streak using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1357056
PDroid is a privacy add-on.
Had a data wipe after I did a reboot. Unfortunate as it seemed nice as a "update" for DSC 2.3.
Explain please? I've never had a data loss issue in the entire time I've been running this ROM (several months before I released it).
Strephon Alkhalikoi said:
Explain please? I've never had a data loss issue in the entire time I've been running this ROM (several months before I released it).
Click to expand...
Click to collapse
Don't take it as a slight on your ROM, personally I think it's more of an issue with my device. I did fresh install over DSC 2.3 after that I had a data wipe after a random restart. With this ROM I'd rebooted after I changed default orientation to portrait in DSC config resulting in complete wiping, i.e. upon restart I was welcomed with the Welcome to Dell Streak touch here to continue screen.
I wasn't taking your comments in a negative fashion. Sorry if I gave that impression.
I don't change the default orientation so I've not noticed that. One thing I did notice is that ever since I changed the baseband in my Streak to 366 WiFi has never failed to initialize after waking up the Streak. The "beta" versions of this ROM I ran using the 406 baseband and often had to engage and disengage airplane mode to wake up the WiFi. It still doesn't stop me from having an occasional spontaneous reboot, but it's an improvement. So, I recommend using the 366 baseband, which can be installed using the DSC "Flash Me Before Installing" pack.
Thanks for sharing... I am downloading the files and will read thru all the instruction before proceeding...
I have place back the picture to show the problem.
For some reason XDA is adding <br /> to the end of the links here, which is why people were getting the request for a decryption key. I've edited my post to fix the links.
ROM updated to correct the chef's not realizing that the version of Spirit FM he added did not support the Streak any longer.
Currently testing one of _n0p_'s older versions of the kernel to see if replacing the kernel fixes the spontaneous reboot issues I and a couple other people have been getting at random times. If this does fix things, I'll provide an updated ROM. If anyone wants to try this out, you can download the u28 (DSC 2.0 release) boot.img from _n0p_'s DSC thread here.
Some updated information available here.
Any update on your test results @strephon
Sent from my Dell Streak using Tapatalk 2
ammujee said:
Any update on your test results?
Click to expand...
Click to collapse
Check the DSC thread. I reported my results there.
Just for anyone waiting for an update.. @Strephon Alkhalikoi has updated an 'all in one' fixed version 2.3.3 in the OP.
Thanks. :highfive:
I'm having problems downloading from the MEGA links on the first page... does anyone have any mirrors set up?
I had no trouble. Possibly an Internet issue?
OK, I successfully grabbed the rom and the "Gingertrue Theme and Phoenix Boot Animation"
...however when attempting to install the theme zip I got a failure. (Status 6)
IntroductionMost Android devices come with bloatware in some form or another. At best, nearly all of those apps do nothing but take up precious space. At worst, they get in your way of working productively and efficiently. Wouldn't it be nice if getting rid of those apps was just a matter of uninstalling them?
Problem is, there is no easy way to completely rid yourself of bloat—unless you have a rooted device, in which case, completely jettisoning that bloatware is actually possible. But even if you don't have a rooted device, all is not lost. I want to introduce you to some tools that will help you rid yourself of that bloatware—or hide it from sight on un-rooted devices.
Before I introduce you to the apps, I have to remind you to always have a full backup of your device and to use caution when deleting apps. Do not delete critical system apps—otherwise you'll wind up with a non-functioning phone. End standardized warning.
I am going to share Bloatware Removal Script especially designed for Android Marshmallow. You can use this script after flashing Custom ROMs on your device. This script will remove main apps like CM File Manager, Launcher3, CMHome, AOSP Browser, AOSP Gallery, AOSP Camera etc. I have also made a flashable zip of Extra Apps that will install Es File Manager, Gallery Extra by Cyanogen, AudioFX by Cyanogen, ScreenCast by Cyanogen, Google Now Launcher etc. on your system partition.
Click to expand...
Click to collapse
Disclaimer
Flash this at your own risk. I am not responsible for any damaged or bricked devices.
Click to expand...
Click to collapse
Advantages of Removing Bloatwares
Free up System
Get rid of non-usable apps
Better RAM Management
List of Apps That the script will remove from Your Device
system/app/Apollo
system/app/BasicDreams
system/app/Browser
system/app/Camera2
system/app/Calendar
system/app/CellBroadcastReceiver
system/app/CMFileManager
system/app/CMHome
system/app/CMWallpapers
system/app/DashClock
system/app/DSPManager
system/app/Eleven
system/app/Email
system/app/Exchange2
system/app/FileManager
system/app/Galaxy4
system/app/Gallery2
system/app/HoloSpiralWallpaper
system/app/LiveWallpapers
system/app/MagicSmokeWallpapers
system/app/Music
system/app/NoiseField
system/app/PhaseBeam
system/app/PhotoPhase
system/app/PhotoTable
system/app/VideoEditor
system/app/VisualizationWallpapers
system/app/VoicePlus
system/app/WhisperPush
system/priv-app/Launcher3
system/priv-app/MusicFX
system/priv-app/AudioFX
system/priv-app/PicoTts
system/priv-app/talkback
Extra Apps[Flashable via Custom Recovery] includes[Optional] you can directly install these apps normally by unzipping the "Extra_Apps.zip"
Google Chrome
Google Camera
Google Now Launcher
Google DeskClock
Google Play Music
Gallery Next by Cyanogen New
AudioFX by Cyanogen New
Audio Recorder by Sony Communication
ScreenCast
Es File Explorer
Installation Procedure
Flash Custom ROM
Flash G-APPs
Reboot Your Device
Go to Custom Recovery
Flash "Bloatware_Removal_Script_For_MM.zip"
Flash "Extra_Apps.zip" [Optional]
Wipe Cache and Dalvik Cache
Reboot and Enjoy!
Download Section-> Bloatware Removal Script: Download from here
-> Extra Apps [Optional]: Download from here
Tested on: Karbonn Sparkle V with OCT_OS_MM ROM
Credits: Google, Sprout4 Developers and @jajb
Press Thanks If I Helped You
meprakash_pyc said:
...
Click to expand...
Click to collapse
Hey, thanks for sharing :good:
I noticed this script shares 98% of the code from the one from this thread (download). If you used this (or any other) script as a base, it'd be nice if you'd give credit. This is no accusation by all means, just noticed the similarity.
P1nGu1n_ said:
Hey, thanks for sharing :good:
I noticed this script shares 98% of the code from the one from this thread (download). If you used this (or any other) script as a base, it'd be nice if you'd give credit. This is no accusation by all means, just noticed the similarity.
Click to expand...
Click to collapse
done
Can i use it for lollypop (Flyme OS)
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
Updated on July 3, 2018:
(reason in post #636)
MicroG in post #396, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
Open GApps in post #416, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible. It also performs a one time nice Google setup of the unit, beginning with language, account, and so on.
Note to all using this firmware for the first time: since it is differently partitioned from what you had before, you must also perform a wipe all in recovery, ideally just before the first startup (to avoid wasting time), or at any time now.
WARNING: MicroG Core and LP don't work well: contacts are not seen from apps like Hangouts, Google/Voice Search, while True Contacts needs local loading of profile & contacts - from vcards on the internal SD. Therefore I strongly recommend the Open GApps version!
Note also that with the MicroG version, the gms core app must be configured, and Hangouts' service called NetworkConnectionCheckingService must be disabled, for Hangouts to work:
Code:
pm disable com.google.android.talk/com.google.android.apps.hangouts.service.NetworkConnectionCheckingService
TomTom GO storage support is explained in post #45.
TT GO spoofing is in post #392.
Poweramp's early start&restart is also supported by default.
Phone calls via a BT connected phone could be dialed by (always) selecting the MTC Service(aka Headunit), as the preferred dialer.
MTC Sound direct sound control is readily supported, if the associated hardware mod is also done.
Automatic screen brightness control based on location&time is also implemented by default.
Blank logo kernels are in post #600 (get them while they last).
Developer Mode in post #332.
Firmware is also rooted and xposed.
To those who make outlandish claims about this firmware: they are either trolls or firmware is not for them. However firmware supports all rk3188 MTCB or MTCC units. Make your own judgement, and don't get scared away.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
===
Here's another one: in principle, unless an unlikely bug is reported, I don't reply in this thread to users who are not listed as saying thank you to this post.
===
Mod Edit :- Content Removed
Thanks @dsa8310 .. your rooms are great .. I installed microg rom yesterday . Works great . Will try the new one soon. The only question I have is the performance of both roms similar coz I have 1GB Ram
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396.
Open GApps in post #416.
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Hi @dsa8310, is it possible to find what version of your firmware that I have installed in my radio. I think I updated yesterday, but not sure if it the recent one that you posted yesterday.
Maybe a tall tell signature or something to look for.
Again, thanks for your work on the firmware. And I hope this section works out for you.
Wayne
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
As usualI I ll be putting the ROMs on the fileserver for everyone.
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
dsa8310 said:
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
Click to expand...
Click to collapse
I have the 6/28 one.. MicroG I guess. Getting Gapps..
Thanks bud.
Like to donate as well..
EagleSoldier said:
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
Click to expand...
Click to collapse
I now use the (pico) Open GApps enabled version. I like it because I don't have to configure things and it is 100% Google compatible. I dislike it because of Google ads' undisturbed presence, unlike the MicroG version that avoids them, partially, at least for my set of apps.
There might be observable differences in their footprint size (necessary RAM) and load of system (background tasks). I can't say for sure, since I have a 2GB RAM (upgraded) unit. Furthermore, I run the same set of apps most of time: Poweramp and TomTom GO which have the same heavy requirements (TT mainly).
Perhaps 1GB units should use MicroG while 2GB ones could afford the Open GApps version.
A technical comparison between versions could be done, in a terminal (termux), with commands like "free -m" (free memory) and "uptime" (busybox uptime) (for load average); "busybox ps", too, if implemented.
But, ultimately, it's a matter of feeling: if you feel that one version is more responsive, feel free to use it.
(switching back and forth is facilitated by the same partitioning, though going through a wipe all in recovery seems necessary)
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
ankerede said:
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
Click to expand...
Click to collapse
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
dsa8310 said:
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
Click to expand...
Click to collapse
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
ankerede said:
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
Click to expand...
Click to collapse
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396, and here:
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
Open GApps in post #416, and here:
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
elyl said:
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
Click to expand...
Click to collapse
No, they are not.
It's possible, but then uninstall by hand three apps: com.google.android.gsf, org.microg.gms.droidguard, FakeGapps1.1, and then reboot.
Hi dsa,
i'm on your latest microg version of your firmware with the playstore. But when i open the playstore and try to connect i get this error: [RH-01]
any idea?
problem iam facing now i cant play music while using google maps, any help?
dsa8310 said:
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
Click to expand...
Click to collapse
I give it a + for GApps. Still works nice with Google Play and able to use what you paid for with no issues.
Finally got more play time with the latest and I like it.. Using 1G, no upgrade memory at all..
Still need to add a few more apps.. but good to go..
Thanks @dsa8310
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
dsa8310 said:
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
Click to expand...
Click to collapse
Exactly what I did. A setup that I have never seen before had to be done. Great Job.
It's Open GApps' merit, not mine. Once the setup is done, everything else falls into place.