Related
Here we go !
Starting point is from CyanogenMod Captivate forum and some improvement were added here and there. Credits are recalled and came from this thread : [SCRIPT][CM7/9] /datadata/ low storage notification lagless fix - init.d script.
Background :
CyanogenMod (CM) based roms on our I9000 (and brothers) uses a small and fast flash chip to store application datas. This make the rom smooth and sweet ... This chip is mounted as /datadata and is about 170Mo.
With a lot of apps (or apps storing lots of stuff there) we faced a "Low storage" notification and our phone becomes laggy.
The first idea was to move this /datadata to /data (about 2Go) whose have a lot of free space. This works but the phone became laggy.
Then some others devs think about moving back to /datadata frequently accessed files (sqlite database and xml preferences files). First as scripts part then as flashed zip file. The phone becames smoother but not like a "vanilla" CM rom. This is the 1103 datafix in thread linked previously.
An xda user suggested to let on /data only library files and move back all other stuff to /datadata. These lib files are only accessed (when used by users) in read mode so the ext4 /data partition is efficient in this way and phone becomes smoother as "vanilla" CM roms. This is the 2903 datafix I made and post in previously linked xda thread.
But with this latest datafix, applications cache are stored in /datadata and recent Google apps (like Chrome) fulfilled it quickly : the "Low storage" notification is back !
Next solution :
Like 2903 datafix, only libraries ("lib" and "libs" subdirectories) stay on /data by default.
BUT unlike it you could choose which apps will also store their cache in /data. And this is REVERSIBLE : if one of selected app becomes laggy you could move back its cache onto /datadata
How to use it :
Make a nandroid backup
Just grab the zip file and flash it in recovery
At reboot, it will revert previous datafix (if there is one) and apply this one. So first boot could take more time (5 minutes max) than "normal" boot.
It also creates a "datafix" directory in /data/local with two files : "move_cache.txt" and "skip_apps.txt".
Just edit the first file (root needed) to add apps whose cache will go back to /data at next boot :
Code:
com.android.chrome
org.mozilla.firefox_beta
will put Google Chrome and Firefox Beta cache on /data. All others apps cache will go to /datadata.
If you want Firefox cache to go back on /datadata, just remove its line in the file and reboot.
In the "skip_apps.txt" file, just put apps you want to fully stay on /data/data. If apps was previously moved to /datadata by the datafix it won't apply; you have to add its name in "skip_apps.txt" file after installing it and before rebooting the phone. On the other hand, if you remove the apps name from "skip_apps.txt" file all but libraries will be moved to /datadata at next reboot.
Requirements :
Samsung Galaxy S based phone (GT-I9000, Vibrant, Fascinate, Captivate, etc.)
CM based rom (including CM7/9, MIUI and maybe ao(k)sp etc.)
Kernel that supports init.d scripts (latest CM9 nightly support it)
Busybox installed
A fresh nandroid backup
FAQ :
Q : There is 2 zip files, who's the good one ?
A : It depends of your kernel. With stock CM9 kernel use the Datafix20120521. With others like Devil etc., use the SDatafi20120521. The only difference is between the script name : 30datafix or S30datafix. Some recent kernels add a "S" before the init.d script name. Why ? No idea !!!
Q : Will this wipe my phone ?
A : No, it should not delete any data on your phone. But as it's not tested with every phone xda user have it's a good idea to have a fresh nandroid backup
Q : Do I need to reflash the zip file ? When ?
A : The datafix will be erased each time you upgrade/change your rom (including Nightly Builds) or your kernel (many of them "clean" the init.d directory). But if you don't install lots of apps after upgrading you don't really need to install the datafix again : without full wipe, a nandroid restore or an Odin full installation te datafix will stay on.
Q : Is there something to do when backuping my apps ?
A : Nandroid should work without specific option; Titanium Backup users should tick the Preferences > Troubleshooting settings > Follow all symbolic links option. I don't use other backup apps ...
Q : Can I use this on Samsung based rom ?
A : No ! And it's irrelevant cause Samsung roms don't have the "Low storage" issue !
Q : I'm using Slim ICS rom, do I need some busybox fixer etc. ?
A : I don't use SlimICS but all commands in my script call busybox directly so it should work. Let me know if there is still a problem with this !
Q : Why do you change naming of the zip file ?
A : Cause I want ! And it's listed directly in chronological order in terminal (or recovery) in this way.
Q : How can I know which apps use most space on /datadata :
A : Just run as root (in adb or terminal) :
Code:
du -s /datadata/*|sort -n
Downloads :
Box : https://www.box.com/s/6783d86f3840c02db911
Dropbox : https://www.dropbox.com/sh/rwibb0r0fhhyvh6/KaoBoC1BtB
Please don't mirror this.
I put the shell script in attachement here. Just grab it on your sdcard, remove the ".txt" extension and you could run it using Scripter or equivalent (root needed). Please post here if something gone wrong when using it.
Donations :
As I spent some time (and coffee) for this (and april datafix for those following previous xda thread) I think about a donation button. Give me your advise on that please ...
Link for donations
But just a little "Thanks, it works great !" would be great !
Reserved.
(ten chars)
Thanks for this. I kept wondering why I would run out of storage all the time. Well, now I know and you fixed it!
Sent from my GT-P7510 using XDA Premium HD app
awesome using chrome was causing me FC every once in a while
Hi,
Nice work.
Something I don't understand - how should I choose which apps I have their cache go to the /data partition? Apps that I frequently access? Apps that take a lot of space?
Wendigogo I've previously had an old datafix posted that moved all the files to /data/data and I've only had issues when Chrome filled the cache so Ive ran your script but now /datadata is filled and everything is FC Chrome's cache seems to be in /data/data though
any ideas?
Er.. is my datadata folder meant to be empty after applying this patch ? Phone is definitely slower.. forgot to do a nandroid too argh.
As per the other fixes.. doubt this is reversible ?
Sent from my GT-I9000 using Tapatalk 2
Wendigogo said:
Q : Can I use this on Samsung based rom ?
A : No ! And it's irrelevant cause Samsung roms don't have the "Low storage" issue !
Click to expand...
Click to collapse
Just a stupid question.
Why Samsung Roms dont need it ?
How works the solution of Samsung?
Thanks!
Very good script. Whats your future plans for this?
It would be really good if this was made into an app that let u select the apps cache you want on /data or /datadata rather than having to edit a text document.
Sent from my GT-I9000 using XDA
I've flashed this and now my /datadata partition is empty...
Enviado desde mi GT-I9000 usando Tapatalk 2
Something went wrong for me too
I wasn't previously using datafix,flashed it and checked my /datadata a very little time after reboot that was 128Mb free.Seemed a lot of free space comparing to the only-libs 2903 version.For the same initial configuration/apps installed i usually get about 88Mb of free space after flashing 2903.
Just a little while later i noticed a datadata folder in /datadata and free space was now 66Mb...I reboot and /datadata ended full.
Note:Users of Devil or MnIcs get after each boot a user.log (+ a .bak of the previous boot) that describe among others things init.d process,it could help to paste it here
Seems to work for me... but can someone tell me what the following folders are for and if I need them or if they're remnants of some past datafix?
/data/data.new
/data/data2
Thanks.
TheeWolf said:
Hi,
Nice work.
Something I don't understand - how should I choose which apps I have their cache go to the /data partition? Apps that I frequently access? Apps that take a lot of space?
Click to expand...
Click to collapse
None would be the best choice.
Moving their cache out of /datadata can potentially make them laggy. However, some apps have massive caches (Flipboard, Chrome, Google Music, etc.); as such, these apps are unusable unless you do move their cache (or unless you have very few apps installed).
I wonder why so many people are having troubles. I'll give the script a try soon. It looks good! Thanks for your monumental contribution, Wendigogo.
Wendigogo said:
Donations :
As I spent some time (and coffee) for this (and april datafix for those following previous xda thread) I think about a donation button. Give me your advise on that please ...
But just a little "Thanks, it works great !" would be great !
Click to expand...
Click to collapse
My vote is that you SHOULD put up a donation button, I am happy to contribute to your coffee fund (so long as you don't drink Starbuck's ;-) But since you're French, you surely have better taste than that!)
After upgrade to ver.0521 from 0329, I have the following problems:
1. There is a data.new folder, I wonder if it can be removed.
2. new installed apps haven't been moved to datadata
3. removed apps haven't been removed from datadata
I'm on cm9 0520 with devil 0.56 kernel, busybox updated to 1.20.
By the way, the scripts run well under scripts manager.
curl66 said:
Just a stupid question.
Why Samsung Roms dont need it ?
How works the solution of Samsung?
Thanks!
Click to expand...
Click to collapse
I GUESS it is easy to manage across all devices for the cm team without having to write specific code for different devices.
basily said:
Seems to work for me... but can someone tell me what the following folders are for and if I need them or if they're remnants of some past datafix?
/data/data.new
/data/data2
Thanks.
Click to expand...
Click to collapse
+1. Why do we need those folders to be kept in data? But when I tried to delete data.new I got FC's for all of my apps. Seems that data.new has replaced data/data folder.
And one more. I wanted to move com.android.email to data/data completely and edited skip_apps.txt. But when I check datadata folder with Disk Usage app - com.android.email still remains there.
What have I done wrong?
Sent from my SGH-I897 using xda premium
I find that 0521 version uses busybox for copy /move /mkdir operation, which is different from old versions.
After 3 reboots /datadata is still empty...
Enviado desde mi GT-I9000 usando Tapatalk 2
JATDATAS
What is it?
Jatdatas is a simple package, to be a smaller GAPPS package for the jellybean ROM. When porting jellybean I found that the /system partition was totally full of gapps stuff. This removes some unneeded gapps packages and moves some gapps stuff to /data. Jatdatas stands for Jellybean Apps To Data And Take Away Stuff. This is useful, but basic, if you can make it better, please do I don't however, want to loose functionality of certain stuff.
When do I need it?
If you are a dev then after porting jellybean, run adb shell df to see if you need this package to not overflow /system. If you're not a dev, you probably only need to download and install this package, just as you would with normal gapps. This is based on goo.im's 2012-07-26 package. This is normally needed on lower-spec phones, with smaller partition sizes. This stops the need for dangerous repartitioning.
Credits
- Google
- Goo.im (hosting)
Please credit me if you include this in your ROM, thanks.
Download JATDATAS
(you can flash this in recovery, jellybean roms only)
Add a detailed Description regarding what stuffs are removed and what apps are moved to /data
vNa5h said:
Add a detailed Description regarding what stuffs are removed and what apps are moved to /data
Click to expand...
Click to collapse
Okay, will do
Sent from my Wildfire S using xda app-developers app
I see the file size as 55 MB. May I know how much of that occupies /system ? Coz in mine, only 30 MB is free in /system after installing JB.
Sent from my GT-S5570 using Tapatalk 2
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.
chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.
Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app
It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.
I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.
Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:
Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app
Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.
Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery
I have successfully rooted my T230 and installed TWRP 2.8.0.1. I now want to update the Google system apps with the latest available. I currently do this on my HTC One X running CM11 with the PA-GAPPs from here. I also modify the .zip file contents with the latest when they come out - I usually check here.
Now I tried this on the T230 and the script starts but exits saying 'Incompatible GApps Currently Installed' - I wasn't expecting it to work to be honest.....
I still want to update the Google system apps in /system/app and /system/priv-app to the current ones as the ones in the OTA ROM are fairly out of date. I know I can let the Play store update them to the current ones, however I wipe the device frequently and would prefer not to have to go through this each time. There are apps on the play store that let you move system apps and to user apps and vice versa which I have used before however its a faf each time they get updated as you need to make the system app a user app, let it automatically update or manually update it yourself with the .apk file and then move it back to system/app.
I'd prefer a flashable .zip I can install from recovery?
Andy
ADB100 said:
I have successfully rooted my T230 and installed TWRP 2.8.0.1. I now want to update the Google system apps with the latest available. I currently do this on my HTC One X running CM11 with the PA-GAPPs from here. I also modify the .zip file contents with the latest when they come out - I usually check here.
Now I tried this on the T230 and the script starts but exits saying 'Incompatible GApps Currently Installed' - I wasn't expecting it to work to be honest.....
I still want to update the Google system apps in /system/app and /system/priv-app to the current ones as the ones in the OTA ROM are fairly out of date. I know I can let the Play store update them to the current ones, however I wipe the device frequently and would prefer not to have to go through this each time. There are apps on the play store that let you move system apps and to user apps and vice versa which I have used before however its a faf each time they get updated as you need to make the system app a user app, let it automatically update or manually update it yourself with the .apk file and then move it back to system/app.
I'd prefer a flashable .zip I can install from recovery?
Andy
Click to expand...
Click to collapse
Well, I haven't tried flashing a Gapps zip but I agree that the apps are really outdated and would be too much to update each time you factory reset/wipe the device.
One way of doing this as you have mentioned: Remove the current Gapps. But I'm not sure it works for the play services. But even doing this may lead to the same error while flashing the zip.
Second way, as you said yourself, would be to make them as user apps and update them and make them system apps again. Which would take some time. But it seems the best method here.
The last way, specific to your case, is to wipe the device, update the apps and finally make a nandroid backup. Next time, instead of wiping, just restore the backup.
There can also be other ways to flash the zip in traditional manner but I think it would require a chance in the updater script of the package. (While you're at it, make sure you're flashing Kitkat 4.4 Gapps and not L Gapps.)
I am attempting to apply an update of stock amazon 4.5.3 on apollo and there are three files being symlinked that are missing from my 3.2.3.2 device. Can anyone be so kind as to provide the following three files?
/data/misc/DxHDCP.cfg
/data/misc/audio/wcd9320_mad_audio.bin
/mnt/sqfs/fonts
The last one is a folder, so if someone could provide the folder and its contents recursively, that would be most helpful.
I don't have an Apollo so can't directly help with your request. However, I believe you need to be at 3.2.6 before upgrading to Sangria vs flashing a complete image. Maybe it's just those 3 files but could be others or different versions of identically named files. Smarter people in these forums can correct if I misspoke.
gbgadgets said:
I am attempting to apply an update of stock amazon 4.5.3 on apollo and there are three files being symlinked that are missing from my 3.2.3.2 device. Can anyone be so kind as to provide the following three files?
/data/misc/DxHDCP.cfg
/data/misc/audio/wcd9320_mad_audio.bin
/mnt/sqfs/fonts
The last one is a folder, so if someone could provide the folder and its contents recursively, that would be most helpful.
Click to expand...
Click to collapse
Did you manage to fix it using my tips?
p1gl3t said:
Did you manage to fix it using my tips?
Click to expand...
Click to collapse
I greatly appreciate the tips!! However, the time I have to mess with the device is quite random. I ended up having a problem restoring a backup and had to format the data, sdcard, etc partitions. I did have the backup also stored on a separate drive, so I got back up and running on a 'close to stock', rooted, xposed, gapps, etc 14.3.2.3.2 version. From there I went ahead and tried to update all but the bootoader to 14.3.2.6. This was successful and so I backed that up. Then I went ahead and re-tried the .zip you had posted for 14.4.5.2, and sure enough it flashed great. So, I am enjoying this fireos with unlocked bootloader, custom recovery, root, and gapps. I am sure I will try cm11, cm12, and aosp lolli as they come out, but for now, things are quite glorious with this device.
The devs around here (you included) are doing amazing things with this stuff. I really appreciate the teaching moments you guys (and gals) share too. What a great community.