Database Develop

[MOD] Resolution (dpi) changer *now with zips for all (hopefully) legend ROMs*

I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows

Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse

hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager

Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...

TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!

No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.

nice job
thanks bro

nice
spare parts is also in neonmod

xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?

TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234

TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!

xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App

Wow, really cool mod Love it!
Good job!

Cool, glad you like it

Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.

Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...

SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App

i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/

TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.

Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"

[ How to ] How to get the V6 supercharger to work on the 10.1 tab

What this does is speed up your tab. Its crazy how well zepplinrox got this to work, but it makes the tablet fly. It doesnt require more battery, nor stress the hardware any. It alters and fixes the OOM groupings, lowmemorykiller and the priorites. I don't want to get into the nitty gritty, but do it and I'm sure you will be amazed!
If you do not have the init.d folder, then you need to load a custom rom. Some custom roms will have this folder. Read on page two, zepplinrox explains it more.
Here is the process to get the supercharger to work and stick on out tabs. Its all spelled out on the original post ( by zepplinrox ) , but this is the short and sweet version.
You need to be rooted and have busybox 1.18.2 or lower.
First off go here and download the script : www.mediafire.com/?w6682pwu52ty5o6
Then download this app : https://market.android.com/details?id=os.tools.scriptmanager&feature=search_result
1. Then you run the script manager and find the V6 script that we first downloaded.
2. When you click on the script, the manager will open,( Make sure the run as root box is ticked under the "run" button ) just hit run in the top left of the screen.
3. Then, you have to just click in the black anywhere and the keyboard will open. Select a number 1, 2, or 3 , this is how fast the text will scroll. Being the screen is so big, select number 1. You will be fine. Hit enter on the keyboard, then lower the keyboard away.
4. You can now see a lot of options, don't get nervous. The script does it all itself. Being that we have so much ram already, the minfrees are already huge, but can be bigger . So options 1 - 7 are smaller than the stock minfrees. You can use either setting 8 or 9. I'm using the setting number 9. So to select the minfrees you want ( either number 8 or 9 ), click on the screen to bring up the keybpard, and hit the number you want ( again 8 or 9 only )!
5. Once that is done you will see the script run some info in front of you. It will say to reboot but don't yet. Type the number 17 in, and you will see it say bye etc. Ok, once it says bye, hit the back soft key in our launcher. Now navigate to this on the screen that in front of you. Keep hitting back until you get to the ''/'' of the tablet. Rom there you will click on ''system'', then click on ''etc'' and lastly on '' init.d '' . In there you will see a file called '' 99SuperCharger'' . Click on that and the script manager will open again, but you need to select certain boxes this time before hitting run. When the screen comes up hit '' run as root '' and '' run on boot ''' and hit save. Once that is done hit run ( nothing happens here, so don't expect to see anything scrolling) , then back out using the back arrow in our launcher. Then reboot your tablet, and that's it. The custom minfrees now stuck, and your supercharged!
Thanks to zepplinrox for this script!
P.s. to find out of the script stuck, reload the FIRST V6 script. Select your speed like we did, then once it is all loaded up you will see a line in there that says prior mifrees ( prior is still your current ) . Just match that up with the number you selected at first.
Thats it.
Here is the op on supercharging, from zepplinrox forum.xda-developers.com/showthread.php?t=991276
Sent from my Galaxy Tab!

so what does this do exactly?

In a nutshell, its a memory manager.
It will speed up your phone, multiasking etc. Its kinda crazy how well it works, and does not require more battery life like overclocking does. What it does it rearrange the OOM groupings, lowmemorykiller and priorties.
Sent from my Galaxy Tab!

cool thanks for the quick reply, can this be used in conjunction with a Task's ROM and pershoot's kernel?

I think I'll wait for others to test this out first seems too good to be true

mickey78 said:
cool thanks for the quick reply, can this be used in conjunction with a Task's ROM and pershoot's kernel?
Click to expand...
Click to collapse
yes. you can use in on basically anything bro.

yes it works anything android based. And for the skeptics, its been out for sometime now. Look here..
forum.xda-developers.com/showthread.php?t=991276
That's the op on this.
Sent from my Galaxy Tab!

Samsung Adrenaline Shot
This has been developed for some days and I am using on my Captivate, it's amazingly fast. I know some files are HC based but written for GB, maybe someone take a look and see if it will work?
http://forum.xda-developers.com/showthread.php?t=1236779
I use SAS, not USAS as it is just a script.

I've been using it for a while on my evo and the same with the tablet. All works well.
Sent from my Galaxy Tab!

I'll follow this thread closely. It always amaze me how a small group of people working together can achieve things beyond what Google themself can achieve with their OS.

Im getting permission denied during the last step (run as boot etc.)
Any ideas? My tab is deffo rooted as other apps that require root work fine.
Cheers!

I haven't got the init.d? What's wrong? I'm using broadcom KH7.

Here is a screen shot.

same for me, i dont get the init.d folder. I saw many permission denied lines in the script, so i run the script again with root. It doesnt help and i restart my Tab... and now i am in a bootloop. So i restore my backup, but can someone tell me what i do wrong?
Thx in advance
Flash
Edit: same for me, like klass1 , i use the Broadcomb stock too

klass1 said:
Here is a screen shot.
Click to expand...
Click to collapse
I also have the same problem, running stock rom.
Is root required?

Hey sorry guys, I'm out of the house. But yeah root required, I think. But not 100% sure as I have always been rooted. And as far as not seeing the init.d folder.. are you fellas all the way back to the '/' in the script manager? Go system, etc,init.d and the 99SuperCharger should be there. In sure why you can't see back that far. Are all or you guys rooted that are having issues? The ron type doesn't matter, as these folders are universal on all roms.
Also I too received some denied lines, but all is working as should. So that shouldn't be an issue.
Sent from a miui powered HTC Evo.

Yes, I am all the way back at / going to /system/etc and I could NOT find the init.d folder after running the script. I am rooted and using the Broodcomb ROM for GT-P7500. I have the same problem the other guys have. Help please!

i didnt have it either, the init.d folder, so i ran a kernel tweak from the creator of V6 scrpit and that created a init.d folder for me then i ran the script again and there it was the 99Suercharger file. So i think you can just create the folder your self, no need to run the kernel tweak, just ad new folder to system/etc called init.d that should fix it for thoose that dont have it created by the script.

And did you noticed a good speed improvment?
Sent from my GT-P7500 using xda premium

How do you create a folder?

[Q] bundling system apps into pre-existing custom roms?

I'm wanting to install the current version of the AOKP rom onto my note, but i noticed (after I flashed - boh) that there's an FC problem with the included launchers on that rom.
In the instructions they suggest using ADB to push novalauncher's apk file out to your device, but that seems needlessly complex to me when I could just (in theory) bundle the app into the .zip before I flash.
Is there any reason I can't insert the nova.apk into the AOKP.zip file (in /system/app as i understand it), zip it back up, flash the .zip as per normal AOKP instructions and proceed on my merry way?
Is it that simple? Do I need to mess around with chmodding the apk file or should the fact that it's in /system do that stuff for me?
FWIW I have tried this, but got some problems with having lost root between flashes (stupid ICS root) and that caused me some problems and a lot of high-heartrate moments trying to flash back to a working RocketRom build.
I'd rather do it 'properly' with accurate information about what I'm doing before I try again.
Appreciate the assistance.

I am to faceing the same problem but on other device
Sent from my HTC Glacier using xda premium

sideways86 said:
I'm wanting to install the current version of the AOKP rom onto my note, but i noticed (after I flashed - boh) that there's an FC problem with the included launchers on that rom.
In the instructions they suggest using ADB to push novalauncher's apk file out to your device, but that seems needlessly complex to me when I could just (in theory) bundle the app into the .zip before I flash.
Is there any reason I can't insert the nova.apk into the AOKP.zip file (in /system/app as i understand it), zip it back up, flash the .zip as per normal AOKP instructions and proceed on my merry way?
Is it that simple? Do I need to mess around with chmodding the apk file or should the fact that it's in /system do that stuff for me?
FWIW I have tried this, but got some problems with having lost root between flashes (stupid ICS root) and that caused me some problems and a lot of high-heartrate moments trying to flash back to a working RocketRom build.
I'd rather do it 'properly' with accurate information about what I'm doing before I try again.
Appreciate the assistance.
Click to expand...
Click to collapse
I open the ROM zip up and add .apks to the /system/app/ folder all the time..I also delete the ones I know I can and won't use..
There are some apps that won't work like this but its very uncommon..For example I can never include quickpic I always have to manually install it from the market.

sideways86 said:
I'm wanting to install the current version of the AOKP rom onto my note, but i noticed (after I flashed - boh) that there's an FC problem with the included launchers on that rom.
In the instructions they suggest using ADB to push novalauncher's apk file out to your device, but that seems needlessly complex to me when I could just (in theory) bundle the app into the .zip before I flash.
Is there any reason I can't insert the nova.apk into the AOKP.zip file (in /system/app as i understand it), zip it back up, flash the .zip as per normal AOKP instructions and proceed on my merry way?
Is it that simple? Do I need to mess around with chmodding the apk file or should the fact that it's in /system do that stuff for me?
FWIW I have tried this, but got some problems with having lost root between flashes (stupid ICS root) and that caused me some problems and a lot of high-heartrate moments trying to flash back to a working RocketRom build.
I'd rather do it 'properly' with accurate information about what I'm doing before I try again.
Appreciate the assistance.
Click to expand...
Click to collapse
Well my problem is solved
Check the app name of apps ur adding they should not include space in them ( like xda primium.apk) if there r space then remove the space (like xdaprimium.apk) it should work fine
Sent from my HTC Glacier using xda premium

MrDSL said:
I open the ROM zip up and add .apks to the /system/app/ folder all the time..I also delete the ones I know I can and won't use..
There are some apps that won't work like this but its very uncommon..For example I can never include quickpic I always have to manually install it from the market.
Click to expand...
Click to collapse
Thanks man.
One more question - as far as launcher apps go, is there any way to set the default launcher in the .zip file?
If I delete the pre-existing launcher app from the rom in question and add nova.apk should it set itself as the default launcher app automatically?

sideways86 said:
Thanks man.
One more question - as far as launcher apps go, is there any way to set the default launcher in the .zip file?
If I delete the pre-existing launcher app from the rom in question and add nova.apk should it set itself as the default launcher app automatically?
Click to expand...
Click to collapse
no you will prbably need to makea script to get it to work

How can i make the required script??
plz help
---------- Post added at 09:41 PM ---------- Previous post was at 09:37 PM ----------
And ive heard "the TouchWiz launcher included in the rom has hardware acceleration for better graphics performance while the launchers we use like GO LAUNCHER etc depends totally on cpu. They consume cpu power only and no GPU"
IS THAT SO??????????????
that would not mean a good thing
cause GO launcher or n other launcher are way better than Stock TWiz launcher.

I don't want someone to do all the work for me, but if anyone could direct me to some kind of resource with the relevant syntax and such that'd be amazing.

sideways86 said:
If I delete the pre-existing launcher app from the rom in question and add nova.apk should it set itself as the default launcher app automatically?
Click to expand...
Click to collapse
You can delete any launcher in the original zip and replace it with Nova and it will work. You don't need any script to do that, as suggested before.

thanks chasmodo - this worked flawlessly.

Fully install V6 Supercharger on ICS

I have been looking through the recent ICS threads and people have had alot of out of memory problems, so I thought I would post this easy to understand tutorial (well I hope it will be easy to understand)
Before starting, on Miroslav's Project Icecream Swift, you need to download busybox installer and install version 1.18.2, busybox included will not correctly determine minfrees.
First download the latest version of V6 at the end of this post, then copy it to your SD card and run it with Script Manager (from the market).
Choose your prefered scrolling speed and in the latest version its pretty much automated, you just have to say yes no a few times but it will auto detect the best settings based on the RAM of the device.
Also do not superclean and reboot, we need to do something else before we reboot.
Ensure you have a file explorer that can view the /system partiton before continuing.
On your phone browse to http://android.mimic.ca
Then click browse and choose your file explorer, and find services.jar in /system/framework then upload it.
After this the site will modify the services.jar and offer a download for it, to make it easy lets just use the update.zip so select that and download it.
Using the stock browser atleast it will go to /sdcard/download.
After this reboot to recovery, scroll to mounts and storage and mount /system manually (when I did not do this it didn't write the modified file) then install the zip.
Wipe dalvik cache and reboot, first boot will take a long time while its upgrading applications then run the V6 supercharger script to confirm you are 100% supercharged and you have your hard to kill or die hard launcher.
Note: On AOKP (atleast this version) because it doesn't have init.d (think its that one) before you first reboot to install services.jar you will need to browse in script manager to /data and find the 99SuperCharger.sh file and make it run on boot to get 100% supercharged.
I don't know if its important but every new rom I use I repatch services.jar just to be safe.
Any questions post here (also if the file doesn't download let me know and I'll upload it and post the link.)
Recovery zips for AOKP and Icecream Swift services.jar can be found below, just mount /system manually and i"nstall zip from sdcard" sorry it took a bit

For me i just use swap works good enough

For me not. Even if i use swap when i try to use gplay and listen music, music app closes itself. (Miro's latest ron)
Sent from my GT540 using xda premium

coto39 said:
For me not. Even if i use swap when i try to use gplay and listen music, music app closes itself. (Miro's latest ron)
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
Thats because swap is not technically used as RAM, what it does is suspends background apps using up RAM, then puts that state in to swap, the apps cannot run from the swap partition, so if you are listening to music and using the browser you will notice this, if you have twitter open, then open a link from a twitter post, the state of twitter gets pushed to the swap partition, to allow the browser to open and run, you then close the browser and it pulls twitter from the swap partition back to RAM giving the illusion of multitasking.
V6 actually gives multitasking by making sure android does not close apps when you have a fair amount of RAM left.

delsus said:
Thats because swap is not technically used as RAM, what it does is suspends background apps using up RAM, then puts that state in to swap, the apps cannot run from the swap partition, so if you are listening to music and using the browser you will notice this, if you have twitter open, then open a link from a twitter post, the state of twitter gets pushed to the swap partition, to allow the browser to open and run, you then close the browser and it pulls twitter from the swap partition back to RAM giving the illusion of multitasking.
V6 actually gives multitasking by making sure android does not close apps when you have a fair amount of RAM left.
Click to expand...
Click to collapse
Thanks for the explanation. I tried to apply supercharger (latest version, Update9RC8.2) to IceCreamSwift second official release bug when it try to apply minfrees the phone reboots.... The version you left works but don't shoy current minfrees, just shows: , , , , ,

coto39 said:
Thanks for the explanation. I tried to apply supercharger (latest version, Update9RC8.2) to IceCreamSwift second official release bug when it try to apply minfrees the phone reboots.... The version you left works but don't shoy current minfrees, just shows: , , , , ,
Click to expand...
Click to collapse
Hmm thats wierd, I have always been able to see them, but if it works it works

delsus said:
Hmm thats wierd, I have always been able to see them, but if it works it works
Click to expand...
Click to collapse
Don't know why but everytime i try to use the script with latest miroslav ICS i got an exception when try to appy supercalculator minfrees then a reboot.
With latest version of the script i can see original minfrees= "1,1,1,1,1,1,1" and when i try to apply new one = Poof! reboot!
Did you installed another busybox or something?... This rom without the script sucks in multitasking matter. (open one app and the others will be closed, is monotasking )

coto39 said:
Don't know why but everytime i try to use the script with latest miroslav ICS i got an exception when try to appy supercalculator minfrees then a reboot.
With latest version of the script i can see original minfrees= "1,1,1,1,1,1,1" and when i try to apply new one = Poof! reboot!
Did you installed another busybox or something?... This rom without the script sucks in multitasking matter. (open one app and the others will be closed, is monotasking )
Click to expand...
Click to collapse
I'll check it on new version of miro's rom tonight when I charge my phone (battery is dead right now) but I normally use the default busybox, it could be that the default has been changed on this rom, download busybox installer from the market and try a version on there, they are all complete so should have no problems on that end, lemme know if it still doesn't work.

delsus said:
I'll check it on new version of miro's rom tonight when I charge my phone (battery is dead right now) but I normally use the default busybox, it could be that the default has been changed on this rom, download busybox installer from the market and try a version on there, they are all complete so should have no problems on that end, lemme know if it still doesn't work.
Click to expand...
Click to collapse
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/

coto39 said:
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
Click to expand...
Click to collapse
Hmm, I'll try myself soon, havent noticed the problem before, I'll report back

coto39 said:
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
Click to expand...
Click to collapse
Ok I just resupercharged my phone running miroslav's rom, and I did see your problems, I fixed it downloading busybox installer and using busybox version 1.18.2 and it will detect your minfrees.
Also updated OP with this info and the patched services.jar files.

delsus said:
Ok I just resupercharged my phone running miroslav's rom, and I did see your problems, I fixed it downloading busybox installer and using busybox version 1.18.2 and it will detect your minfrees.
Also updated OP with this info and the patched services.jar files.
Click to expand...
Click to collapse
I did this, but when i run the script for second time to confirm if it worked, it says:
Launcher is DIE-HARD! ie. SUPERCHARGED
but after says:
OOM Grouping Fixes ARE NOT in Effect
...
Current values DON'T MATCH Prior SuperCharge!
this means that didn't worked???
I use miroslav last update 20/05/12

arperalta3 said:
I did this, but when i run the script for second time to confirm if it worked, it says:
Launcher is DIE-HARD! ie. SUPERCHARGED
but after says:
OOM Grouping Fixes ARE NOT in Effect
...
Current values DON'T MATCH Prior SuperCharge!
this means that didn't worked???
I use miroslav last update 20/05/12
Click to expand...
Click to collapse
Did you use busy box installer to install busy box or are you just using the version pre installed? The CM9 one will not work with V6.
Sent from my LG-GT540 using XDA

delsus said:
Did you use busy box installer to install busy box or are you just using the version pre installed? The CM9 one will not work with V6.
Sent from my LG-GT540 using XDA
Click to expand...
Click to collapse
I used busybox installer to get the version 1.18.2

arperalta3 said:
I used busybox installer to get the version 1.18.2
Click to expand...
Click to collapse
Using root explorer check /system/etc/init.d and see if there is a supercharger script in there.
If not try supercharging again, reboot and check, if its still not working find the 99supercharger.sh script and select "run on boot" and reboot, it should work after this.

delsus said:
Using root explorer check /system/etc/init.d and see if there is a supercharger script in there.
If not try supercharging again, reboot and check, if its still not working find the 99supercharger.sh script and select "run on boot" and reboot, it should work after this.
Click to expand...
Click to collapse
thanks, the script is in /system/etc/init.d, i will try to run the script with the option "run on boot" in script manager later

arperalta3 said:
thanks, the script is in /system/etc/init.d, i will try to run the script with the option "run on boot" in script manager later
Click to expand...
Click to collapse
Before you select "run on boot" just try to supercharge again, something could have messed up a little when you applied the minfrees, init.d scripts should run on boot anyway.

delsus said:
Before you select "run on boot" just try to supercharge again, something could have messed up a little when you applied the minfrees, init.d scripts should run on boot anyway.
Click to expand...
Click to collapse
weird weht i run the script in the end it says that everything is ok and active, but when i reboot and clean davilk chache and run again, it says that isnt ok

I have applied V6 Supercharge on this IceCreamSwift ROM. If I do Wipe Data/Factory Reset, do I need to apply V6 again?

Yes

[MOD] [P6800] DXMD3 Stock Jelly Bean Phabletized! [HELP WANTED - SCRIPTING PROBLEMS]

DXMD3 Stock Jelly Bean Phabletized!​
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...

Screenshots:
They're big. There are many, Unhide to see.
Mostly just showing off the Samsung apps. From my experience, most apps are a lot easier to handle on a bigger dpi. Again, if on some apps you don't like the change...go with Xposed framework.
Undoubtedly you'll notice how the fonts in the Settings app seem smaller than the rest of the rom and the alarm clock app seems bigger. You're right. They are. That's Xposed + App settings hard at work. I want the alarm clock buttons big when I'm smacking the **** out of my tab in the morning (300dpi) and don't need the big fonts when I'm fiddling with the settings (160dpi).
By the way, don't mind the "25% brightness" (I had it at -28% on some other screenshot). That's just Lux. It helps keep the display at a comfortable level in the dark. A screen filter basically. I also found this and this very helpful on a big screen and fiddly-sometimes-hard-to-press-when-your-hands-are-messy-when-cooking-and-just-need-to-look-at-the-recipe-one-more-time buttons (the other two persistent notifications).
Coming soon: Flashable zip. I'll get around to it, I promise. Having trouble scripting the thing. Take a look at the help wanted section if you think you can help. Thanks.

It is wonderful seeing someone try to create something for our Tablets...
I wish I could help in your efforts but instead I can only thank and applause you...
Good luck...

actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7

Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app

Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app

zip
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.

edan1979 said:
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Click to expand...
Click to collapse
Doesn't e-robot have some issues? I got the distinct feeling it wasn't quite so stock. I might be wrong though.
EDIT: Now I remember! I couldn't get over the flickering wifi icon in the status bar. Annoyed the **** out of me. Trivial, I know. I could live with something not working quite right if it wasn't visible most of the time.
{Diemex} said:
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Click to expand...
Click to collapse
Good tip. Thanks!
vivalamoza said:
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
I'll take some and post asap.
konsolen said:
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
Click to expand...
Click to collapse
Can this create a single zip for multiple apps or is it one app = one zip?

It creates one ZIP file. So exactly what you looking for.

Just a quick update:
I'm working on a cwm flashable zip that would back up the original apk and odex files and copy the new ones in place. Plus, I've been toying around with other versions of system apps.
I will be posting everything in the next few days - after I test it out.
Cheers

paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!​
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) Restart
13) If you have any issues with any of the apps, first try clearing their caches and data.
Click to expand...
Click to collapse
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.

obeguin said:
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
Click to expand...
Click to collapse
Never heard of LCDDensity before, but I'll add it to the instructions.
You're correct, the phablet ui starts at 180 (176 I believe), but the navigation bar keys are off center when lcd density is not set to 213.
Sort of defeats the purpose of phablet ui for me. Personally, I changed to a smaller dpi (for a smaller status bar - 195) and removed the navigation bar with the qemu.hw.mainkeys switch. I mainly navigate thru gestures (using GMD Gesture Control) anyway.
Again, you're correct. But when starting out on a freshly flashed rom, some might happen to skip the part where they connect to the wifi or connect their google account. Besides, I've seen Play being hesitant to install and update on it's own - sometimes it requires you to launch it before you get update notifications and automated app downloads which requires a launcher. I want the instructions to be as foolproof as possible. That's why I'll be making a separate flashable zip with a custom home and keyboard, just in case.
On that topic, do you know anything about scripting? I'm having trouble with the update script. Check out the first post.

You can try this note 8 samsung keyboard, it work on both tablet and phablet ui.
http://forum.xda-developers.com/showthread.php?t=2228836
Sent from my GT-P6800 using XDA Premium 4 mobile app

paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!​
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Click to expand...
Click to collapse
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed

vivalamoza said:
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
Click to expand...
Click to collapse
My suggestions:
You sure you're rooted?
You might have free space issues. Try disabling and uninstalling the apps from titanium backup and then pasting the apps in place. Samsung roms are pretty huge and fill the available space almost to the limit.
Pasting sometimes didn't work for me when the apps were running. Try closing them from a task manager. I always did the modding after a fresh boot on a fresh rom.
I hope this is helpful.