Hi, just a noob question.. how does it affect your phone's performance if you have double (or triple even) the entry of the same line of code in your build.prop file? example: if "pm.sleep_mode=1" appears twice in your build prop, would they cancel each other out? or if "wifi.supplicant_scan_interval=150" appears 3 times in your build prop, would they sum up (like scan interval =450)? or is it better to delete the duplicates (or triplicates) and just have 1 per line? thanks..
The last one on the list is applied, i.e. if you have nobootanimation 0 and then nobootanimation 1 it will not show bootanimation activating last line entered (how could two equal commands cancel each other out??)
Rudjgaard said:
The last one on the list is applied, i.e. if you have nobootanimation 0 and then nobootanimation 1 it will not show bootanimation activating last line entered (how could two equal commands cancel each other out??)
Click to expand...
Click to collapse
thanks for the reply... i was just thinking that probably with 2 contradicting commands, system might be slower or perhaps crash (boot loop) or something... however, you think it would be better to clean up, meaning, in your example, to delete the nobootanimation 0 if you want to have no boot animation? because if there will be lots of duplicate entries, i would think that your system would slow down?? thanks..
there is no problem is there are double lines with same value
but it aint good if they are doubled with different values
It's always best to clean up double entries, i have a model build.prop where i sorted everything out nicely, with #and explanation of the tweaks below, put it at the bottom of the script and when flashing new roms you can just copy-paste the bottom part since little ever changes above the "additional build properties" line. Also it is best not to edit it directly from the phone, just pull it out, use notepad++ which can easily higlight parts of script and show you where it's repeated. If i am not mistaken build.prop is only used on boot, so it's not constantly "working" thus it isn't always computing conflicting cmds
mv_style said:
there is no problem is there are double lines with same value
but it aint good if they are doubled with different values
Click to expand...
Click to collapse
Rudjgaard said:
It's always best to clean up double entries, i have a model build.prop where i sorted everything out nicely, with #and explanation of the tweaks below, put it at the bottom of the script and when flashing new roms you can just copy-paste the bottom part since little ever changes above the "additional build properties" line. Also it is best not to edit it directly from the phone, just pull it out, use notepad++ which can easily higlight parts of script and show you where it's repeated. If i am not mistaken build.prop is only used on boot, so it's not constantly "working" thus it isn't always computing conflicting cmds
Click to expand...
Click to collapse
thanks, both, for your reply... this is very helpful indeed...
nah, found this thread, for someone that who concern about this, just like me.
if this the case on build.prop, then how about on init.d?
i already checked on several ROM from somebodies that contains many many script/duplicate command, but in different script name.
in example just like value of nobootanimation is "1" or "0", this is conflicting, right.
i dont care if they just copy-paste it to init.D and forget to editing the script they use or what, then say it "Custom ROM" or "build from scratch", but im really currious is about effect of many duplicate tweak or conflict command on init.d.
someone, please enlighten me
Sent from my SK17i
Init.d is another bootup only instance, so it will only load the values on boot, if there are conflicting lines within the same script, as before, it will only load the last ones in the script, but if they are on separae scripts i don't know how it prioritizes the choices, but i am pretty sure it's not as safe as build.prop double edited lines (if you have 2 buil.prop files it will only load one) i used pimp my rom and added several tweaks and scripts (which were from all over the place and not well edited, such as thunderbolt script needs to be modified to suit your need for renice and memory tweaks) and on my already supercharged rom i would get kernel panic after the first reboot with a bootloop on bootloader starting process, always check what you're putting in your phone ((many scripts have functions disabled b a # at the beginning) and enable only things you need so they only run once. If you don't want to get messy just add a # at the beginning of every line of the script and that excludes them from booting
Related
These steps are intended for use on the stock Droid X2. I'm sure they will be close to the same on other phones, but if your phone is not a stock Droid X2, know that the steps may be different or you may get unfavorable results. Always backup anything you don't want to lose.
Before even considering this, READ ALL THE STEPS. Then READ IT AGAIN.
There are two tweaks recommended here: V6_Supercharger and SD Speed Increase.
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
3. BusyBox 1.18.2 or earlier
NOTE: I haven't confirmed the script works on 2.3.4... You may want to use the latest version of the script if you have 2.3.4
Installing/Using the script:
1. Install BusyBox. There are a number of ways to get this... it comes as part of Titanium Backup, for example. If you're not sure if you have it, or not, you can use BusyBox Installer (free on Market) to detect whether or not you have it and install it if you don't.
- Note: BusyBox Installer tells you which version you have installed on the main screen after it loads... it should be in a list that starts with "Your device is Rooted"
- Note: Make sure you don't install BusyBox 1.19 or anything newer than 1.18.2
2. Download the script. Save it in a place where you'll be able to find it.
3. Launch Script Manager and find the downloaded file (usually in /mnt/sdcard/download). Long-press no it and select rename, then delete the .txt from the end. You should have a file named "V6_SuperCharger_for_Android-update8.sh"... Press once on the script file to load it into Script Manager, check the 'Run as Root' box (DO NOT select "Run at Boot") and push "Run" to execute the script.
4. The script will run and ask for a speed. Touch anywhere on the screen to open your keyboard. Type 1 if this is your first time running the script, 0 if you're a fast reader or you are in a hurry. Next, it lists 17 options and gives an input prompt. Type 8 and push Enter. (This selects the called MegaRAM 1 preset, but feel free to try others, if you're so inclined)
5. Once script finishes, type 17 and push enter to end the script. Push the phone's Menu button and select 'exit' to return to the list of scripts.
6. Pushing the phone's Back button should bring you to a file browser. Push the '..' line (second from top) until the top line reads '/'.
7. Push the phone's Menu button, push 'More' and then 'Config'. Check the box 'Browse as root'. Push the phone's Back button to return to the file browser.
8. Browse to /data and select '99SuperCharger.sh' (This script was created by the first script and makes sure the settings from the first script are re-applied on boot)
9. Select both 'Run as root' and 'Run at boot'. Push 'Save' and then 'Run'. If it says "Exit code 0" at the top of the screen, the script ran successfully. Any other Exit codes should be reported.
10. Almost all the settings are now in place... but reboot your phone to get the last ones implemented.
11. After reboot, launch Script Manager and run V6_SuperCharger_for_Android-update8.sh (the first script). Select 0 at the first prompt, look for the current minfrees values... it should say "Launcher is HARD TO KILL!" and "Current minfrees = 6, 12, 40, 60, 80, 100". If the settings are correct, type 17 to exit and you are done. If not, re-read steps because you missed something.
Credit goes to Zeppelinrox, see this thread for more info on this script.
Requirements for SD Speed Increase:
1. Rooted Phone (Gingerbreak 1.20)
2. SD Speed Increase (free on Market)
Configuring SD Speed Increase:
1. Open the app and adjust the memory slider to 2048
2. Check 'Set on every reboot'
3. Push the red button
4. Reboot the phone
Advanced: 3G TurboCharge
- I'll post full step-by-step instructions soon, but for now, here are two more scripts from Zepplinrox that will boost 3G performance... (Forum Post) Run 3GTurboChargerInstaller.sh and 98KickAssKernelTweaksInstaller.sh once each (Hint: Don't forget to remove the .txt extension). The second script creates this boot script: /system/etc/init.d/98kickasskernel, so you will have use this thread to get init.d created (Side note: I haven't been able to get it to actually run the scripts that are placed in init.d... we're stuck with Script Manager for now). Run all scripts as root, obviously.
Questions, Comments & Corrections are welcome!
To Do:
Update SuperCharger to update7 (need to test it myself first)
Test and implement AutoStart script
Edit:
06/27/2011 - Removed ro.Home_app_adj tweak. It's handled by the SuperCharger script.
06/27/2011 - Updated SuperCharger script instructions to use v4 of the script.
07/14/2011 - Updated SuperCharger script instructions to use v5 of the script.
07/25/2011 - Added BusyBox requirement to the SuperCharger script.
07/25/2011 - Updated SuperCharger script instructions to use v8 of the script. Rewrote most steps for improved clarity.
08/19/2011 - Updated 3G and Kernel links.
Using it now... Cant see a major difference but I can tell some things are faster... and havent had any reason to kill any apps because the phone starts to get sluggish so IMO thats a major plus and a sign that it is working...
Oh yeah... use option 9! Megamemory device....
Sent from my DROID X2 using XDA App
alright so I did all the steps... but when i re-open it (step 10) it goes back to the original 1-3 menu. what did i do wrong?
falconfan101 said:
alright so I did all the steps... but when i re-open it (step 10) it goes back to the original 1-3 menu. what did i do wrong?
Click to expand...
Click to collapse
What does the script say those numbers mean?
The 1-3 settings are just setting the scroll speed of the text when the script runs. I personally like to set it to 1 (fastest) but it really doesn't matter. 3rd gives you a chance to read everything.
Works, like a charm, now if i wanted to get rid of it would it just be going back through the steps and undoing what i did?
slowz3r said:
Works, like a charm, now if i wanted to get rid of it would it just be going back through the steps and undoing what i did?
Click to expand...
Click to collapse
No, all you have to do is uninstall script manager and reboot. Deleting the scripts is optional.
Sent from my DROID X2 using XDA App
This script really made a big difference.
Great work, and there is no battery drain...
Sent from my DROID X2 using XDA Premium App
vvildcard said:
Before even considering this, READ ALL THE STEPS. Then READ IT AGAIN.
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
Installing/Using the script:
1. Download this ZIP and extract the script to your sdcard.
2. Load the V6_SuperCharger_for_Android-update4.sh script into Script Manager and check the 'Run as Root' box (DO NOT select "Run at Boot"). Push "Run" to execute the script.
3. The script will run and display a list of 16 options and a prompt. Touch anywhere on the screen to open your keyboard. Type 9 and push Enter. (This selects the option called MegaMemory Device)
4. Once script finishes, type 16 and push enter to end the script. Push the phone's Menu button and select 'exit' to return to the list of scripts.
5. Pushing the phone's Back button should bring you to a file browser. Push the '..' line (second from top) until the top line is '/'.
6. Push the phone's Menu button, push 'More' and then 'Config'. Check the box 'Browse as root'. Push the phone's Back button to return to the file browser.
7. Browse to /data and select '99SuperCharger.sh' (This script makes sure the other script runs on boot. Otherwise you would have to do steps 2-5 everytime you boot your phone)
8. Select both 'Run as root' and 'Run at boot'. Push 'Save' and then 'Run'. You will most likely see 2 errors at the end of the 99SuperCharger script... this is expected.
9. Reboot your phone, but you might already notice a significant difference in speed and zero redraws from your launcher.
10. After reboot, launch Script Manager and run the V6_SuperCharger_for_Android.sh script, but this time don't select any options just look at your current settings and make sure they are the same as the Step values you put in. Right under the list of options, it should say: 'NOTE: Current minfrees =' If they are correct, type 16 to exit and you are done. If not re-read steps because you missed something.
Credit goes to Zeppelinrox, see this thread for more info on this script.
These steps were posted a while ago on droidforums.net... you might run through the comments on that forum if you have any trouble and don't want to wait for a reply.
Click to expand...
Click to collapse
What are the values that it sets? I currently am running the V6 script and unless this is a newer version my option 9 is called "Gaming settings". At any rate I did option 10 and set values at 6,12,75,125,150,175. What does this set them to?
disregard my previous post. I ran it and found they are the same settings I have been using. Thanks for the updated script though.
is their a script dev thread where updated scripts are posted
THANK YOU!
I was about 10 mins away from calling VZW and telling them to take this back and send me my original X back... I wasn't able to get ANY Ver. of Pandora to play or even Slacker half the time. The complete phone would freeze ALL the time to the point I could not do anything unless I performed a Battery Pull to hard reset.
This fixed ALL my issues. I don't even have the 1-3 second wake delay I was experiencing before. So far so GREAT!! As I type I even realize that while Pandora is playing and the phone is charging it is not getting nearly as hot as it was before? I don't care why it's working better now, but I'm glad it is!
I can't wait until we can get a decent rom with these fixes already in place! I loved Liberty on my old X. I miss it!
A+++\
slowz3r said:
is their a script dev thread where updated scripts are posted
Click to expand...
Click to collapse
The end of the OP has the link.
This's pretty slick. While I haven't noticed huge gains in most areas, due to having cleaned and optimized my phone, the whole thing just seems to run with extra smoothness. Also, there's no more delay when waking the phone.
Sent from my DROID X2 using XDA App
I ran this script on my phone and couldn't be happier. Stock I'd get about 115mb ram free on ATK. After root and de-bloat I topped out at 170. After this script, 220+!!!
Sent from my DROID X2 using XDA App
This is a godsend!
Thanks for creating this thread and providing the most excellent script for memory mgmt. I've just installed it on my DX2 and boy, does it fly! I now see 130m+ memory free whereas before it would bounce between 50M-90M. Many thanks! I will run the remainder of this week and see if there are other impacts.
I do have one question, however, since I'm a newbie to all this: can I now remove the ATK application and disable the native Task Manager application with this script now in place? Or should I keep these as add'l failsafes?? Please advise and thanks for all the great info on this forum!
droid4ever said:
I do have one question, however, since I'm a newbie to all this: can I now remove the ATK application and disable the native Task Manager application with this script now in place? Or should I keep these as add'l failsafes?? Please advise and thanks for all the great info on this forum!
Click to expand...
Click to collapse
Try using Titanium Backup Pro to freeze these programs. I have both apps frozen, and my phone is fine
Sent from my rooted, supercharged Droid X² using XDA App
Does this increase benchmark scores at all? I know they don't mean anything but I think we can all agree, they're fun.
Also does this JUST manage memory or does it do other things as well?
Sent from my SCH-I500 using XDA Premium App
In my limited and completely amateur testing, there was no noticeable improvement in benchmarks... but I'm sure mileage will vary. You should seek out Zepplinrocks (the scripts writer) for a better answer.
I am sure this is a stupid question, but I'm a droid Newb. Is it nessicary to have the script manager app constantly running once you have already ran the script? Or is it good to go once I have exited it the last time? And after rooting, and running this script my weather widget keeps on saying i am in rockport il. And I'm not.... any suggestions?
When I click the Zip to download V6 on my phone it say "download unsuccessful"
And I have done these:
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
robocuff said:
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
Click to expand...
Click to collapse
That's what I figured is happening. I just have to determine where it's happening at.
I see that the V6 scripts are running, but something is setting it AFTER the init.d process is done.
I also checked the /data/SuperChargerRan log file and this is what I saw:
02-16-2012 09:20:53: Applied Settings from /system/etc/init.d/S99SuperCharger!
02-16-2012 09:20:54: DIDN'T Apply Settings from /data/99SuperCharger.sh!
Not sure why the second one isn't working.
Looking at the /sys/module/lowmemorykiller/parameters/adj file, it's back to the original settings that CM7 has: 0,1,2,4,7,15
iBolski said:
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Click to expand...
Click to collapse
Hehehehe... Me thinks you should search the forums a little bit. When I was testing cm7 for DZK, I tried EVERYTHING I used on previous ROMs, to include V6_SuperCharger. V6_SuperCharger DOES NOT WORK with CM7! The BIGGEST reason is the mapping for the memory slots are different with CM7, so fudging with them tends to cause massive issues and slowdowns. The reason it does not stick is most likely (speculation here) due to CM7 settings things back to it's optimized default settings.
Keep in mind that CM7 is an "optimized" AOSP based ROM... That means NO BLOATWARE! I am running with roughly 315 apps, most of which I use on a WEEKLY basis. Some, only monthly.
There are a few issues that I have noticed, root/su issues, sometimes system crashes on boot, sometime bluetooth crashes on boot, sometimes the dialer crashes... But with non-root apps, this thing SCREAMS!
Also, CM7 incorporates it's own memory management system that works better than the Moto Blur based ROMs. Just my two cents.
Ciao!
Moonshadow, thanks for the explanation. I did do a search and for some reason, your post didn't come up. Now that I search, I find it. I'll attribute it to an ID-10T or PEBKAC error.
iBolski said:
I'll attribute it to an ID-10T or PEBKAC error.
Click to expand...
Click to collapse
Are you REALLY sure about that??? It could be that Google just hiccuped during that nanosecond that your search on XDA was running... And didn't affect anyone elses searches...
You can be like Apple and blame/sue everyone else... (Just joking!)
Ciao!
Besides cm 7 does not need any script runs good as it is.
[UPDATE FOR JB.15][Custom Build Prop] Increase Performance & Battery Life of PRIME
MAJOR UPDATE: U.S. & WW. MODDED BUILD.PROP FOR NEW. 15 JELLYBEAN RELEASE ADDED. here are edited build.prop files for both the US & WW 10.4.2.15 Jelly Bean. Tweaks are listed as to what they are within the build.prop and to install just copy over using Root Explorer or similar app and then ensure permissions are set correctly. MUCH LOVE AND THANKX GO TO MR.WOOKIE FOR THIS and his constant contributions to making the prime a better device to own. I know I haven't been around as much as I don't own a prime anymore. But I can continue to update this thread as needed. Its very important that if issues arise, PLEASE TRY TO HELP ONE ANOTHER OUT. I can try to help out when I can. As always, make sure to set permissions correctly. JB build.prop Modding should be no different than previous versions. so most of the instructions in this OP/thread still apply. please post up how this mods are working for you on new JB firmware. if you notice any particular mod or line is causing problems with JB, please let us know. so it can be modified again. HAVE FUN...PRIME WILL ALWAYS BE HOME FOR ME
With the permission of the Original Developer, Seanzscreams, we bring a modified version of his mod for the 300 that now works on the Prime also. This is a custom modified build prop, that Brings Overall Performance & Battery life Improvements to the Transformer Prime. This will make your device feel more snappy and responsive overall. It should improve battery life. Other performance tweaks also will improve everyday use of Prime.Your device has to be on the latest U.S. .21 or U.S..28 firmware and rooted. If you on a ww version or other, you may need to tweak the build.prop to reflect your region version. Take a look inside the modded build.prop & see before you try it out. If you know how to edit it, give it a shot. just make sure to back up your original build.prop. If unsure, hit the link & ask the developer. It is possible to not be rooted and push this through ADB but being rooted makes it ALOT easier.
UPDATE: U.S. & WW .28 MODDED BUILD.PROP ADDED. EVERYTHING EXCEPT power collapse & wifi scanning added. some users reported issues that could be linked. same instructions on implementing this. MAKE SURE TO MAKE BACKUP OF YOUR ORIGINAL FILE. MIGHT BE BEST TO SEND IT TO SOMEPLACE OUTSIDE INTERNAL MEMORY OF PRIME. JUST TO BE ON THE SAFE SIDE.
*Users on region versions other than the US .21 or U.S. .28, read the tips at the end of this post before you attempt this. Putting this US version of build.prop in your device can cause issues if not properly edited to reflect your region.
*If you running Androwoki rom, no need to apply this tweak. the developer already added these tweaks to his ROM/build.prop.
-UPDATE: fellow member Mekrel made a .21 WW version of this for those who wish to try out. or you go the other route like mentioned in this post. the WW version is attached to this thread also.
Thanks to Hairdex for making a making a version for people running Team EOS Cornerstone build #9. only those on build #9 can use it.
-added De .21 version also
PLEASE READ IMPORTANT INFO & TIPS AT THE BOTTOM OF THIS POST IN CASE ANY POSSIBLE ISSUES ARISE.
Method described below is for rooted users as I don't really know how to do it the stock(not rooted) method through ADB. You can go to original thread and ask developer on how to push it through ADB method
Quote from developer, Seanzscreams:
" This is a modified build.prop to include all the latest ics tweaks
(from a build.prop standpoint)
forced 60fps
faster wifi connect and suplicant scan set at 100 (battery saver as well)
added deep sleep mode
added screen dithering
removed checkin back to base
kernel tweaked
dalvik mins and max set higher than stock
increased over-all fling velocity min and max now set
min at 8000 and max at 12000
a few nvidia specific graphics tweaks as well
. power collapse disable enabled
-and just a few i dont feel like explaining google is your friend"
Link to his original thread: http://forum.xda-developers.com/showthread.php?t=1641219
DISCLAIMER: I nor the original developer take responsibility if you don't follow instructions or researched first. USE AT YOUR OWN RISK. It should be a fast n simple mod. Works great on my prime. If you run into issues, we will help you the best we can. Please read the important info & tips at the bottom of this post. It could eliminate possible issues from arising.
USE ROOT EXPLORER:
this modded build.prop, which is attached to this thread, goes in /system. Make sure to back up your original build prop or add .bak to the end of it(.bak). I sent a copy of my original file to my drop box. just an extra safety precaution... You will need to change root explorer to mount as RW. after you back up the original file, paste the new modded build prop into /system. then long click on it and press permissions. the permissions need to be exactly like the original file. which is rw-r--r-- after you properly set the permissions, change root explorer back to Read only. then power down and reboot, then profit. You can reboot twice to make sure everything sticks, if you want. If you don't notice anything initially, let it cache(kind of like letting a car warm up before you drive off) just like with roms. just start using tab so it can cache.
CLARIFICATION ON SETTING PERMISSIONS IF UNSURE. your permissions for this mod build.prop should look like this: rw-r--r--
...........Read. Write
Owner. X .......... X
Group. X
Others. X
I would suggest before even applying this, open the mod build prop up in root explorer. then just take a look at it all. Then cross reference the new tweak lines added with the links I will provide now. These links show all the build prop tweaks and what they do. This is to get a better understanding of what will be improved on your device Performance & Battery Savings wise. It won't hurt for you to become more familiar with what the different lines do and it might eliminate some questions concerning what each does.
http://forum.xda-developers.com/showthread.php?t=1639104
http://forum.xda-developers.com/showthread.php?t=1510652
EXAMPLES OF SOME OF THE TWEAKS SEEN IN THIS MODDED BUILD.PROP & WHAT THEY DO OR AFFECT: Thankx to TheFrankenstain & H M Judge threads for Reference
- Allows the tablet to sleep better: This setting puts your tablet into a deeper sleep when on standby
ro.ril.disable.power.collapse=1
- Allows your wifi to scan less frequently, saving more battery
wifi.supplicant_scan_interval=100
- Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
-Increases Scrolling responsiveness
windowsmgr.max_events_per_sec=300
- Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
-Increases quality of photo/Increases the memory cap when decoding JPEGs
ro.media.dec.jpeg.memcap=8000000
-Raises quality of JPEG images: makes JPEG Higher Quality
ro.media.enc.jpeg.quality=100
-Enable Surface dithering:Improves image quality
persist.sys.use_dithering=1
-System tweaks:
Change the Dalvik VM heap size
-dalvik.vm.heapsize=256m
-dalvik.vm.startheapsize = 8м
-makes apps load faster and frees more ram.
dalvik.vm.dexopt-flags=m=y
-Use Jit (Dalvik just-in-time compiler): faster better caching system
dalvik.vm.execution-mode=int:jit
-Disable error checking (Should speed things up a bit)
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
this has been running great for me so far. battery life seems improved and the responsiveness of the touch screen is unbelievable. it scrolls so fast n fluid it crazy. this is with the regular UI & within browsers. It also increases quality of your JPEG pictures. Im really impressed with it so far.
Do note though, once OTA update comes, it will knock all this out and a new custom build prop will have to be made. this is even if you accept the new OTA.
I will keep this thread updated to stay current with the developers original thread. As new updates come out, he will be modifying the newer build props within the update. So I will add those here as they come.
Make sure to click on the developer, Seanzscreams, original thread(http://forum.xda-developers.com/showthread.php?t=1641219) and give him thanks. You can leave feedback in this thread and original thread, if you wish. Feedback is encouraged as it will lead to better future results on this mod.
THANKS TO: Seanzscreams for Modding my Prime build prop. Now we have this MOD available to all prime owners on latest .21 firmware and rooted.
Attached to this post is a zip file with the custom build prop inside of it. The U.S. and WW version
*IMPORTANT:
If you come across a difficulty, you can ask in this thread or even better would be to ask in the developer original thread. He would know more on possible issues that may arise.
If you run into issues or caught in a bootloop or something here is how to use adb and push back your original build.prop file: Thanks to Mekrel
in regards to being for locked/unlocked users, I posted two sets of commands. Technically three scenarios exist:
Being locked
If you're locked, you're not going to have any third party kernel installed and therefore WILL have a secure kernel and therefore not able to push files to /system. That's why you need the command that involves pushing to the /sdcard and then using su via shell to copy from the /sdcard and then to /system.
Unlocked but with a kernel installed that's still secure
As above
Unlocked but with a kernel installed that's insecure
You can push directly to /system, so you don't have to push to the /sdcard first
If you're unlocked you're going to be running a secure kernel which means you're not going to be able to run adb as root, so even with root and the /system partition mount as r/w; you're not going to be able to push to system:
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
adb push build.prop /sdcard/
adb shell
su
cp /sdcard/build.prop /system
chmod 644 /system/build.prop
rm /sdcard/build.prop
exit
exit
Unlocked and with an insecure kernel:
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
adb push build.prop /system
adb shell
su
chmod 644 /system/build.prop
exit
exit
In regards to remounting to read only once finished, you don't have to as you can simply reboot and the commands executed in ramdisk will remount every partition with the relevant flags. Or you could:
Code:
adb shell
su
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
you should be good to go after this.
*TIPS for users that are not on US .21 but instead on a WW or other version: thnkx to Buxtahuda & Gage_Hero
- instead of editing this build.prop with your information, edit your build.prop with any missing lines from this one. That's going to cut down on error a lot, and even if you get the right characters and spacing, the build.prop can be finnicky as all hell.
- IF you edit the build.prop use the right tool which would be notepad++ (download) not the standard windows note pad. if you use the standard windows notepad you could end up with format and character issues
*CAUTION:
We had a user who was unlocked, boot to a black screen. He got his prime back running by doing a restore from recovery. For unlocked users who want to try this, make sure to do a full backup, including the original build.prop file. Unlock users could even edit their own build.prop & add the lines one by one until it breaks. You can download notepad + yes it is +(plus). then you can edit the build prop (properly with out screwing up the format) on the pc and move it to the tablet. I'm not sure if being unlocked conflicts with this mod. just make sure you on latest .21 or .28 firmware and rooted. Then follow instructions carefully. you can even click on the original developer link for assurance on how to install if unsure how to install or if you have any possible conflicting issues. It would be best to ask developer if this is safe for unlocked users also. Unlocked users should proceed with caution and make sure you will be OK using this.
update:Developer said being unlocked shouldn't matter. I'm still waiting to hear back on what if people are on a different version like WW or something.
You can feel free to Hit my Thanks also, if you want. For putting this guide together on my Prime solely. The Prime is my PC Make sure to give feedback here & to OG developer, Seanzscreamz and his OG thread http://forum.xda-developers.com/showthread.php?t=1641219 . He made this all work for our Primes when he didn't have to. Much thanks to him & other members who contributed critical info, tips, & feedback.
Thanks to Texstar & Andromorphone for editing U.S. .28 buildprop.
That is the one I am looking for so long. Thanks for sharing.
Sent from my HTC Desire HD using xda premium
Could you please explain how to do this without root?
okay okay.. I will try it and report back
1SiK1500 said:
Could you please explain how to do this without root?
Click to expand...
Click to collapse
you actually dont need root
but this is way easier if you do
you could adb push /system/build.prop
or you could just paste it into root explorer replacing your existing
(back up existing or rename it to build.prop.bak just for safe keeping )
then reboot
or
when it reboots and adb comes alive you may be able to push it to /system with: adb push build.prop /system
not really much more was explained. you can click on his original thread link to get more details or ask him about it. most seem to be doing this the rooted method. I haven't seen anyone confirm doing this adb way yet.
I get an error..
"There was not enough free disk space to complete the paste operation" when I tried to paste this into /system with the original .bak there
I had to remove the original file to make room
Also, I think you better expand on what -RW, -R, -R means for people - like exactly what boxes to check and uncheck
I forgot to add:
If you don't notice anything initially, let it cache(kind of like letting a car warm up before you drive off) just like with roms. just start using tab so it can cache. it'll take to the changes.
Lock-N-Load said:
I get an error..
"There was not enough free disk space to complete the paste operation" when I tried to paste this into /system with the original .bak there
I had to remove the original file to make room
Click to expand...
Click to collapse
that's strange. I still have my original file in there renamed. I never got that error. Do you still have all those modded wifi files in there also?
edit: I saw the other part you added, I gotcha
demandarin said:
that's strange. I still have my original file in there renamed. I never got that error. Do you still have all those modded wifi files in there also?
edit: I saw the other part you added, I gotcha
Click to expand...
Click to collapse
Yes I do in /bin which is in /system - suppose i should delete those.
But this implies /system looks for and checks the size of that directory and pukes if it is beyond xx size - which is kind of interesting
Also, technically speaking, aren't permissions rw-r--r-- not -RW, -R, -R
Well, I did this and it just goes to a black screen and does nothing else.
How can I get back into the system and restore the old file?
Lock-N-Load said:
Yes I do in /bin which is in /system - suppose i should delete those.
But this implies /system looks for and checks the size of that directory and pukes if it is beyond xx size - which is kind of interesting
Also, technically speaking, aren't permissions rw-r--r-- not -RW, -R, -R
Click to expand...
Click to collapse
I edited OP to reflect that.
acdcking12345 said:
Well, I did this and it just goes to a black screen and does nothing else.
How can I get back into the system and restore the old file?
Click to expand...
Click to collapse
were you rooted and on .21 firmware?
did you put the modded file into /system & set its permissions to rw-r--r--? & rename the old file? so it won't be confused with 2 files try to be activated.
demandarin said:
I edited OP to reflect that.
were you rooted and on .21 firmware?
did you put the modded file into /system & set its permissions to rw-r--r--? & rename the old file? so it won't be confused with 2 files try to be activated.
Click to expand...
Click to collapse
I did exactly that..It was also unlocked...
Not sure how to go back to the old file..
Works great! Wow I can see a big speed difference! I can't wait to see how much longer the battery lasts.. Thanks man!
Sent from my Transformer Prime TF201 using XDA Premium App
jjdevega said:
Works great! Wow I can see a big speed difference! I can't wait to see how much longer the battery lasts.. Thanks man!
Sent from my Transformer Prime TF201 using XDA Premium App
Click to expand...
Click to collapse
you see changes that quick?? guess I will test mine more tonight.
my install went fine and reboot went fine.
I believe in this mod type as I did similar mods to my OG Droid
Lock-N-Load said:
you see changes that quick?? guess I will test mine more tonight.
my install went fine and reboot went fine.
I believe in this mod type as I did similar mods to my OG Droid
Click to expand...
Click to collapse
Surprisingly did. I didn't think I would see much of a difference that quick. As soon as it rebooted and right after the lock screen swiping was fast and opening closing apps are much quicker load times
Edit: overall loading speeds are improved quite a bit
Sent from my Transformer Prime TF201 using XDA Premium App
At work and don't have my Prime with me at the moment.
I will try tonight and report to you guys.
Good to hear positive feedback.
acdcking12345 said:
I did exactly that..It was also unlocked...
Not sure how to go back to the old file..
Click to expand...
Click to collapse
I'm wondering if being unlocked messes with things. Did you make a backup of your original file? if so. you can try to adb push it in there. you should go to original developer thread and post this up. As I'm not exactly sure on the adb method on getting the prime to use the original file.
ill make sure to add to the OP that being unlocked may conflict with this. As this is the only difference between yours n mines.
so you rebooting and it just went to a black screen? any Asus logo or anything? can you get into recovery and reflash your rom or restore a backup?
Anyone with insight into how he get back using the old file from state he is in now?
I don't see a wifi scan interval on either the original or this build prop. That was one I changed from 30 seconds to 100 on my phone to cut down on the power used by wifi to go out and ping and search for signals.
On my phone is it wifi.supplicant_scan_interval = 30
A bit surprised this does not exist as it can be a good battery saver
I also see some telephony stuff in this prop that seems of no value as we dont have phones
demandarin said:
I'm wondering if being unlocked messes with things. Did you make a backup of your original file? if so. you can try to adb push it in there. you should go to original developer thread and post this up. As I'm not exactly sure on the adb method on getting the prime to use the original file.
ill make sure to add to the OP that being unlocked may conflict with this. As this is the only difference between yours n mines.
so you rebooting and it just went to a black screen? any Asus logo or anything? can you get into recovery and reflash your rom or restore a backup?
Anyone with insight into how he get back using the old file from state he is in now?
Click to expand...
Click to collapse
I just went into recovery and restoring from a 3 old backup..
Lock-N-Load said:
I don't see a wifi scan interval on either the original or this build prop. That was one I changed from 30 seconds to 100 on my phone to cut down on the power used by wifi to go out and ping and search for signals.
On my phone is it wifi.supplicant_scan_interval = 30
A bit surprised this does not exist as it can be a good battery saver
I also see some telephony stuff in this prop that seems of no value as we dont have phones
Click to expand...
Click to collapse
it there is one actual in there. you have to look closely. its set to 100. I just looked in saw it. its like the 4th line above the additional build properties. I believe this scan is lower than in stock configuration.
I noticed the phone stuff also. he said once he updates, he has more tweaks he will add. ill update this thread with the changes also.
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.
Hello,
Problem:
My Meizu MX3 (runs Flyme os 3 based on android 4.2.2) has preset "Camera" in the DIRECTORY_DCIM environment variable. Most of the camera apps respect this setting and they are saving photos in the Camera instead of the DCIM. This causes problems with automatic syncing, because photos are obviously expected to be in the DCIM.
Partial solutions:
I tried symlinking the two dirs, but as far as i know it is not possible in the FUSE used since the 4.2.2.
mount -o bind led to the duplicity in the gallery app and i don't consider it too "clean" solution.
I ended up with modifying source of Focal open source camera not to read DIRECTORY_DCIM env var, but rather just to save the picture into the DCIM directly.
Is there a way to change this variable on boot? I don't want to use any 3rd party apps for simple things like this. Editing init.rc led to nothing, because it is always replaced by the default one from the ramdisk.
Thanks in advance.
Have you tried making an init.d script to export the value you want? I haven't looked at the source code so I don't know if that'll make a difference, but that's the only thing I can think of, short of modifying the API call using e.g. Xposed (somewhat similar to what this mod does.)
You may want to link the SO question you also created, in case you get a working answer there, so anyone stumbling on this page will find the way to that.
The init.d dir was not on my phone, so i tried creating it. Scripts from there do not get run on the startup, which brings me back to the problem with editing init.rc.
I will probbly just keep using modified camera until they release Ubuntu mobile for mx3 - which according to rumors could be soon
Thank you for your time
Sent from my M353 using XDA Premium 4 mobile app
Check if in your init.rc there is something like
Code:
service flash_recovery /system/etc/install-recovery.sh
Then you can edit/create that script and enable running init.d scripts with:
Code:
busybox run-parts /system/etc/init.d
search on this forum for more info
Sent from my ZP980 using Tapatalk
Thank you, your guide worked and my scripts in init.d now get executed
Sadly, exporting the variable in script residing in init.d does nothing (the script itself gets executed, i tried echoing "test" in file). There must be something, which keeps reseting the DIRECTORY_DCIM to its original value, or else i'm out of ideas
Or am i assuming incorrectly, that Java code
Code:
Environment.DIRECTORY_DCIM
should read env variable settable by
Code:
export DIRECTORY_DCIM="DCIM"
?
Actually now that you say that I checked my init.rc and I don't have that. Plus if I try
Code:
echo DIRECTORY_DCIM
I have nothing, so at least for me it's not set there.
Sent from my ZP980 using Tapatalk
For me echoing the varible also returns nothing, but reading it by Java returns "Camera".
Since it was my only clue, i hoped it could be reset by exporting DIRECTORY_DCIM (since android docs states that
android.os.Environment provides acces to environment vars) I guess i was wrong.
Is there any other kind of emvironment variables, i am not aware of?
Sent from my M353 using Tapatalk
I checked that variable is hardcoded in the android.os.Environment class.
I can think of three methods to test to change that but I didn't test any:
Use exposed framework to change the call that gets DIRECTORY_DCIM, if that's possible it's probably the best choice.
Edit and compile again android.os.Environment (I have no idea how to do that or if it's even possible)
Make a script that monitors your X folder to move pictures to DCIM folder
I can help you with the last one
The xposed is great idea, but unfortunately it doesn't work. It says "unknown option -- c" which as far as i know has something to do with bad (probably outdated?) version of SU. Meizu's firmware is probably more customized android than i previously thought.
Now i'm using the solution you also advised - i am automatically moving media from Camera to DCIM - i was hoping for more clean solution, but i guess this is as close as i'll ever get (don't get me wrong, it works as it is supposed to. I'm just a perfectionist )
Thank's for your time.
np I'm a perfectionist too and it's always cool to learn how things work and can be hacked
Sent from my ZP980 using Tapatalk