Related
The fruits of my deodexing project are now available for everyone to taste. What this ROM has is JH7 fully deodexed and zipaligned, and then tweaked. I have decided to remove the focus off the optimization, as others have made far more advances, and my choices may not be agreeable to someone else. I am not responsible for anything that happens to your phone, but I have tested this on my phone, and other than the issues noted below, I have not run across anything deal breaking. This is just a different way to optimize the files, so risk of any hardware damage is minimal. You'll only run into software that won't work.
How to install:
1. Download the zip file, and place it on the sd card.
2. Fire up ROM manager, and apply from SD card, also recommend doing a nandroid back up at the same time
3. ???
4. Profit
What yout get:
1. Stock JH7 deodexed, and zipaligned
2. AT&T and Samsung bloatware removed
2. Superuser and Busybox preinstalled
3. build.prop preedited to allow you to see all market apps
4. The kernel is untouched during the update, but the user data, and cache are wiped. You will need a Titanium Backup to restore.
Known Issues:
1. This is a stock style ROM, and you have to apply any optimizations or fixes manually, or using something like SRE. The JH7 files are all there (except the odex's of course), so the latest SRE should be compatible in theory, but I have always done all tweaks on the phone myself in the past so I am not 100% sure. I'll let some of you be the guinea pigs and report back.
2. Deodexing, and zipaligning is not some magic bullet for performance increase. I personally see no significant difference between the stock performance and this installation. But this is more flexible down the line to get us nearer to Vanilla Eclair due to having been deodexed.
How to Remove:
Use ROM manager, and restore previous backup.
The ROM can be downloaded Here:
Captivate-Deodexed-JH7_v_0.2-Stock
I hope for this to become a test bed of new ideas I can try out to make things better on our phone. So if you want to test it and guide me, I'd appreciate your input. If someone wants to take this and build upon it further, feel free to do so. I'll look into fixing the two apps force closing, with focus being on the camera, followed by the keyboard. Squashed.
Wow lets see what's to come off this + sre + new kernel + voodoo lag fix + froyo!
BRING ON THE THEMES!
WOw! How long did this take you???
TheTodFather said:
WOw! How long did this take you???
Click to expand...
Click to collapse
Not all that long. The deodexing itself is very automated. Making the ROM took a couple of more days to work out the updating script. I still need to work on the best way to integrate superuser and busybox.
i'll give it a shot!
Dear sirs and/or madams,
What's "deodexed and zipaligned"?
skinien said:
Dear sirs and/or madams,
What's "deodexed and zipaligned"?
Click to expand...
Click to collapse
I've wandered this as well
I would try it but I am too happy with how I've got it. The next time I flash it, it's gonna be to stock so I can get the 2.2 OTA. The work tho, I will say thank you for that.
Quick question..Why is sideloading disabled???
Flashing in just a sec, will update.
Sideloading is controlled by the settings.db file in dbdata. When you flash this ROM, that file gets wiped out and is rebuilt on first boot. I think the original is in the ramdisk packed with the kernel. So on first boot the old crippled file is recreated for you to hack into again.
Sent from my SAMSUNG-SGH-I897 using XDA App
Camera FC all the time, besides that ROM is pretty fast and zippy good job OP.
Will this rom do anything that might break something like SRE? If not, I'll flash it for sure. Got to do a round of it anyway to get the latest goodies
Here's what I've found so far:
-Camera force close
-Log tab in Superuser causes it to force close
-Superuser does work though, aside for the Log tab
-Wifi doesn't work for me
-Mobile Video bloatware isn't uninstalled, just need to be removed from script file and apps folder
Other than that, it's quite zippy and quick. Nice job! I'll take a look at the scripts and files a little later to see if I can fix some of the problems. Keyboard FC should also be an easy fix.
rajendra82, can I suggest that you release the rom as completely vanilla with the deodex and zipalign in place? In theory, everything should work as expected from a vanilla rom and not have things like the Camera app FC.
Users can then apply SRE and you would not have to reinvent the wheel regarding including Superuser, etc. apps.
From what you said about deodex and zipaligning in the other thread, a completely vanilla rom with these optimizations would already be beneficial.
Will installing this ROM negatively affect my phone in any way besides voiding the warranty?
spook said:
rajendra82, can I suggest that you release the rom as completely vanilla with the deodex and zipalign in place? In theory, everything should work as expected from a vanilla rom and not have things like the Camera app FC.
Users can then apply SRE and you would not have to reinvent the wheel regarding including Superuser, etc. apps.
From what you said about deodex and zipaligning in the other thread, a completely vanilla rom with these optimizations would already be beneficial.
Click to expand...
Click to collapse
It will be very easy for me to release the vanilla version, I had actually built that first. Samsung Keyboard still force closed on me when I had flashed that. I didn't know about the force close on camera at the time, but I am sure that it would have behaved the same way. The reason for force closure of these two apps is some bug in deodexing. The apps I removed are the same that SRE does, and I manually removed from my phone before deodexing. That is not the reason for force closes. But if everyone would rather have a stock deodexed ROM that they optimize themselves, I can release it a short time. I will also have to look at tweaking the deodexing process some to get rid of the force closes on the keyboard and camera apps.
+1 on a vanilla Rom..That would be great
rajendra82 said:
It will be very easy for me to release the vnilla version, I had actually built that first. Samsung Keyboard still force closed on me when I had flashed that. I didn't know about the force close on camera at the time, but I am sure that it would have behaved the same way. The reason for force clodure of these two apps is some bug in deodexing. The apps I removed are the same that SRE does, and I manually removed from my phone before deodexing. That is not the reason for force closes. But if everyone would rathe have a stock deodexed ROM that they opimize, I can release it a short time. I will also have to look at tweaking the deodexing process to get rid of the force closes.
Click to expand...
Click to collapse
vanilla would be great my friend...much appreciated
OP updated with stock deodexed ROM linked.
Now I need your help. I know the Camera app that is force closing is Camera.apk, but what app is the Samsung keyboard? On the same lines, when an app force closes, is there a log file generated somewhere to explain what happened.
frenchtoasted said:
Here's what I've found so far:
-Camera force close
-Log tab in Superuser causes it to force close
-Superuser does work though, aside for the Log tab
-Wifi doesn't work for me
-Mobile Video bloatware isn't uninstalled, just need to be removed from script file and apps folder
Other than that, it's quite zippy and quick. Nice job! I'll take a look at the scripts and files a little later to see if I can fix some of the problems. Keyboard FC should also be an easy fix.
Click to expand...
Click to collapse
Camera issue acknowledged. Looking to fix that. The superuser app version I used had that issue anyway on stock ROM before deodexing, later versions seem to have solved it. I have now decided to keep this a stock ROM project to weed out extraneous issues such as these. WiFi worked fine for me at home and work, so I am not sure what's going on at your end.
E_man5112 said:
Will this rom do anything that might break something like SRE? If not, I'll flash it for sure. Got to do a round of it anyway to get the latest goodies
Click to expand...
Click to collapse
Other than the kernel, everything that SRE does will be wiped out, as the whole system, data, and cache partitions will revert back to stock. You can always re flash SRE though.
I recently rooted/installed CleanROM for my S4, but now I have some basic questions regarding what actually happened in the process and how I could improve it. (First smartphone, first Android).
1. Is flashing the exact equivalent of installing a kernel/ROM/app in a recovery like TeamWin that is zipped in an SD card? All I did was select my zipped file and install--the guide says to use GooManager but I never used it. Also, does updating TWRP, kernel, or ROM (same application/kernel/ROM, but newer version) require that you delete the old ZIP, copy over the new ZIP, then install it? Is there a cleaner method (I feel that since we have to wipe to prevent old files from interfering with new ROM that maybe parts of the old version of a ROM may be redundant or may interfere with the new ROM?
2. Is there a way I can save the phone settings when dealing with one ROM and transferring these settings to another ROM? I really don't want to spend 20 minutes to go through all the settings and change it to my liking every time I install a new ROM.
3. With TWRP I could backup the entire ROM and also be able to install that backup ROM if I don't like the new ROM installed? What does Titanium Backup offer in regards to this aside from backing up app data and the ability freeze/uninstall system apps?
4. Does Titanium Backup leave any residual files? I see other apps designed to uninstall system apps and Titanium Backup seems like an all-in-one jack of all trades.
5. I thought I wiped everything and to me, that sounds like reformatting the entire drive. I only wiped system, boot, and data though (good enough for ROMs, according to what I've read). I was surprised when I saw my videos that I had already backed up to my PC accessible on the phone. Should I just wipe literally everything (I assume it would be cleaner) like cache, preload, EFS, modem, recovery, etc.? Will wiping literally everything be like reformatting my phone (since my phone was not reformatted because my personal videos was still there when I installed my custom ROM? If I were to install completely different ROMs cleanly and wanted to keep my personal files, I would only need to wipe system, data, and boot?
4. Do I have to use CASUAL again to install an updated TWRP?
5. Does backing up a ROM also backup its root? I'm going to assume this is a dumb question and the answer is no. I'm also guessing I have to block OTA updates from AT&T to ensure I keep my root. How would I go about doing this? Also, would my phone be "safe" if I stick to my ROM (no updates or anything) for 4+ years? I'm asking this as an extreme case because I feel like I'm missing out on AT&T security updates that could protect my phone and also I don't think the developer my ROM (CleanROM) will do frequent updates).
6. I had problems with my computer not being able to recognize my phone and my SD card in the phone after I wiped everything and before I installed a ROM. I literally had to take the SD card from the phone and use an SD card reader to transfer my custom ROM/loki then put it back into the phone. Was I missing a driver?
7. What are some must-have apps a newly rooted user would want?
8. I read that you only need 1 EFS backup and you don't need to back it up every time you are going to install a custom ROM. Can I get a confirmation?
9. What does Goo Manager do and would I want it?
10. Is it essential that I keep up to date with news about my custom ROM/phone to ensure my phone is secured?
**Not Root/ROM related--Is swiping an app away from the Recent Apps List (long-press home button) the equivalent of killing an app? I use the Recent Apps List often but I don't want to go about swiping apps away if means it is killing it, since I read that killing apps are bad and actually drains battery life. Also, is there a mod that lets you access the Recent Apps List by long-pressing the menu one? I only see a mod that kills the app if you long-press it.
Also, any ROMs you guys can recommend me that is like CleanROM? It has to be TW-based because I use multi-windows. Basically, I want a stable, popular (popular ones tend to be more frequently updated, which is important because there are often bugs in custom ROMs), and optimized/debloated ROM (as debloated as possible, I rather use my own large list of apps than pre-installed ones). I was looking at GoldenEye but I'm not sure.
Thanks. I'm hoping for many responses as I have more questions to ask but not a lot of free time (I will check back on this thread every several hours until there are no more responses on the thread.
Hey there! Here is my take on at least some of your questions. I am not a super pro, but I will try not to give you any wrong info.
1. The zip files that are still out on your SD card are just the install files for whatever you are flashing. They won't be cleaned up automatically and you will need to delete them yourself if you want them gone. That being said I would recommend leaving the previous version's zip out there in case you need to back out of the new version.
2. If by phone settings you mean all of the settings in the various option menus baked into the ROM it is best to redo those when switching between ROMs. Many ROMs add and take away options and add whole new option sections so you will want to go through those and set things to your liking. Another option is to use a launcher like Nova Launcher that lets you back up its settings and restore them which is a big chunk of the things I change when going to a new ROM. Some people may have a different opinion on this one.
3. Yes if you make a backup in a recovery like TWRP and then restore from it it will be like you never flashed the other ROM. Titanium backup does what you say and also can backup individual Apps themselves and restore them.
4. Once you have a recovery installed you should not have to go through the hoops you went through to get it there to update it. Check the thread for the recovery for upgrade instructions.
5. Your SD card will not be wiped when you wipe system or data. There is also the internal "sdcard" that if I recall is not wiped when you do a standard wipe which will keep things like pics and videos between flashes.
6. So you were trying to access the phone storage/SD card while it was in recovery? I have never had much luck with that. I always just make sure I have all of the files I will need to install the new ROM moved over before I wipe it. That being said if you have the right driver it might be possible.
7. Titanium Backup, a file explorer that can leverage Root access like Root Explorer, maybe something like Greenify (I think it takes Root). Other than that check out the thread in the Apps/Themes subforum where people list their top 5 apps.
8. Pass (but I think what you heard/read is right)
9. Goo Manager can let you know if there is updated version of your ROM or what other ROMs are available for your device and download them. It can also be used to install a recovery. Personally I don't use it and just check ROM threads for updates if the ROM doesn't offer OTA updates.
10. I rarely see mention of security fixes/features in custom ROMs so I don't think you need to stay on top of threads for that reason. With that said, if security is crazy super important to you then a custom ROM might not be your best bet. Even though source code is available for most if not all of them that doesn't mean someone has gone through the code looking for security flaws (or even malicious code).
11. You can test this yourself. Go into the "Apps" section of the options and look at what Apps are running then swipe one away and check again. Personally I would go ahead and swipe away Apps as needed since that is a core Android feature. I haven't seen a mod for what you are asking.
12. The other two TW-based ROMs I have used are Goldeneye and Alpha. Both are good, but I am using Alpha now due to its higher degree of customization. Goldeneye hasn't been updated in a month or so, Alpha is being updated regularly at the moment.
---------- Post added at 08:15 PM ---------- Previous post was at 08:09 PM ----------
Here is the link to the thread where people list out their top 5 apps!
Nice post, very good help...serious...
Incredibly helpful, thanks. I will post more questions if I have here, kind of busy at the moment.
Question:
What is the best way to detect whether a third-party app has a keylogger? I read from an article that it is incredibly easy for someone to put a keylogger on an app. Is Avast Mobile Security and Antivirus capable/overkill for this job? Also, I was worried that Avast may actually be bad because it would deteriorate (wear and tear on the SSD of the phone) through all the scannings? Or am I completely wrong? If I am wrong, I'm guessing it's because an antivirus only reads your files and therefore does not wear down a SSD (I'm not even sure if this is right).
mindstormer said:
Question:
What is the best way to detect whether a third-party app has a keylogger? I read from an article that it is incredibly easy for someone to put a keylogger on an app. Is Avast Mobile Security and Antivirus capable/overkill for this job? Also, I was worried that Avast may actually be bad because it would deteriorate (wear and tear on the SSD of the phone) through all the scannings? Or am I completely wrong? If I am wrong, I'm guessing it's because an antivirus only reads your files and therefore does not wear down a SSD (I'm not even sure if this is right).
Click to expand...
Click to collapse
You can read a SSD all day long, that doesn't wear it out. Writing to a SSD will cause wear, not reading. I'm thinking that most antivirus apps can find that kind of stuff, but don't download from unknown sources or those you don't trust. Even Google Play has some shady stuff. I would recommend researching an app on Google if you have any doubts about it. I'm sure it can be done, but I really doubt any of your friends know how to reprogram one of your apps to have a keylogger, plus I wouldn't let them use my phone in the first place.
To answer your questions:
1. Antivirus doesn't wear anything out, it just puts load on your system.
2. Most antivirus apps should detect apps like the ones your talking about.
agent929 said:
You can read a SSD all day long, that doesn't wear it out. Writing to a SSD will cause wear, not reading. I'm thinking that most antivirus apps can find that kind of stuff, but don't download from unknown sources or those you don't trust. Even Google Play has some shady stuff. I would recommend researching an app on Google if you have any doubts about it. I'm sure it can be done, but I really doubt any of your friends know how to reprogram one of your apps to have a keylogger, plus I wouldn't let them use my phone in the first place.
To answer your questions:
1. Antivirus doesn't wear anything out, it just puts load on your system.
2. Most antivirus apps should detect apps like the ones your talking about.
Click to expand...
Click to collapse
Thanks for the confirmation.
Another question for anyone:
Clean Master found the folder of an app that I installed on a precious ROM, so I not wipe the device cleanly. I though wiping system, boot, and data was enough--what was I missing, or should I have checked everything to be wiped on TeamWin Recovery?
Are you sure its not coming from your SD card?
Sent from miPhone using XDA Premium HD app
I have been trying to set ART as my runtime environment.It asks me about the change in the library and reboots my device.But then again while checking in the developers option it shows me dalvik as the runtime environement.What should I do in order to use the delights of ART.My phone is rooted with stock kitkat image.
cnilesh said:
I have been trying to set ART as my runtime environment.It asks me about the change in the library and reboots my device.But then again while checking in the developers option it shows me dalvik as the runtime environement.What should I do in order to use the delights of ART.My phone is rooted with stock kitkat image.
Click to expand...
Click to collapse
Do you use Xposed? I know that only works with Dalvik at the moment and actively resets that setting to Dalvik.
JASN_DE said:
Do you use Xposed? I know that only works with Dalvik at the moment and actively resets that setting to Dalvik.
Click to expand...
Click to collapse
Yeah i use that module just to extent my greenify features.Is there any way to use exposed and make ART work at the same time?
Quote from rovo89: "After installing Xposed, the runtime gets reset from ART to Dalvik. Can you stop it please?
You can be glad that I implemented this, otherwise you would be in a bootloop know. Xposed isn't compatible with ART (yet). It's a completely different architecture with pretty much no documentation. I hope that I can rewrite Xposed for the ART runtime, but don't expect it in the near future. It requires understanding the concept, the code structure and many details to know how it works. Afterwards, I have to think about ways to hijack it and this needs to be implemented, tested and improved again and again. So please don't ask when it will be available - you will surely know when it is ready." Plz search xda before asking theses questions if you had you'd have found this http://forum.xda-developers.com/showthread.php?t=1574401
Sent from my Nexus 4 using Tapatalk
ART is still in early version so use Dalvik for next few months.
rishabl1d said:
ART is still in early version so use Dalvik for next few months.
Click to expand...
Click to collapse
it has been answered already, the op is just dumb enough to not read the sec post of xposed thread, witch says that it sets back to dalvik, so your answer is wrong, and you also are dumb enough to not read all posts//or u just wanna win more posts.
Is it that I will have to remove all the apps which does not support ART?I have greenify as well as titanium backup and removing xposed also did not help.What should I do?
I'm guessing you just uninstalled xposed without removing the framework... Sigh
Sent from my Nexus 4 using xda premium
As the title suggests, I'm looking for information on what is necessary to root Alien Dalvik (4.4) on the Jolla C (hwadaption is based on 5.1 API lvl 22 but Alien Dalvik is not, it's based on 4.4 apparently)
On Jolla Phone, we had one superuser binary that we linked to in the directories opt/alien/system/bin and xbin and in /system/bin and xbin named su
The same procedure seemingly does not work. I've tried putting one of the many available su binaries in the respective places without success.
Sadly I have no clue where to look next. Does Android 4.4 need more than just the su binary for root access? On Jolla Phone Android 4.1.2 it was enough.
Thanks for any help in advance!
It is rooted.
Norpan70 said:
It is rooted.
Click to expand...
Click to collapse
Can you post a link to the process involved? I'm not talking about the SailfishOS side of the OS, I'm talking about the Alien Dalvik runtime... I have yet to find a way that works.
Thanks
MoritzJT said:
Can you post a link to the process involved? I'm not talking about the SailfishOS side of the OS, I'm talking about the Alien Dalvik runtime... I have yet to find a way that works.
Thanks
Click to expand...
Click to collapse
Actually, it seems semi rooted, I thought it was due to the fact that I earlier renamed the su files to be able to play pokemon on my phone. Now that I checked with root check it said that its not rooted, SuperSu seems to start tho, which it doesn't if it's not. So not properly rooted. My bad!
MoritzJT said:
As the title suggests, I'm looking for information on what is necessary to root Alien Dalvik (4.4) on the Jolla C (hwadaption is based on 5.1 API lvl 22 but Alien Dalvik is not, it's based on 4.4 apparently)
On Jolla Phone, we had one superuser binary that we linked to in the directories opt/alien/system/bin and xbin and in /system/bin and xbin named su
The same procedure seemingly does not work. I've tried putting one of the many available su binaries in the respective places without success.
Sadly I have no clue where to look next. Does Android 4.4 need more than just the su binary for root access? On Jolla Phone Android 4.1.2 it was enough.
Thanks for any help in advance!
Click to expand...
Click to collapse
NECRO REPLY INBOUND!!!
why do/did you need this? Usually people need root to interact and modify critical (or not so critical) components of android, and last I checked, Sailfish only uses the android base for Hardware support, nothing else, and I don't think SetCPU or similar will have much effect because if I remember correctly, SFOS uses it's own kernel.
Galaxyninja66 said:
NECRO REPLY INBOUND!!!
why do/did you need this? Usually people need root to interact and modify critical (or not so critical) components of android, and last I checked, Sailfish only uses the android base for Hardware support, nothing else, and I don't think SetCPU or similar will have much effect because if I remember correctly, SFOS uses it's own kernel.
Click to expand...
Click to collapse
Modifying critical files of the Alien Dalvik runtime such as e.g. build.prop etc. is possible through SailfishOS side with root rights.
However some apps that manage system notifications on the android runtime require root permissions to modify what is shown and what is not. That's just one example of many. Another would be backup solutions that want to write apps data aside from only installing the APKs
I find it ridiculous that Jolla didn't order a rootet or rootable Alien Dalvik from Myriad. I'm basically god on the SFOS side but the damn sandboxed Alien Dalvik is a world on its own? Nope that's not acceptable.
I hope you see where I'm going with this. By the way I have given up on figuring out a way since this time with Android 4.4 as Alien Dalvik base there seems to be another system security in place that requires to modify more than just one file. I'm clueless
Cheers
MoritzJT said:
Modifying critical files of the Alien Dalvik runtime such as e.g. build.prop etc. is possible through SailfishOS side with root rights.
However some apps that manage system notifications on the android runtime require root permissions to modify what is shown and what is not. That's just one example of many. Another would be backup solutions that want to write apps data aside from only installing the APKs
I find it ridiculous that Jolla didn't order a rootet or rootable Alien Dalvik from Myriad. I'm basically god on the SFOS side but the damn sandboxed Alien Dalvik is a world on its own? Nope that's not acceptable.
I hope you see where I'm going with this. By the way I have given up on figuring out a way since this time with Android 4.4 as Alien Dalvik base there seems to be another system security in place that requires to modify more than just one file. I'm clueless
Cheers
Click to expand...
Click to collapse
Ah, I see. I was wondering, then again I have never gotten alien dalvik set up on either of my sailfish devices (Nexus 7 2013 flo, and Droid RAZR M xt907), so I wouldn't know. Also where can I buy an Jolla Tablet and Jolla C? I Would sell all my devices in a a heartbeat and just use Jolla devices if I could find them. I live in Australia if that matters.
While Primary idea behind Project Treble allowing the OS layer to be updated independently - without relying on /vendor things (For starters/newbies https://www.xda-developers.com/project-treble-custom-rom-development/ )
Here at XDA we tinker around ROMs all the times. Irrespectively of ROM's stability, causal users always get stuck due to necessity to clean flash every time they want to try new ROM/new version of android
Dirty flash often creates conflicts with framework-res, System-Ui, etc etc such system apps data after a new ROM/Update and create unnecessary issues. Thus mostly considered as taboo. Whereas running Stock does not need to data wipe throughout device update lifecycle.
So, I would want discuss about the possibility of having /data modular to ROM as User App data is not going to change (Based on which root backup solutions like Titanium backup,etc work). This should enable the possibility of flashing any ROM, and User apps working smoothly on new ROM (just like device-specific blobs, etc in vender) unless major android version change is detected.
@ XDA Devs, Is this technically feasible?
Obviously its possible, i use this trick since last year.
In this trick, the app wont deleted, but, the app-data will erase.
Also everything inside/data (excluding media) erase.
But, the large sized /data/app will be intact.
Btw, it wont work, if u rollback to previous android version.
Only works within same version of multiple roms/ upgrading Android version
afridi.shahriar said:
Obviously its possible, i use this trick since last year.
In this trick, the app wont deleted, but, the app-data will erase.
Also everything inside/data (excluding media) erase.
But, the large sized /data/app will be intact.
Btw, it wont work, if u rollback to previous android version.
Only works within same version of multiple roms/ upgrading Android version
Click to expand...
Click to collapse
People are ok to lose app data if they want to roll back to previous versions of android. My context is reg. Project Treble which is only supported from Oreo..
Btw., Senior developers/tweakers pls think about this. Lets discuss if implementation of this is possible down our ROMs lane!!
arvindgr said:
People are ok to lose app data if they want to roll back to previous versions of android. My context is reg. Project Treble which is only supported from Oreo..
Btw., Senior developers/tweakers pls think about this. Lets discuss if implementation of this is possible down our ROMs lane!!
Click to expand...
Click to collapse
Hey. U don't need trebel/oreo to change ROM without deleting apps.apk, even i used this trick since......mmmm marshmallow 6.0.x
Is this referencing deleting /data/data/?
It works... But can have issues based on ART optimization...
Which is why the full wipe is recommended... Not for stability... But for troubleshooting
Sent from my PH-1 using Tapatalk
Maybe even just deleting /data/data for just the system apps, keeping the user app data in tact. Its definitely possible with a basic recovery script. Maybe we can look into that
rignfool said:
Is this referencing deleting /data/data/?
It works... But can have issues based on ART optimization...
Which is why the full wipe is recommended... Not for stability... But for troubleshooting
Click to expand...
Click to collapse
Thread is related to not deleting /data/data/ on ROM changes. Won't such ART Optimisation issues go off when cache is cleared?
This same is done on stock ROMs and even official Lineage OS updates don't require clean flash
tytydraco said:
Maybe even just deleting /data/data for just the system apps, keeping the user app data in tact. Its definitely possible with a basic recovery script. Maybe we can look into that
Click to expand...
Click to collapse
Yeah, when treble overcomes some major system partition shortfalls, /data shouldn't that hard.
Basically, this should ideally allow us switch between ROMs seemlessly...
I was able to do this about 3 years ago when I had an s3 mini, I had a custom rom available called Vibrant os but I wanted some apps to be pre-setup it included a data folder with data/app and data/data included along with data/system for wallpaper
took me a while and I had to find the folder permissions for each folder and do the set permissions command in the updater script but I was able to somewhat do this
I've taken the same code applied it but with set metadata changed to set perm
and I've reverted back to stock EMUI from resurrection remix project treble and all my apps have come across ( the data/data folder is next but atleast it is possible )
some google apps don't work if downgrading though
right now i'm copying data/app to my sdcard manually, wiping system, moving it back then doing my script
My goal is for the script to move data/app and data/data to the sd card, format data partition as f2fs, move data/app and data/data back then set the permissions
So basically, split /data/data into...
/data/data_system
/data/data_user
...?
I guess it's possible, but it would require changes at the ROM level. Maybe only framework, but possibly also in native code (e.g. zygote, not sure).
But... I don't think this really has anything to do with Treble.
CosmicDan said:
So basically, split /data/data into...
/data/data_system
/data/data_user
...?
I guess it's possible, but it would require changes at the ROM level. Maybe only framework, but possibly also in native code (e.g. zygote, not sure).
But... I don't think this really has anything to do with Treble.
Click to expand...
Click to collapse
i've managed to downgrade back from pixel experiece 8.1.0 to EMUI 8.0.0 and keep my apps ( data for the apps is tricky finding out the right read, write, execute permissions )
Livi-Tech said:
i've managed to downgrade back from pixel experiece 8.1.0 to EMUI 8.0.0 and keep my apps ( data for the apps is tricky finding out the right read, write, execute permissions )
Click to expand...
Click to collapse
It's not really, you just run restorecon command recursively on the tree - as long as file_contexts is intact then it will set permissions (and, more importantly, contexts) as they should be.