Database Users

Editing build.prop tutorial

I haven't seen a guide for this yet...but if there is mods please delete this.
Your build.prop is what tells android what your phone is. A Nexus S a Motorola Droid, or a Samsung Epic. Knowing how to change it can be EXTREMELY useful from tweaking your phone to faking it to run netflix.
There's 3 ways to modify your build.prop. You must have root (and busybox) for all of them, but I beleive if you want to you can unroot and it will stick.
ADB
Adb is a part of the android sdk, and is more for advanced users then novices. You can modify your build.prop by using adb and pulling it, editing it on your computer, and putting it back. Not the simplest way.
Type in adb:
Code:
adb pull /system/build.prop C:\Users\user\Desktop
Always replace "user" with your windows username
You should see a file named "build.prop" on your desktop. Open it with WORDPAD, not notepad. Change what you want. When your done, type this:
Code:
adb push C:\Users\user\Desktop\build.prop /sdcard/build.prop
This will put the build.prop on your sd card, since we cannot directly push to /system
Code:
adb shell
This should give you a shell. A shell is where you can run commands. After you have a shell, type:
Code:
su
mount -o remount,rw none /system
busybox cp /sdcard/build.prop /system/build.prop
mount -o remount,ro none /system
You have successfully changed your build.prop!
File Expert (or other free file managers) and text edit
This involves two apps, File Expert (or similar) and Text Edit. They can be found on the market here: File Expert and Text Edit
After you install these two apps, open File Expert. Click the menu button (the one on the phone), more, and Settings. Click on File Explorer Settings and click Root Explorer. It should request root, allow it. Press back twice to go back to your sd card. Then press back twice again. Click on /system. Press the menu button, more, and click mount. Select "Mount as Read Write". Now long click on build.prop and select File Operations. Click permission. A menu should pop-up, check the boxes so it looks like this
Code:
X X []
X X []
X X []
and click apply. Now, click on build.prop and it should say open as. Click text, then Text Edit.
Feel free to edit as you please! Once your done, click menu, then save. Then close the application. Don't forget to go to file expert and unmount system as rw, do this by going to the system folder and clicking menu, more, Mount, Mount as Read Only. Your done!
The easy way
Go buy an app. Really, some are worth the trouble. Two apps that will help edit your build.prop are Absolute System and Root Explorer
Thats about it. Any suggestions on how to edit, I'll add in this op. So be sure to leave them!

thanks for this! I have it bookmarked but where can i find common build prop edits?

You can also use ROM Toolbox to edit some items on the build.prop

For version 2 above, I use ES File Explorer and its built in ES Text Editor. One app instead of two. Same effect.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"

tq, nice info
Sent from my SCH-I500 using XDA App

awesome post. comes in handy

Is it not just possible to take the zip from a custom rom and modify it with Notepad++?

zanderman112 said:
For version 2 above, I use ES File Explorer and its built in ES Text Editor. One app instead of two. Same effect.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"
Click to expand...
Click to collapse
I came to say the exact same thing.
Sent from my SPH-D700 using Tapatalk

You may want to add quotes for the desktop directory in case their user name is "John Smith"
Sent from my SPH-D700 using Tapatalk

ugothakd said:
File Expert (or other free file managers) and text edit
This involves two apps, File Expert (or similar) and Text Edit. They can be found on the market here: File Expert and Text Edit
After you install these two apps, open File Expert. Click the menu button (the one on the phone), more, and Settings. Click on File Explorer Settings and click Root Explorer. It should request root, allow it. Press back twice to go back to your sd card. Then press back twice again. Click on /system. Press the menu button, more, and click mount. Select "Mount as Read Write". Now long click on build.prop and select File Operations. Click permission. A menu should pop-up, check the boxes so it looks like this
Code:
X X []
X X []
X X []
and click apply. Now, click on build.prop and it should say open as. Click text, then Text Edit.
Click to expand...
Click to collapse
If anyone has any problems, MAKE SURE you're using TEXT EDIT. That solved my problem! =D

Actually Z, root explorer will let you edit the text.
Sent from a phone with kNOw CIQ

So I got the editing part down, how about potential options. Like what identifies the device to the market? I wanna be able to increase my app compatibility and I'm wondering if changing from an ei22 fingerprint to something else may help?
sent from the other woman

bryanfritz1 said:
So I got the editing part down, how about potential options. Like what identifies the device to the market? I wanna be able to increase my app compatibility and I'm wondering if changing from an ei22 fingerprint to something else may help?
sent from the other woman
Click to expand...
Click to collapse
I'm not sure but I think it's your build I.d. Just woke up and still learning.
Via OG Epic 4g Cm9 & NYGiants 2012 Champions!!!!!

So here is my build.prop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. The part about ei22 and test keys can that be updated to something different (newer) and would that play a part in the market apps not being compatible? Thx guys just trying to understand how it all works together.
sent from the other woman

Hi!I have xperia mini with ICS.My device wake up if I push the volume button(unlock).I edit the build.prop.I writing this line:ro.config.hwfeature_wakeupkey = 0.
But this not working just with radio.Its not good with Proplayer.
Any solution?

My huawei 8650 sonic freeze after i do your steps because i forgot to install the busybox any idea what i can do ?
sry for my english...

Thank you so much!!!!!!:victory::victory::victory: o/

Nice OP!

Pure Awesomeness
Thanks a million! :good:

hey guys i need a big help whit that i was tweaking the build.prop of my pantech flex is already rooted but it get stock into the logo of att i mean it got brick so i decide to modifited the build.prop to the original i mean just erasing the lines i added to it but i was just fine doing the abd pull and the push to the sdcard build.prop but i get failed doing (su
mount -o remount,rw none /system
busybox cp /sdcard/build.prop /system/build.prop
mount -o remount,ro none /system) in the cmd it stay doing anything

[Guide] Fix / Reduce SGS3 Home Launcher Redraw - Tested on TouchWiz

This basic guide was requested by a few users who found the Elite Dev zeppelinrox instructions a little overwhelming, so I found a "little" time to whip this up for you and others.
This guide is written for rooted deodexed SGS3 ROMs only with TW OOM priority above 1 (lower value = higher priority and less likely to be killed off). The patch sets the OOM value of the HOME Launcher to 1.
Use Auto Memory Manager (AMM) to check TouchWiz Home OOM priority >1
Menu > Running Processes > Group by OOM grouping
++ For those using an alternative Home Launcher (eg. Apex), ensure that it is set as "default/home" launcher, so that OOM priority for only the HOME Launcher is changed. Any change to home launcher default will require reboot into CWM recovery and wipe advanced/dalvik. ++
Note: For Apex, I have only checked for OOM priority change, not for redraw.
Below: Unpatched ALF2 TW OOM Priority = 6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWO METHODS POSTED IN THIS GUIDE:
1. Modify your downloaded ROM.zip from Windows PC
2. From running ROM on Device
METHOD #1
* Modify your downloaded ROM.zip from Windows PC
Requirements:
1. 7-Zip
2. Root & CWM Recovery Thanks Chainfire!
3. Deodexed "ROM.zip" : Example = GT-I9300_WanamLite.XXALF2.V1.2.NO-WIPE.zip
4. Nandroid backup in CWM Recovery
1. Using 7-Zip on the PC, extract the services.jar from the ROM.zip system/framework/
a) Right click on ROM.zip > 7-Zip > open archive
b) Open system/framework
c) Extract services.jar to somewhere on the PC you can find it (Do not close 7-Zip system/framework/)
2. Upload the extracted services.jar to ICS OOM Priority Charger , follow the instructions there......
3. Download the patched services.jar to PC (the CWM.zip file may not work as it’ll most likely require the updater-script modified)
4. Naviagte to your patched services.jar, left click (hold) and drag into the open 7-Zip system/framework
5. Close 7-Zip & copy ROM.zip to sdcard
6. Boot into CWM Recovery, Nandroid backup
7. Wipe cache & advanced/dalvik
8. Flash ROM.zip
9. Use AMM app to check TouchWiz Home OOM priority =1
10. Enjoy
METHOD #2
* From running ROM on Device
Requirements:
1. Root
2. Root Explorer app or similar (instructions are for Root Explorer)
3. Deodexed ROM
4. Nandroid backup in CWM Recovery
1. Open up device browser http://android.mimic.ca/
2. File upload > choose file > Root Explorer > phone menu > home > system > framework > services.jar
3. This will exit to the ICS OOM Priority Charger webapp
4. Upload
5. Download > Save As "services.jar" > OK
6. Open Root explore and navigate to /sdcard/Download
7. Long tap services.jar > copy
8. Back > back > system > framework
9. Mount R/W
10. Paste > overwrite
11. Set permissions: long tap services.jar > permissions > rw-r--r--
12. Reboot
13. Use AMM app to check TouchWiz Home OOM priority =1
14. Enjoy
Note: Some widgets (weather) may occasionally redraw as their OOM priority may allow them to be killed off, but you should see reduced TW Launcher redraw.
HUGE THANKS to subvertbeats@XDA for pointing me in the right direction and of course blk_jack@XDA for ICS OOM Priority Charger and especially zeppelinrox@XDA for the services.jar patch instructions.
Added Disclaimer: All your own risk. I am not responsible for anything you may try here. I didn't make you do it, blah blah blah

Just to clarify, reading into the script a little it seems the priority changer changes the priority of the "home launcher", rather than "touchwiz home" itself in services.jar....
Am I reading this correctly?
So if someone were using, say Apex launcher as default home, this will still work as intended, and reduce the redraws on whichever app set as deafult home?
If so thank you VERY much

patchseven said:
Just to clarify, reading into the script a little it seems the priority changer changes the priority of the "home launcher", rather than "touchwiz home" itself in services.jar....
Am I reading this correctly?
So if someone were using, say Apex launcher as default home, this will still work as intended, and reduce the redraws on whichever app set as deafult home?
If so thank you VERY much
Click to expand...
Click to collapse
Just testing for you now.............
AMM > Apex OOM = 5
Set Apex as "home" launcher
Reboot and wipe dalvik
Check with AMM > Apex OOM = 1
YES, I belive it will, should work/help, I will edit my OP
Backup and test and see if theres any improvement in preventing the launcher being killed off, and causing redraw

Where to get ROM.zip?
UpInTheAir said:
1. Using 7-Zip on the PC, extract the services.jar from the ROM.zip system/framework/
a) Right click on ROM.zip > 7-Zip > open archive
Click to expand...
Click to collapse
thanks, where do i get this ROM.zip,can i deodox my stock services.jar and follow these steps?

oyam said:
thanks, where do i get this ROM.zip,can i deodox my stock services.jar and follow these steps?
Click to expand...
Click to collapse
The "ROM.zip" refers to a any custom ROM that is in .zip format used to flash from CWM Recovery.
Example: GT-I9300_WanamLite.XXALF2.V1.2.NO-WIPE.zip
Most custom ROMs are installed this way, so using method #1, you can just replace the services.jar before copying the custom ROM.zip to you sdcard for flashing.
I'll update the OP, again.

UpInTheAir said:
The "ROM.zip" refers to a any custom ROM that is in .zip format used to flash from CWM Recovery.
Most custom ROMs are installed this way, so using method #1, you can just replace the services.jar before copying the custom ROM.zip to you sdcard for flashing.
I'll update the OP, again.
Click to expand...
Click to collapse
Cool, thanks i will give a try

I've been trying this method many times, but to no avail. I'm currently running on the NoSympathy OTA ROM. I've tried both methods, as well as using adb push/pull then copying it to the folder, then fixing permissions, and still nothing. It's like that website for patching the services.jar isn't working. Apex Launcher is still set to 6, no matter what I've done.
Any ideas?

well if you are using Apex why not just tick "keep in memory" option?

I have, but I still get the redraw problems.

jefflikesbagels said:
I've been trying this method many times, but to no avail. I'm currently running on the NoSympathy OTA ROM. I've tried both methods, as well as using adb push/pull then copying it to the folder, then fixing permissions, and still nothing. It's like that website for patching the services.jar isn't working. Apex Launcher is still set to 6, no matter what I've done.
Any ideas?
Click to expand...
Click to collapse
Either your missing a step, ROM not compatible, permissions not set properly etc.
Have you rebooted after patching and wiped dalvik and cache in recovery?
Also, You could try to edit manually, link to zeppelinrox instructions in the OP. This may be a little overwhelming for some though.
Also, try his v6 supercharger script, this may help too. I think this has the option to patch during the setup process (read his thread)
Sent from my GT-P6810 using xda premium

UpInTheAir said:
Either your missing a step, ROM not compatible, permissions not set properly etc.
Have you rebooted after patching and wiped dalvik and cache in recovery?
Also, You could try to edit manually, link to zeppelinrox instructions in the OP. This may be a little overwhelming for some though.
Also, try his v6 supercharger script, this may help too. I think this has the option to patch during the setup process (read his thread)
Sent from my GT-P6810 using xda premium
Click to expand...
Click to collapse
I've tried this about 5 times, so I know I haven't missed a step. Maybe you're right about it not being compatible. I have the Verizon i535 GS3, so maybe there's a difference somewhere.
Thanks for the help though.

Stock Sgs rom
Can the redraw on the stock sgs3 rom be fixed using these same steps

Get Ram Manager from playstore.
Tick "Keep launcher in memory".
Solved the problem for me.
I only get redraws while coming out of games or something. Otherwise no redraw.
Trust me, it works.

That's a scam.
You said it yourself, you get redraws when you come out of a game.... LOL
It's like saying "I never crap until I poop"

zeppelinrox said:
That's a scam.
You said it yourself, you get redraws when you come out of a game.... LOL
It's like saying "I never crap until I poop"
Click to expand...
Click to collapse
Umm..yes..Only if I play games like NOVA or so..
Before that; if I browse for 20-30 mins or even go to playstore for 10-20 mins and hit on Homescreen button; there would be a redraw.
No its not at all.
Sometimes even waking up phone after a long time would cause it.
Now absolutely now. Infact my phone doesn't redraw at all unless I do a very heavy task.
By games I didn't mean Angry Birds.
Give it a try; it really makes things better.

That dev STOLE my OOM grouping fix and calls it lock home in memory.
He used to call it Hard To Kill which was stealing my "brand names" so I had that app pulled off the market until it was changed.
None of it does a single thing for launcher priority.
It's all BS... you get the same thing by lowering your minfrees but that would require you to know what you're doing.
SuperCharge it and then you'll know what's BS and what isn't.
Otherwise, you don't know crap about what is possible.

zeppelinrox said:
That dev STOLE my OOM grouping fix and calls it lock home in memory.
He used to call it Hard To Kill which was stealing my "brand names" so I had that app pulled off the market until it was changed.
None of it does a single thing for launcher priority.
It's all BS... you get the same thing by lowering your minfrees but that would require you to know what you're doing.
SuperCharge it and then you'll know what's BS and what isn't.
Otherwise, you don't know crap about what is possible.
Click to expand...
Click to collapse
If that's the case, he's no "dev" then.
Doesn't take much to take someone's hard work and call it their own. Need to give appropriate credit and if need be, ask first.
Sent from my GT-I9300 using xda premium

zeppelinrox said:
That dev STOLE my OOM grouping fix and calls it lock home in memory.
He used to call it Hard To Kill which was stealing my "brand names" so I had that app pulled off the market until it was changed.
None of it does a single thing for launcher priority.
It's all BS... you get the same thing by lowering your minfrees but that would require you to know what you're doing.
SuperCharge it and then you'll know what's BS and what isn't.
Otherwise, you don't know crap about what is possible.
Click to expand...
Click to collapse
Well I had no idea that he stole your work. Really sorry for that.
I can only tell from a consumer's POV that it actually works; and it's not a placebo.
Earlier if I browsed a page with lots of Images and go to home screen; it would re load.
Now it doesn't. At all.
I should commend you for it; since it's your work.
But it does work and now I'm not embarrassed to hand my phone for show off.
That relaod was crapping on my showoff :laugh:

I already have Touchwiz Home OOM priority set to 1 with ARHD 2.1.1.

eggman89 said:
Well I had no idea that he stole your work. Really sorry for that.
I can only tell from a consumer's POV that it actually works; and it's not a placebo.
Earlier if I browsed a page with lots of Images and go to home screen; it would re load.
Now it doesn't. At all.
I should commend you for it; since it's your work.
But it does work and now I'm not embarrassed to hand my phone for show off.
That relaod was crapping on my showoff :laugh:
Click to expand...
Click to collapse
It moves the launcher down a slot.
That's it.
It still gets killed in the same order as before.
I made the grouping limits more multitasking friendly.
Glad you enjoy getting screwed so much.
Now STFU about it because you still haven't a clue.
The app really is a piece of **** and represents all that is wrong with app development and kanging.

[TWEAKS/SCRIPTS/DOWNLOADS]~ BEST TWEAKS EVER ~ ((26-Oct))

Some great stuff from Amazing devs
-Androguide.fr Pimp My Rom {the best tweak :good:} ((October 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1908269[/url]
- AC!D AUDIO ENGINE Developers ((amazing sound experince))
Code:
[url]http://chautemseric.wix.com/acidaudiotechnology#!devices-support/cdfs[/url]
-croniccorey CronMod-A2SD/D2EXT/INT2EXT {best A2SD tweaks} ((updated 09/19))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909374[/url]
- CarlDeanCatabay Increase RAM using Swap File and Swap Partition and SD card partitioning ((great one try it))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1659231[/url]
-hyperbolic The Complete Guide For Maximum Battery Life {great battery life}
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909996[/url]
-PIT Tech GameBooster ★ root {great games experience }
Code:
[url]https://play.google.com/store/apps/details?id=com.burakgon.gamebooster[/url]
-OOM groupings and priorities tweaks - SuperCharger ((add it with loopy))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=991276[/url]
-Loopy Smoothness tweak ((add it with SuperCharger))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1137554[/url]
[url]http://forum.xda-developers.com/showthread.php?t=1205744[/url]
-droidphile Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs ((15th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1369817[/url]
-jader13254 MooDeD Holo Camera
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1742758[/url]
-Rizal Lovins Camera Mod v.4.0 Cybershot Experience
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1918744[/url]
-Arcatarc NotificationLedFix for 4.1.B.0.587 ((17th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1840114[/url]
Other tweaks or guidelines
-Patch your hosts file for blocking Ads
(please think before doing this; many developers are supported through this way)
You can use AdFree application for this or changing manually your hosts file.
Code:
[url]http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts[/url]
-Use UOT kitchen for basic theming on your device.
Code:
[url]http://uot.dakra.lt/[/url]
-Disable sync feature in sqlite
(author: ownhere - needs a source for your device so you can compile the /system/lib/libsqlite.so)
Code:
[url]http://forum.xda-developers.com/showthread.php?t=903507[/url]
-Use CyanogenMOD's APN list file - one of the most complete located in
Code:
/system/etc/apns-conf.xml
-Do not use task killers.

for GOD sake ... don't use them all... SELECT/MODIFY according to your ROM and what you want.
WARNING
Note: if you don't know what you are doing please don't try. read first and make sure you understand what you are doing and make a backup before doing any mods. i am not responsible for messing up your device but the ARC community and i may assist.
TO WHO CARE TO KNOW
What is build.prop:
- The build.prop file is your android handset’s ‘ID card’.
- It tells applications the specifications of your device, so that apps can change their interface or function for your specific device.
- Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer.
- Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.
- The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don't know what you are doing, you can actually decrease the performance of your device. Over time I will investigate more build.prop properties to determine which ones can actually enhance your Android experience and which ones only create a placebo effect
XperienceD said:
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also sift through what works and what doesn't.
Click to expand...
Click to collapse
WAIT
REQUIREMENT BEFORE YOU START :-
- Make a NANDROID BACKUP
- If you have any V6 Supercharger tweaks installed, un-supercharge before doing these tweaks. Once finished, you may re-supercharge and
- Root (Superuser/Busybox/Terminal Emulator/ES File Explorer),
- kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/)This requires edits in build.prop and the use of terminal emulator
- If your build.prop has an additional build properties section the line of code needs to go in there
(If lines starting with dalvik.vm.checkjni=false or windowsmgr.max_events_per_sec=300 exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
How to
Replace OR tweaks Build.prop :-
1. Download Es File Explorer ((OR ANY APP LIKE IT))
2.CLick menu, settings, check Root Explorer and Mount File System
3.Copy the Build.prop file into the sd card and copy with file manager
4.Click Favorites tab, Click Phone icon /
5.Navigate to system/
6.Rename build.prop to build.bak
7.Paste build.prop you copied earlier Reboot! Done! :good:
Build.prop tweaks((UPDATED 26-Oct))
Add these at the end of your build.prop
Code:
IN THE ATTACHMENT
~ Free Up More RAM, Make Apps Load Faster ~
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
Code:
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Add these lines to the bottom of build.prop using Root Explorer -- or any other app of your favorite
.
(If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
Code:
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
After this, run these two commands in adb shell or terminal emulator
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
3) Okay, this step is only for those who experience errors from typing the following lines from Step 2:
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
**If you got the error, make sure to undo the tweak since now you are probably experiencing FC's right now and start all over. The undo process**
How to UNDO this tweak
Type the following in adb shell or terminal emulator
((also u can users, skip the 3rd and 4th lines. That starts with "rm" and instead, reboot in recovery and clear cache partition and dalvik-cache but better to do it all))
Code:
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
So just make sure you have done Step 1 and the edits of build.prop from Step 2 correctly. After that, reboot into recovery and clear cache partition and clear dalvik-cache. Thats all.
Init.d tweaks ((UPDATED 26-Oct))
(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)
Note:
1- If you have init.d problem or if not have init.d folder try add this line at hw_config.sh
2- some (needs zipalign bin) #!/system/xbin/bash,so it needs the bash file in the /system/xbin folder in order to work
Code:
I COLLECT A LOT OF THEM
IT TOOK ME ALLOT OF TIME AND EFFORT
I PUT THEM IN TEXT
IN THE ATTACHMENT
DELETED WHICH IS DUPLICATED
& MODIFIED SOME
I COULDN'T WRITE THEM ALL HERE
CAUSE ITS SO BIG TO WRITE IT HERE
THEY JUST ALLOW AMOUNT OF LINE FOR ME
SO I PUT THEM ALL IN TEXT DOCUMENT IN THE ATTACHMENT
EVERY DEVS NAME NEAR HIS SCRIPTS
ANYONE COULD DO THEM IN FLASH ABLE ZIP IT WILL BE GREAT
GOOD LUCK TO ALL
THE RAR IS JUST THE TWEAK NOT FLASH ABLE ONE
sysctl tweaks ((UPDATED 26-Oct))
To make them work:
1. make a new file in /system/etc/init.d, name it sysctl tweaks
2. make a new file in /system/etc, name it sysctl.conf
3. Paste the right code in the right file
-To activate sysctl tweaks
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
-sysctl.conf
Code:
IN THE ATTACHMENT

Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
I COLLECT MOST OF THEM AND WE WILL POINT WHAT IS FAKE AND WHAT IS NOT
Build.prop tweaks
some was big placebo
and i was saying way my phone gone bad and my gf and my friends
cause alllllllllll was fake
some are not but its already been put to the tweaks up
prove of what i said
first one thanx to the amazing XperienceD
- first one by XperienceD thanx
second
3g tweak its just a big lie
http://forum.xda-developers.com/showthread.php?t=1610444
http://forum.smartphonegeeks.in/index.php?topic=2414.0
i will keep digging to clean the net from placebo tweaks so my plan is not to **** any phone any more and make universal tweaks works with every one
and point out what is never worked and was just a placebo effect. and which have compatibility issues with ICS
so we can Unleash our device Hidden Powers thats my goal​

Thanks for the info man
But just some advice, I found that some of the tweak mentioned above is somewhat experimental
I forgot which ones, but after doing some research on google, they are indeed not yet fully tested (the effect is still unnoticeable)
And it will be great if you make the thread (2nd post to be more specific) to be more tidy
There are same tweaks mentioned more than one time, it might not good for people to copy and paste the tweaks directly from your thread
Cheers

fakhreza said:
Thanks for the info man
But just some advice, I found that some of the tweak mentioned above is somewhat experimental
I forgot which ones, but after doing some research on google, they are indeed not yet fully tested (the effect is still unnoticeable)
And it will be great if you make the thread (2nd post to be more specific) to be more tidy
There are same tweaks mentioned more than one time, it might not good for people to copy and paste the tweaks directly from your thread
Cheers
Click to expand...
Click to collapse
MAN
First thanx to tell me about my mistake of putting the same tweaks twice
Second i tidy it more now every tweak title will start with #
Third experimental yes some r but u will see improvment
thanx again

dr said:
Third experimental yes some r but u will see improvment
thanx again
Click to expand...
Click to collapse
And some just don't work - http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/

XperienceD said:
And some just don't work - http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
Click to expand...
Click to collapse
sorry for that :angel:
am just trying to help
i just updated for other new stuff and cool tweaks
best wishes

i add huge update and new tweaks and arrange it in better way

dr said:
i add huge update and new tweaks and arrange it in better way
Click to expand...
Click to collapse
thanx great collection

dr said:
am just trying to help
Click to expand...
Click to collapse
So am I.

If these things really improve experience, why Sony didn't add theme to their devices in official roms ?
They are professional developers after all ?

XperienceD said:
So am I.
Click to expand...
Click to collapse
thanx :good:
n4ki said:
If these things really improve experience, why Sony didn't add theme to their devices in official roms ?
They are professional developers after all ?
Click to expand...
Click to collapse
why sony didn't fix led bug and they did it here
why sony roms vs good modified stock roms suck
so simple
welcome to android world

dr said:
thanx :good:
Click to expand...
Click to collapse
I found that link whilst searching for mods and used to use some myself, but when you take in to account...
The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don’t know what you are doing, you can actually decrease the performance of your device.
Click to expand...
Click to collapse
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also shift through what works and what doesn't.

yes as i already said in an other thread, it would be helpful known which of these improove our Arc/Arc S and which one deprove some roms, for example the JS 6.1 which im using

XperienceD said:
I found that link whilst searching for mods and used to use some myself, but when you take in to account...
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also shift through what works and what doesn't.
Click to expand...
Click to collapse
noooooooooooooooooooooooooooooooooooooooooooo
noooooooooooooooooooooooooooooooooooooooo
noooooooooooooooooooooooooooooooooo
i didnt take it in to account really its my first time to make thread and i thought u attak me while those not mine
in other way u can say it in deffrent way so i will understand what u want me to understand i will add ur link to the collection
am sorrrrrrrrrrrrrrrrry really soooooooooooo much if i efended u
and thats right lets start to see what is working and what is not
by the way i add and correct some
and trying to do what i can do for helping whom i can
again thanx and soooooooooory if i did something bad
danybhai said:
thanks
Click to expand...
Click to collapse
at ur service alll the time welcome
deniel said:
yes as i already said in an other thread, it would be helpful known which of these improove our Arc/Arc S and which one deprove some roms, for example the JS 6.1 which im using
Click to expand...
Click to collapse
for me i dont use any rom i just root the stock one and play with it for me the last build one works with me
although i went through the web and see some and puts the best value for the best berformance and whats work with me maybe didnt work with u so try and tell us it will be great help

dr said:
again thanx and soooooooooory if i did something bad
Click to expand...
Click to collapse
No offence taken, obviously just a mis understanding.

Thankx for ur hardwork

xperienced said:
no offence taken, obviously just a mis understanding.
Click to expand...
Click to collapse
glad to hear that
cimi244 said:
thankx for ur hardwork
Click to expand...
Click to collapse
all the time welcome
glad to help

why
i get bootloop
alllllllllllllllllllllllllllllllllllllllllllllll
the time when i update the Build.prop tweaks
in JELLY SANDWICH 6.1
and i noticed also the same thing
some Build.prop tweaks repeated twice but with deffrint value in defferint tweak pak
but the rom work like charm :laugh: any idea

dr said:
Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))​
- first one by XperienceD thanx
Click to expand...
Click to collapse
The battery tweaks that you posted in the second post - what does they improve? Huh?

[TWEAKS/SCRIPTS/DOWNLOADS]~ Unleash Your device Hidden Powers ~ ((19-Oct))

Some great stuff from Amazing devs
-Androguide.fr Pimp My Rom {the best tweak :good:} ((October 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1908269[/url]
- AC!D AUDIO ENGINE Developers ((amazing sound experince))
Code:
[url]http://chautemseric.wix.com/acidaudiotechnology#!devices-support/cdfs[/url]
-croniccorey CronMod-A2SD/D2EXT/INT2EXT {best A2SD tweaks} ((updated 09/19))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909374[/url]
-hyperbolic The Complete Guide For Maximum Battery Life {great battery life}
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1909996[/url]
-PIT Tech GameBooster ★ root {great games experience }
Code:
[url]https://play.google.com/store/apps/details?id=com.burakgon.gamebooster[/url]
-OOM groupings and priorities tweaks - SuperCharger ((add it with loopy))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=991276[/url]
-Loopy Smoothness tweak ((add it with SuperCharger))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1137554[/url]
[url]http://forum.xda-developers.com/showthread.php?t=1205744[/url]
-droidphile Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs ((15th September 2012))
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1369817[/url]
Other tweaks or guidelines
-Patch your hosts file for blocking Ads
(please think before doing this; many developers are supported through this way)
You can use AdFree application for this or changing manually your hosts file.
Code:
[url]http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts[/url]
-Use UOT kitchen for basic theming on your device.
Code:
[url]http://uot.dakra.lt/[/url]
-Disable sync feature in sqlite
(author: ownhere - needs a source for your device so you can compile the /system/lib/libsqlite.so)
Code:
[url]http://forum.xda-developers.com/showthread.php?t=903507[/url]
-Use CyanogenMOD's APN list file - one of the most complete located in
Code:
/system/etc/apns-conf.xml
- SD card partitioning
Code:
[url]http://forum.xda-developers.com/wiki/SD_card_partitioning[/url]
-Do not use task killers.

Note: if you don't know what you are doing please don't try. read first and make sure you understand what you are doing and make a backup before doing any mods. i am not responsible for messing up your device but the ARC community and i may assist.
What is build.prop:
- The build.prop file is your android handset’s ‘ID card’.
- It tells applications the specifications of your device, so that apps can change their interface or function for your specific device.
- Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer.
- Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.
- The build.prop file is a powerful tool for root users to modify the behavior of various aspects of the Android experience. However, there are no secret values here that are going to instantly make your phone run faster, better, smarter, or more efficiently. In fact, if you don't know what you are doing, you can actually decrease the performance of your device. Over time I will investigate more build.prop properties to determine which ones can actually enhance your Android experience and which ones only create a placebo effect
XperienceD said:
...it helps to know what works and what doesn't, causes conflicts, do you need to use one tweak if you're using another etc and all those classed as "busted" I'll never use again. So while it's great to have it all collected in one place lets also sift through what works and what doesn't.
Click to expand...
Click to collapse
NOTE :- please if u have any other tweaks or some of this tweaks are busted tell me or pm me
i put all the tweaks togethers and i arrange them accordingly so u can find easily what u have and what u don't and what is working and what is not so hope it will be good help for u​
WAIT REQUIREMENT BEFORE YOU START :-
- Make a NANDROID BACKUP
- If you have any V6 Supercharger tweaks installed, un-supercharge before doing these tweaks. Once finished, you may re-supercharge and
- Root (Superuser/Busybox/Terminal Emulator/ES File Explorer),
- kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/)This requires edits in build.prop and the use of terminal emulator
- If your build.prop has an additional build properties section the line of code needs to go in there
(If lines starting with dalvik.vm.checkjni=false or windowsmgr.max_events_per_sec=300 exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
How to replace OR tweaks Build.prop :-
1. Download Es File Explorer ((OR ANY APP LIKE IT))
2.CLick menu, settings, check Root Explorer and Mount File System
3.Copy the Build.prop file into the sd card and copy with file manager
4.Click Favorites tab, Click Phone icon /
5.Navigate to system/
6.Rename build.prop to build.bak
7.Paste build.prop you copied earlier Reboot! Done! :good:
Build.prop tweaks((UPDATED 19-Oct))
Add these at the end of your build.prop
Code:
IN THE ATTACHMENT
~ Free Up More RAM, Make Apps Load Faster ~
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
Code:
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) Add these lines to the bottom of build.prop using Root Explorer -- or any other app of your favorite
.
(If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already in build.prop, please modify them as shown below. Obviously if it isn't already in build.prop, just add it in.)
Code:
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=a,u=y,m=y
As shown:((here written v=n,o=v so the new one is v=n,o=a,u=y,m=y))
After this, run these two commands in adb shell or terminal emulator
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
3) Okay, this step is only for those who experience errors from typing the following lines from Step 2:
Code:
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
**If you got the error, make sure to undo the tweak since now you are probably experiencing FC's right now and start all over. The undo process**
How to UNDO this tweak
Type the following in adb shell or terminal emulator
((also u can users, skip the 3rd and 4th lines. That starts with "rm" and instead, reboot in recovery and clear cache partition and dalvik-cache but better to do it all))
Code:
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
So just make sure you have done Step 1 and the edits of build.prop from Step 2 correctly. After that, reboot into recovery and clear cache partition and clear dalvik-cache. Thats all.
Init.d tweaks ((UPDATED 19-Oct))
(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)
Note:1- If you have init.d problem or if not have init.d folder try add this line at hw_config.sh
2- some (needs zipalign bin) #!/system/xbin/bash,so it needs the bash file in the /system/xbin folder in order to work
Code:
I COLLECT A LOT OF THEM
AND I PUT THEM IN TEXT
IN THE ATTACHMENT
AND DELETED WHICH IS DUPLICATED
I COULDN'T WRITE THEM ALL HERE
CAUSE ITS SO BIG TO WRITE IT HERE
THEY JUST ALLOW AMOUNT OF LINE FOR ME
SO I PUT THEM ALL IN TEXT DOCUMENT IN THE ATTACHMENT
EVERY DEVS NAME NEAR HIS SCRIPTS
ANYONE COULD DO THEM IN FLASHABLE ZIP IT WILL BE GREAT
GOOD LUCK TO ALL
THE RAR IS JUST THE TWEAK NOT FLASHABLE ONE
sysctl tweaks ((UPDATED 19-Oct))
To make them work:
1. make a new file in /system/etc/init.d, name it sysctl tweaks
2. make a new file in /system/etc, name it sysctl.conf
3. Paste the right code in the right file
-To activate sysctl tweaks
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
-sysctl.conf
Code:
IN THE ATTACHMENT

Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
Build.prop tweaks
some was big placebo
and i was saying way my phone gone bad and my gf and my friends
cause alllllllllll was fake
some are not but its already been put to the tweaks up
prove of what i said
first one thanx to the amazing XperienceD
- first one by XperienceD thanx
second
3g tweak its just a big lie
http://forum.xda-developers.com/showthread.php?t=1610444
http://forum.smartphonegeeks.in/index.php?topic=2414.0
i will keep digging to clean the net from placebo tweaks so my plan is not to **** any phone any more and make universal tweaks works with every one
and point out what is never worked and was just a placebo effect. and which have compatibility issues with ICS
so we can Unleash our device Hidden Powers thats my goal​

JUST IN CASE

NIce one... But U need to throw more light. Some of the mods never worked and was just a placebo effect. and some of them hav compitability issues with ICS. And in ur sign i dint see S2 device. Did u try these on Xperia ARC S and posting or did u try on S2?

Tweaks wich didnt wrok "busted" we will never use again and been test by users ((thanx to XperienceD for this great idea))
I COLLECT MOST OF THEM AND WE WILL POINT WHAT IS FAKE AND WHAT IS NOT
Build.prop tweaks
some was big placebo
and i was saying way my phone gone bad and my gf and my friends
cause alllllllllll was fake
some are not but its already been put to the tweaks up
prove of what i said
first one thanx to the amazing XperienceD
- first one by XperienceD thanx
second
3g tweak its just a big lie
http://forum.xda-developers.com/showthread.php?t=1610444
http://forum.smartphonegeeks.in/index.php?topic=2414.0
i will keep digging to clean the net from placebo tweaks so my plan is not to **** any phone any more and make universal tweaks works with every one
and point out what is never worked and was just a placebo effect. and which have compatibility issues with ICS
so we can Unleash our device Hidden Powers thats my goal​

UPDATED ((11-Oct))

updated ((19-oct))

For those having issues editing their build.prop in Marshmallow,or other system files

As ive been reading about this very much lately, after people have flashed Marshmallow and rooted, many are having issues editing their build.prop files. And many arent having any issues at all. Well, the fix is rather easy. You are going to have to change your SElinux to be permissive. Many that arent having the issue is because they are either using a custom kernel that has set SElinux to be permissive, or are using an app to change it. I use an app, dir viper4, because it needs to gave SElinux at permissive. There arent any apps that do it in the play store, because google removed them. But.. theres a site called xda that somebody is posting their SElinux changer app in http://forum.xda-developers.com/showthread.php?t=2524485

setenforce 0 don't work no mo on dat m?
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
setenforce 0 don't work no mo on dat m?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
probably does, but an app that does it would be easier, for most. but you are right

Why did Google remove the apps that allow you to do this?

rester555 said:
Why did Google remove the apps that allow you to do this?
Click to expand...
Click to collapse
security?

simms22 said:
About Google removing apps . . . . . . .security?
Click to expand...
Click to collapse
Just assuming . . . Google dev's have managers that puts them under pressure. . . Why. . .
1. Deals with telecom providers; demanding special factory images. Project Fi.
2. Ignoring many user requests; forcing encryption and forcing to use apps with text on white background.
3. Dark material removed since M-preview 3.
4. Use of RRO layers needs root access.
5. Deals with banks for Android Pay; not working when rooted.
6. Bloat. Built-in apps that should be in the play store.
7. Privacy. Services that can't be blocked.
8. Boot message device corrupt when it isn't.

This 6.0 update is a much bigger pain in the ass then it needs to be. Especially for Nexus devices which are suppose to be "mod" friendly. What gives Google?

First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.

NLBeev said:
Just assuming . . . Google dev's have managers that puts them under pressure. . . Why. . .
1. Deals with telecom providers; demanding special factory images. Project Fi.
2. Ignoring many user requests; forcing encryption and forcing to use apps with text on white background.
3. Dark material removed since M-preview 3.
4. Use of RRO layers needs root access.
5. Deals with banks for Android Pay; not working when rooted.
6. Bloat. Built-in apps that should be in the play store.
7. Privacy. Services that can't be blocked.
8. Boot message device corrupt when it isn't.
Click to expand...
Click to collapse
There are many logical reasons, however.
1)ProjectFi actually NEEDS special factory images
2)Security
3)It was unstable and needs more work (they are improving it for future releases)
4)I'm actually not sure about this one... I agree with you
5)Security
6)They've remove most apps like PinyinIME and HindiIME from the system with 6.0
7)Security
8)Security

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dang old security. Pha. Lol. Don't need permissive w viper. [emoji12]
Official Team Bliss Flo, Deb, v410 Maintainer
Sent from my Nexus 6 using Tapatalk

if i make any changes to build.prop at reboot my phone just sits at the Google screen. Even after setting SElinux to be permissive.
Any other solutions???
I'm running MRA58k rooted with supersu v2.50

mrizvi66 said:
if i make any changes to build.prop at reboot my phone just sits at the Google screen. Even after setting SElinux to be permissive.
Any other solutions???
I'm running MRA58k rooted with supersu v2.50
Click to expand...
Click to collapse
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?

Pecata said:
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Click to expand...
Click to collapse
yes, I made a backup. so i'm up and running.
all i tried to add was:
net.tethering.noprovisioning=true
i added it at the very bottom. i've done it before on lollipop and it worked before i'm not sure why it's not working now tho.

mrizvi66 said:
yes, I made a backup. so i'm up and running.
all i tried to add was:
net.tethering.noprovisioning=true
i added it at the very bottom. i've done it before on lollipop and it worked before i'm not sure why it's not working now tho.
Click to expand...
Click to collapse
if you make any spelling errors or gramatical errors, or miss any spaces, your phone wont ever boot up.

Pecata said:
What kind of changes did you make? Did you do a backup of the build.prop file before the changes?
Click to expand...
Click to collapse
simms22 said:
if you make any spelling errors or gramatical errors, or miss any spaces, your phone wont ever boot up.
Click to expand...
Click to collapse
does it need an extra space at the end of the file? i think i might have removed that.

mrizvi66 said:
does it need an extra space at the end of the file? i think i might have removed that.
Click to expand...
Click to collapse
no.
i use root explorer to edit my build.prop btw. what ill do is just copy/paste the line in, save it, then reboot. and it always is fine(unless i write it myself and mess it up).

simms22 said:
no.
i use root explorer to edit my build.prop btw. what ill do is just copy/paste the line in, save it, then reboot. and it always is fine(unless i write it myself and mess it up).
Click to expand...
Click to collapse
that's exactly what i do.
i just tried it again right now and it worked. strange.
thanks for you help both of you :good:

doitright said:
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
Click to expand...
Click to collapse
Great advice on local.prop. Did not know this before. Read up on it and sounds more useful especially when applying edits you dont want to re-enter after each flash.
(Take all this with caution) Good to note for others that local.prop is read after build.prop in boot up (hope i got that right), so you can use the same lines in build.prop in local.prop with changes in the values. Those values in local.prop will override those in build.prop! *except if the same line in build.prop begins with ro. "read only". **apparently the addition of qemu. in place of ro. in local.prop will override the build.prop line setting that had ro. at the beginning. Now does anyone know what qemu is exactly? Emulator? For hardware?

MunkinDrunky said:
Great advice on local.prop. Did not know this before. Read up on it and sounds more useful especially when applying edits you dont want to re-enter after each flash.
(Take all this with caution) Good to note for others that local.prop is read after build.prop in boot up (hope i got that right), so you can use the same lines in build.prop in local.prop with changes in the values. Those values in local.prop will override those in build.prop! *except if the same line in build.prop begins with ro. "read only". **apparently the addition of qemu. in place of ro. in local.prop will override the build.prop line setting that had ro. at the beginning. Now does anyone know what qemu is exactly? Emulator? For hardware?
Click to expand...
Click to collapse
qemu is the virtual machine infrastructure used for the android emulator. It is far more generic than for just the android emulator, but android does use it. The prefixes used imply a priority, and qemu (because of its association with the emulator for testing) is considered as for testing and development purposes, so it can, as you say, override.

doitright said:
First thing that comes to mind, is that you shouldn't EVER BE editing /system/build.prop. Its purpose is that it is generated by the build, hence "build".prop. If you need custom properties added to the system, use /data/local.prop.
Second thing is that most of the problems with system partition edits are NOT due to selinux problems. Most are because the factory sysimage bloats it absolutely FULL of crap. Delete some junk like google photos (which is a bloated pig).
Third, there is *absolutely no* reason to disable selinux. Just switch your context to one that matches the files you are trying to interact with. The su command has a parameter "--context" that lets you do this. Look it up.
Click to expand...
Click to collapse
I am sorry if this is a stupid question but when you say data/local.prop-do you mean root/data/ or just data/ in internal memory?
and if I create local.prop and add the line qemu.hw.mainkeys=1 in local.prop would that be able to hide the navigation bar even if the I don't touch build.prop?