yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] howtomen:
Im just saying that they are placebo as its lacking perms... maybe setting correct perms would allow them to work... and u would get real results instead of benchmarks...also video hardware one im familiar with... and the purpose is to enable hardware acceleration... which is enabled by default in ics so that for sure is useless...

im on my phone. expect terrible typos.
[T-Mobile, Samsung Galaxy SIII] fcortes626:
then open a thread that shows how to set the correct perms?:fingers-crossed:
[T-Mobile, Samsung Galaxy SIII] howtomen:
You can set perms through a root explorer such as es file explorer clock properties and allow the buildprop to execute

im on my phone. expect terrible typos.
[T-Mobile, Samsung Galaxy SIII] Chilled26:
What are the correct perms?
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
If these are placed in the ROM to begin with, then the ROM is flashed....the correct perms should be set on flash.

Or am I thinking wrong....
[T-Mobile, Samsung Galaxy SIII] overground:
No you are correct. As a matter of fact, I've never had to touch permissions after pushing a build.prop, then rebooting.
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
Thank you, that's what I thought :)
[T-Mobile, Samsung Galaxy SIII] fcortes626:
only time i change permissions to the build.prop is when i copy the file back from the sdcard using root explorer. even then wouldnt it automatically change the permissions on boot?
[T-Mobile, Samsung Galaxy SIII] fcortes626:
why execute? i never heard of setting the permission on a build.prop to execute. as far as i know its supposed to be rw-r-r. its not a script so why would it need to execute? soe of these are applied to my transformer prime, stock rooted, and locked bootloader. i dont have it set to execute and my benchmark scores doubled.
[T-Mobile, Samsung Galaxy SIII] howtomen:
Execute to run ur commands that u added... how else would it take effect

wrong it has to be added in updater script

Look.above u need to set perms in updater script

im on my phone. expect terrible typos.
[T-Mobile, Samsung Galaxy SIII] fcortes626:
before you edit the build.prop the permissions are set to rw-r-r. how would it read the factory settings then?
[T-Mobile, Samsung Galaxy SIII] howtomen:
Factory settings have perms already... these arent in the buildprop...

im on my phone. expect terrible typos.
[T-Mobile, Samsung Galaxy SIII] fcortes626:
makes no sense. why wouldnt samsung set default permissions to execute?:confused:
[T-Mobile, Samsung Galaxy SIII] Disconn3ct:
Because execute doesn't mean "use this configuration file." You had it right in the other post - execute is for scripts and executables, not configs. (And not images, and not sounds, etc.) It is a little more complicated for directories, but not that much more.
[T-Mobile, Samsung Galaxy SIII] jdbeitz:
Awesome thread man. I'll throw some of these in my build.
[T-Mobile, Samsung Galaxy SIII] fcortes626:
so bottom line do we need to add execute permission? and to who (ie.owner)?

i just got my phone exchanged so im about to root again. but this time im only sticking to the tmobile section lol:victory:
[T-Mobile, Samsung Galaxy SIII] fcortes626:
cool ill try to look for some more and test different values to see how it performs better.
[T-Mobile, Samsung Galaxy SIII] Disconn3ct:
no execute for 2 reasons. First, original perms are rw-r--r and second, because configuration files don't get x.
[T-Mobile, Samsung Galaxy SIII] fcortes626:
ok cool so i was right:victory:
[T-Mobile, Samsung Galaxy SIII] nonmindo:
haha, no i spelled it correctly when I put it on my phone, I have terrible spelling so I always triple, sometimes quadruple check my spelling when I'm working in the build.prop

Sadly, ADB would not detect the phone, I had all the drivers installed and everything, ODIN could see it and everything

End result tho, I couldnt wait for the factory ODIN to be posted as at the time it hadn't been posted yet so i just went to my local store, claimed it got hot when playing NOVA 2, rebooted and wouldnt go any further than the Galaxy S III screen, they swapped it out for me :)
[T-Mobile, Samsung Galaxy SIII] howtomen:
Sigh i give up... u guys can continue ur placebo gb stuff.. here half of this stuff doesnt work and what does needs certain perms but if u feel this works than have a party with it...

im on my phone. expect terrible typos.
[T-Mobile, Samsung Galaxy SIII] franknozly:
That wasn't pretty.

..

I changed a few options on the build.prop, took a backup of my original build.prop file and tried to reboot... screen is blank after the samsung s III logo.

I can adb shell and modify things and even restore the original build.prop file but it still has the same problem. Still doesn't show anything beyond the logo.

Going to try restoring my old nandroid system partition. If that fails then I'll restore the entire backup. If that fails I'm going to weep quietly in the corner of my room and .. OH LOOK restoring the /system partition worked! lol
[T-Mobile, Samsung Galaxy SIII] fcortes626:
are you sure you didnt make a typo? that doesnt happen to me:confused: i can send you a copy of the build.prop im using if you want it. on it i deleted some lines that seemed like they were dropping my benchmark but im still trying different values.
[T-Mobile, Samsung Galaxy SIII] overground:
I stand corrected. Howtomen is right. Should have tried before I spoke. Odd the way this device works.

So what permissions need to be in place for build.prop after a change in order for it to boot?
[T-Mobile, Samsung Galaxy SIII] franknozly:
I copy and pasted. If there was a typo it wasn't mine.

Second of all why did the original unmodified build.prop still not boot when I restored it? Damage has been done to other sections of my system partition?
[T-Mobile, Samsung Galaxy SIII] dave2metz:
I don't know about you guys, but this looks like a foreign language to me... Lol.

Sent from my Pebble Blue Galaxy S3
[T-Mobile, Samsung Galaxy SIII] fcortes626:
Maybe its not the build.prop causing the problem. Did you modify any other file?
[T-Mobile, Samsung Galaxy SIII] franknozly:
Don't see how that's possible when all I did was:

adb shell
su
mount -o remount,rw /system
cp build.prop /mnt/sdcard/build.prop.original
rm build.prop
(pulled file from phone, modified using copy paste of the few options I wanted)
adb push build.prop.modified /system/build.prop
adb reboot

See anything wrong with what I did?
[T-Mobile, Samsung Galaxy SIII] overground:
It is most definitely a permissions issue after a build.prop replacement.
[T-Mobile, Samsung Galaxy SIII] franknozly:
I made sure the permissions looked the same as before,

-rw-r--r-- root root

Hell I even gave it chmod 777 just to see if it would help. (It didn't)
[T-Mobile, Samsung Galaxy SIII] fcortes626:
i dont do it that way. i usually copy it to my sdcard edit it on my pc and put it back on my sdcard and move it with root explorer. i think thats the best way to do it. might not be the fastest but its the safest.
[T-Mobile, Samsung Galaxy SIII] franknozly:
rebooting the system automatically mounts the system partition back to read-only.
[T-Mobile, Samsung Galaxy SIII] omar300:
can you please upload your build.prop? i messed up mine and now have to push in to bricked phone. thanks
[T-Mobile, Samsung Galaxy SIII] Chilled26:
Happened to me 3 times messing with the build prop and prop editor app. You can just reflash the recovery and restore a backup.
[T-Mobile, Samsung Galaxy SIII] omar300:
please tell me how you restored /system, if possible in P.M with some detail cus ill be doing this for first time.

---------- Post added at 06:05 AM ---------- Previous post was at 05:58 AM ----------

HOW! i only know how to root and use cwm to flash roms, other than that i dont know anything.

i dont have any backup besides nandroid which i have one copy in computer and other in phone, i think i made mistake with giving permission to build.prop , now it turns one, shows galaxy s3 logo and turns off.

please tel me i can still bring this phone back to life.

please tell what you mean and how it is done. thanks
[T-Mobile, Samsung Galaxy SIII] Chilled26:
If you can still get to cwm recovery just restore your nandroid backup. If not then re install cwm recovery the way you did it the first time.
[T-Mobile, Samsung Galaxy SIII] franknozly:
In cm recovery go to backup/restore. Then advanced restore. Then choose the backup you made, then pick restore system partition. Click yes you are sure. Then reboot.
[T-Mobile, Samsung Galaxy SIII] omar300:
i cant get to recovery, how did you manage to get to recovery? ur issue sounds same like mine so how were you still able to proceed
[T-Mobile, Samsung Galaxy SIII] franknozly:
I could get into recovery. Are you sure you're doing it right? If you can't then redo the Odin and flash recovery again.
[T-Mobile, Samsung Galaxy SIII] omar300:
IT WORKED! YYYAYYYY!

phew, i though i had lost hopes.
[T-Mobile, Samsung Galaxy SIII] shineproductions:
How do I unbrick my phone?

The same thing happened to me.

The phone will not boot after editing "build.prop".

I "CAN" get into "recovery".

BUT... I do not have a backup to restore.

Is there a way to push a "build.prop"?

If not, where/how can I use recovery to fix my phone?

Will flashing a ROM help?

If so, how do I get the ROM on the phone?

I thought that I made a backup, but I guess I didn't. ooops! (never again!)

Please help!!!
[T-Mobile, Samsung Galaxy SIII] franknozly:
You're mostly screwed. You either need someone else's backup for your phone model or install a rom. Refer to the actual rom thread for flashing instructions.

A warning for others, don't play with your system partition without a backup. And if you don't know how to backup then you shouldn't be trying anything in the first place.
[T-Mobile, Samsung Galaxy SIII] mrvirginia:
can anyone tell me the difference between these two? should they both be 256?

i've tried looking up heapgrowthlimit but can't seem to find any info. thanks

dalvik.vm.heapgrowthlimit=256m

dalvik.vm.heapsize=256m
[T-Mobile, Samsung Galaxy SIII] aznmode:
I have bad signal at work and home and was wondering if the signal modification helps? Currently my db is between 105-113db when I hold it and once I go beyond 113db it goes to edge and have to put the phone down to let it go back to 4g.
[T-Mobile, Samsung Galaxy SIII] ruterjunior:
very nice! good work! is perfect!

just correct this wrong

rio.ril.disable.power.collapse=1

for correct

ro.ril.disable.power.collapse=1

and this too

dalvik.vm.startheapsize-8M

for

dalvik.vm.startheapsize=8M
[T-Mobile, Samsung Galaxy SIII] G1_enthusiast:
this thread is not for begininer...OP put that in bold..underline...72point font in front...i see people asking the simplest question, if you dont know how to boot into recovery/flash a rom than you shouldnt be doing this!
[T-Mobile, Samsung Galaxy SIII] Markdental:
Has anyone tried some of these tweaks with success?

Also, OP, please update this:

just correct this wrong

rio.ril.disable.power.collapse=1

for correct

ro.ril.disable.power.collapse=1

and this too

dalvik.vm.startheapsize-8M

for

dalvik.vm.startheapsize=8M

Like ruterjunior said in a earlier post....

Also, have you tried:

debug.sf.nobootanimation=1 It should remove boot animation to start the phone faster. It worked on previous phones, but not sure if it will work on this one...
[T-Mobile, Samsung Galaxy SIII] da-pharoah:
+1.. just had to post it again so that way folks read and the op gets corrected.. those minor typos cause bootloops...
[T-Mobile, Samsung Galaxy SIII] overground:
Edited OP with the above corrections.
[T-Mobile, Samsung Galaxy SIII] fcortes626:
thanks for fixing it. i couldnt find the forum anymore because they seperated it and i just saw the other posts. good looking out. and sorry if i caused boot loops:(
[T-Mobile, Samsung Galaxy SIII] ajatt:
Ahem just for testing I tried these adjustments with the CM10 Preview build and they do not play nice Phone won't boot had to restore backup.
[T-Mobile, Samsung Galaxy SIII] flip3547:
I'm just an observer, and I'll admit I'm a novice, but I will say that I've tried the scrolling tweaks and they seem to work for me. First time I tried, I used ESFile Explorer, wouldn't go past the Samsung Galaxy SIII logo, restrored a nandroid, and then used Solid explorer and it worked fine. Maybe the people having trouble with a non booting phone after modifying build.prop are using a file explorer that isn't saving the file correctly or something. Again, I'm just observing, I think I remember reading somewhere that certain file managers aren't saving the file the right way. Anyway, just my two cents.
[T-Mobile, Samsung Galaxy SIII] horrorwolf:
Correct. As a warning, these build.prop edits DO NOT work well with CM10.

*Edit

Nevermind - sorry, these seem to be working fine. I forgot to change permissions on the edited build.prop after making changes.

These seem to be working well.
[T-Mobile, Samsung Galaxy SIII] mrbmg:
Just have to say, I read through this post..

And it's HILARIOUS!!!!

It was up and down, and all around. Pretty good stuff :)
[T-Mobile, Samsung Galaxy SIII] seanvree:
Anyone tried this stuff with Wicked's ROM?
[T-Mobile, Samsung Galaxy SIII] DroidRC1:
adb shell push...a new ROM
[T-Mobile, Samsung Galaxy SIII] Hamodi:
is this work on xperia S ??

because i edit the build.prop and i end on bootloop
[T-Mobile, Samsung Galaxy SIII] puretone:
You do realize this is the Samsung Galaxy S3 TMo variant thread right?
[T-Mobile, Samsung Galaxy SIII] kizakiyuria:
noobs question

what is this for?:confused:
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Yea I'm currently using

Windowsmgr.max_event _per_sec=300

ro.max.fling_velocity=12000

ro.max.fling_velocity=8000

And I notice improved snappiness in scrolling for sure.. Black jelly
[T-Mobile, Samsung Galaxy SIII] fcortes626:
it is supposed to make the device sleep better when in standby and should improve battery life
[T-Mobile, Samsung Galaxy SIII] webstas:
Eh stupid mobile app
[T-Mobile, Samsung Galaxy SIII] jakeinator21:
After applying

ro.ril.hsxpa=3

ro.ril.gprsclass=12

my data speeds increased by a margin of about 2-3 mbps.
[T-Mobile, Samsung Galaxy SIII] imilleson:
OP = regular OG ! Thanks!

---------- Post added at 09:08 AM ---------- Previous post was at 09:01 AM ----------

Is everything under "add to the end of build.prop " supposed to be added ? Or was it just the one item under that statement ?
[T-Mobile, Samsung Galaxy SIII] fcortes626:
everything. if its already there just change the value. if its not then you add it :good:
[T-Mobile, Samsung Galaxy SIII] imilleson:
That makes a lot of logical sense, my bad for the "doh" question Lol. I use to work with some older programs that relied on an ini file for configurations, and the build.prop has always reminded me of this file :)
[T-Mobile, Samsung Galaxy SIII] klin1344:
This is a must read: http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/

I found it while browsing through the developer's discussion forums. It is a very comprehensive article covering which build.prop tweaks are useless, using the AOSP source as reference. It's worth a read, for sure. :)
[T-Mobile, Samsung Galaxy SIII] RotaryXperiment7:
I tried the bitrate raise mod and didn't work. Still recorded at 17mbits for 1080p
[T-Mobile, Samsung Galaxy SIII] Fyahstarter:
Worked for me, but it blew through my battery.
[T-Mobile, Samsung Galaxy SIII] fcortes626:
yup it happens.
[T-Mobile, Samsung Galaxy SIII] marseillesw:
I went thru my build prop line for line and deleted based on this..even changed my max events per second down to 90 and still running very smooth..thanks for this!

sent from GS3 disguised as a GNote2
[T-Mobile, Samsung Galaxy SIII] marvingumba:
i appreciate your efforts b/c i'm learning this stuff too.

:good:
[T-Mobile, Samsung Galaxy SIII] mani1999:
What exactly do you mean by "add to the end of build.prop"?

Does that mean I may only use one tweak which is categorized as "add to the end of build.prop"?

Thanks in advanced....;)
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Think he's means add at the bottom of the list.. If its a new tweak.. If its already existing you can just change the property of it.. Usually you would put a new tweak under "additional properties" and you could put it as the first line under additional or on the bottom.. Doesn't really matter just make sure its absolutely letter for letter correct, and keep it neat.. Keep the spacing between different tweaks and always make sure you have a backup before editing things just in case a tweak doesn't play nice.. Or just delete that edit and reboot.
[T-Mobile, Samsung Galaxy SIII] mani1999:
AW: [MOD] build.prop tweaks

How can I keep it neat?
[T-Mobile, Samsung Galaxy SIII] jdidtht:
I already answered that.. :) just keep spaces between what's their and what you are adding just so you know/remember what you did.. It will automatically make a backup of the unchanged version but its good practice to keep everything separate and spaced between tweaks.
[T-Mobile, Samsung Galaxy SIII] mani1999:
AW: [MOD] build.prop tweaks

Do I have to put something like this between the tweaks?:

# nameoftweak

And a second question;):

What do the Dalvik VM tweaks do?
[T-Mobile, Samsung Galaxy SIII] chipis:
Works great with tweaks, thanks:D
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Yes. Before the name of tweak you will put #. For example with some random tweaks would be:

#Video Media Encoder Tweak

ro.media.enc.hprof.bid.fps=65

#Maximum Capture Resolution

ro.media.capture.maxres=8m

Thats how I would do it.. And as for dalvik VM basically the maximum amount of heap size(read memory) a single instance of dalvik VM (read applucation ) can obtain.. Short answer its basically puts parameters on how much memory/ram applications can use.. Too high will cause lag and issues and too low the same things. So although I haven't read in this thread what his dalvik tweaks are set at I'm sure they are pretty standard. Just look at your current ROMs build props dalvik VM I'm sure your ROMs developer has already implemented a dalvik tweak or two..

Edit those are some optimizations and lock prof I believe acts as a cap so as to prevent too much ram from being taken while multitasking
[T-Mobile, Samsung Galaxy SIII] khaled_7:
Do these codes work on all android platforms on all phones ?!

or just S3 with a specific android version ??
[T-Mobile, Samsung Galaxy SIII] fishman0919:
Some of those codes/tweaks/values are meant for the GS3 but could work on other phones. Others are more universal and could work on most phones.
[T-Mobile, Samsung Galaxy SIII] mikeman45:
So these are not carrier specific? I'm on verizon s3 so can use any or all of these without issue.
[T-Mobile, Samsung Galaxy SIII] scream4cheese:
I'm using it on my Nexus 4 and they seem to be okay. I'm not sure if they work or not. It could just be a placebo. Lol
[T-Mobile, Samsung Galaxy SIII] skytechja:
just a quck question

all these have been used before without bricking the phone right?

i wanan do a few of em like for battery life, video recoring quality n so forth.. not any deep stuff cause if i brick this phone bwoy im ()*&) out of luck
[T-Mobile, Samsung Galaxy SIII] scream4cheese:
Yep
[T-Mobile, Samsung Galaxy SIII] Dragon122333:
what causes the hard brick ? :/
[T-Mobile, Samsung Galaxy SIII] fcortes626:
Hard brick was unrelated to the build.prop. it was cause by flashing the wrong rom.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Wwell, you have to be careful though. Certain build.prop edits can indirectly lead to a brick.

For example, before we got Google Wallet, people could edit the file to trick Wallet into thinking it was on a different device. Well, it would also trick other apps.

There were a few people wo made this edit, and then tried to flash firmware in Mobile Odin. Well, since MO thought it was on a different device it did not use the correct flash kernel and led to a bricked device.

So it wasn't the edit itself that caused it, but it created a scenario where some apps would function differently, and in this case, a rather powerful one.

Just thought I'd throw that out as a reminder.

In general though, the vast majority of edits are perfectly safe to do.
[T-Mobile, Samsung Galaxy SIII] Nakulkhanna:
hey guys i am noob in tweaking build.prop file, i m just learning how to make own custom rom...

so if any1 could plz help and tell me that do i need to just add this scripts shown on the 1st post to the build.prop or do i need to replace them with old ones? i mean whats the correct way to do it if i wanna i add these scripts to my build.prop?
[T-Mobile, Samsung Galaxy SIII] fcortes626:
yup thats why i didnt put those in the post. i tried all of them before i made the thread.;)
[T-Mobile, Samsung Galaxy SIII] fcortes626:
add them one by one and if the line already exists then just change the value. best way to do it is with notepad++. you can ctrl+F and just search each line one by one to see if it already exists.
[T-Mobile, Samsung Galaxy SIII] chrisj22:
Awesome
[T-Mobile, Samsung Galaxy SIII] nappent:
For higher quality audio i use the following:

lpa.decode=false

af.resampler.quality=34

persist.af.resampler.quality=255

Just to add my $0.02
[T-Mobile, Samsung Galaxy SIII] metalfan78:
Does the correct way to add a hack look like this?

# example name

Example.hack=value

I'm confused about needing a name or a space after #. Thanks
[T-Mobile, Samsung Galaxy SIII] cr4ck3r4lif3:
# just represents a comment line. You don't need it but can add anything after it, space or not
[T-Mobile, Samsung Galaxy SIII] metalfan78:
Gotcha, thank you
[T-Mobile, Samsung Galaxy SIII] nxoxe:
My build.prop

Have a nice day...
[T-Mobile, Samsung Galaxy SIII] metalfan78:
I'm not entirely convinced that any of these work. I'm not saying I'm right but I can't really tell a difference and I've read a few articles debunking build.prop tweaks. It makes me wonder if there is a placebo affect on some of these.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Personally I do believe they work. Values do get changed when you mske the change in the build.prop. ril values can make a huge difference.

But.......

YMMV
[T-Mobile, Samsung Galaxy SIII] Woody:
I agree with Doc here. I only change my ril and wifi_supplicant values when I flash a new rom (see below). In fact I have a mock build.prop that all I have to do is open in Root Explorer and copy them (5 lines total) and then open /system/build.prop and find where they go, paste and remove the originals.

I have been doing build.prop edits for quite a long time. They work great on some lower-end devices, however since ICS and the explosion of AOSP/Twiz/Sense (Blur is gone) and the optimization of databases and apps, there is really no need for most of these anymore. Rom Control (and all its derivatives) has most of these incorporated as tweaks, aside from the obscure ones out there.

I would like to caution though. These build.prop edits from the OP are for Motorola and HTC devices:

ro.[COLOR="red"][B]mot[/B][/COLOR].eri.losalert.delay=1000 (might break tethering)
ro.ril.[COLOR="red"][B]htc[/B][/COLOR]maskw1.bitmask=4294967295
ro.ril.[COLOR="red"][B]htc[/B][/COLOR]maskw1=14449

************

These are my ril and wifi_supplicant tweaks in case anyone wants to use them. I am in Cincinnati, so these might not be the best for your or your data coverage. YMMV

ro.ril.hsxpa=3
ro.ril.gprsclass=12
ro.ril.hsupa=6
ro.ril.hsdpa=14
wifi.supplicant_scan_interval=420
[T-Mobile, Samsung Galaxy SIII] metalfan78:
Those are the same type of edits I have made on my galaxy s3. I can see how those would work. I'm going to keep testing them. Thank you for the input.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you want some more info on the ril tweaks, you should read the section on them in the modem thread. Might help a little.
[T-Mobile, Samsung Galaxy SIII] metalfan78:
Thanks, can you give me the link to that thread?
[T-Mobile, Samsung Galaxy SIII] Woody:
Go out of this thread and look up ^^^ ;):p It is stickied.

His build.prop ril settings are in post #3

By far one of the best reference threads we have in this section, IMO of course.