Develop Bugs

How change my phone identity

I have installed incredible sensatation on my Dinc2. I'm using the phone on tmobiles network. The only problem is when I recieve picture messages my photos shrink to thumbnail size. After talking to tmobile, the tech said I would have to have the dev of my ROM tell me how to change the identity of my phone to a model on tmobiles systems.
Sent from my Incredible 2 Sensation using XDA App

bamajoker said:
I have installed incredible sensatation on my Dinc2. I'm using the phone on tmobiles network. The only problem is when I recieve picture messages my photos shrink to thumbnail size. After talking to tmobile, the tech said I would have to have the dev of my ROM tell me how to change the identity of my phone to a model on tmobiles systems.
Sent from my Incredible 2 Sensation using XDA App
Click to expand...
Click to collapse
Masking the phone involves an edit to the build.prop file. /system is the location.
ro.product.model=Incredible 2
ro.product.manufacturer=HTC
Be sure to reboot after you change these properties.

artvandelay440 said:
Masking the phone involves an edit to the build.prop file. /system is the location.
ro.product.model=Incredible 2
ro.product.manufacturer=HTC
Be sure to reboot after you change these properties.
Click to expand...
Click to collapse
That won't work. For example using virtuous 2.37. Under settings/about phone/ phone identity it says HTC sensation. But no where in build.prop can I find that to change. Any ideas?
Sent from my ADR6350 using XDA App

iceman99393 said:
That won't work. For example using virtuous 2.37. Under settings/about phone/ phone identity it says HTC sensation. But no where in build.prop can I find that to change. Any ideas?
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
Here it is in the build.prop. Lines #18 and #25
Virtuous has the agent listed as the Sensation because that's the phone it was based from.

It's not working, do I need to change ro.aa.modelid also ?
# autogenerated by buildinfo.sh
ro.aa.customizationid=191108
ro.aa.project=Vivo_W_Gingerbread_S
ro.aa.romver=2.18.605.4
ro.aa.maincid=VZW__001
ro.aa.cidlist=VZW__001
ro.aa.rid=47
ro.aa.modelid=PG3210000
ro.aa.skulist=605
ro.aa.taskid=200325
ro.aa.mainsku=605
ro.com.google.clientidbase=android-verizon
ro.aa.customizationid=191108
ro.aa.project=Vivo_W_Gingerbread_S
ro.aa.romver=2.18.605.4
ro.aa.maincid=VZW__001
ro.aa.cidlist=VZW__001
ro.aa.rid=47
ro.aa.modelid=PG3210000
ro.aa.skulist=605
ro.aa.taskid=200325
ro.aa.mainsku=605
ro.com.google.clientidbase=android-verizon
ro.build.id=GRI40
ro.build.display.id=GRI40
ro.build.version.incremental=81006
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=六 6月 25 15:24:05 CST 2011
ro.build.date.utc=1308986645
ro.build.type=user
ro.build.user=
ro.build.host=AA125
ro.build.tags=release-keys
ro.product.model=Sensation
ro.product.brand=htc_wwe
ro.product.name=htc_vivow
ro.product.device=vivow
ro.product.board=vivow
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
using XDA App

bamajoker said:
It's not working, do I need to change ro.aa.modelid also ?
# autogenerated by buildinfo.sh
ro.aa.customizationid=191108
ro.aa.project=Vivo_W_Gingerbread_S
ro.aa.romver=2.18.605.4
ro.aa.maincid=VZW__001
ro.aa.cidlist=VZW__001
ro.aa.rid=47
ro.aa.modelid=PG3210000
ro.aa.skulist=605
ro.aa.taskid=200325
ro.aa.mainsku=605
ro.com.google.clientidbase=android-verizon
ro.aa.customizationid=191108
ro.aa.project=Vivo_W_Gingerbread_S
ro.aa.romver=2.18.605.4
ro.aa.maincid=VZW__001
ro.aa.cidlist=VZW__001
ro.aa.rid=47
ro.aa.modelid=PG3210000
ro.aa.skulist=605
ro.aa.taskid=200325
ro.aa.mainsku=605
ro.com.google.clientidbase=android-verizon
ro.build.id=GRI40
ro.build.display.id=GRI40
ro.build.version.incremental=81006
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=六 6月 25 15:24:05 CST 2011
ro.build.date.utc=1308986645
ro.build.type=user
ro.build.user=
ro.build.host=AA125
ro.build.tags=release-keys
ro.product.model=Sensation
ro.product.brand=htc_wwe
ro.product.name=htc_vivow
ro.product.device=vivow
ro.product.board=vivow
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
using XDA App
Click to expand...
Click to collapse
take a stock sensation build.prop and compare it to yours. in yours replace wherever it says vivow with whatever the equivelant is in the sensation build.prop except for the ro.build.fingerprint. that's usually the line that the market uses to identify the phone.
Sent from my Incredible 2 using XDA App

Any idea where to find one
using XDA App

+1 for times' idea. you could find a stock-based app in the sensation forums, download it to the computer, and look under /system within the rom.

Now what model sensation.? Tmobile has a sensation 4g out would I use that one?
Sent from my Sensation 4G using XDA App

Tmobile is now saying my user agent field may have to be changed , any idea wthvthis is
Sent from my Sensation 4G using XDA App

bamajoker said:
Tmobile is now saying my user agent field may have to be changed , any idea wthvthis is
Sent from my Sensation 4G using XDA App
Click to expand...
Click to collapse
Since your signature says "sent from my sensation 4g" i think you've successfully masked your model. Not sure what t-mobile is wanting you to do...

HTC sends a uaprof string with mms with phoneid
Sent from my Sensation 4G using XDA App

bamajoker said:
HTC sends a uaprof string with mms with phoneid
Sent from my Sensation 4G using XDA App
Click to expand...
Click to collapse
yeah he's gonna need to change the useragent in the Mms.apk
that would require decompiling the apk, editing mms_config.XML and then rebuilding the apk.
I should be home shortly. ill see what I can do.
if you want you can try pulling Mms.apk from a sensation rom and pushing it to /system/app see if that helps.
Sent from my Incredible 2 using XDA App

I found this in default.xml in /system/customize
<function name="ua_profile">
<set name="single">
<item name="value">http://uaprof.vtext.com/pcd/adr6350/adr6350.xml</item>
</set>
</function>
<!-- Enable gif animation -->
<function name="enable_gif_anim">
<set name="single" />
</function>
<!-- Mobile_view -->
<function name="mobile_view">
<set name="single" />
</function>
<!-- Default text encoding -->
<function name="default_text_encoding">
<set name="single" />
</function>
<!-- Location_Setting -->
<function name="geolocation">
<set name="single" />
</function>
<!-- Open pages in overview -->
<function name="overview">
<set name="single" />
</function>
<!-- Max tabs count -->
<function name="max_tabs">
<set name="single" />
</function>
<!-- full screen mode (show/hide status bar) -->
<function name="always_show_statusbar">
<set name="single" />
</function>
<!-- Bookmark View Setting -->
<function name="bookmark_view_mode">
<set name="single" />
</function>
<!-- Most Visit Bookmark View Setting -->
<function name="mostvisited_view_mode">
<set name="single" />
</function>
<!-- Default Search Engine -->
<function name="search_engine">
<set name="single" />
</function>
<!-- download_dialog -->
<function name="download">
<set name="single" />
</function>
</module>
<!-- MMS UA string -->
<module name="MMS">
<function name="ua_string">
<set name="single">
<item name="value">pcdadr6350</item>
</set>
</function>
</module>
<!-- J2ME UA string -->
<module name="J2ME">
<function name="ua_string">
<set name="single" />
</function>
</module>
</category>
</customization_form>
Sent from my Sensation 4G using XDA App

Does a normal sensation work on tmoible.? I know the sensation 4g does
Sent from my Sensation 4G using XDA App

Changed everything in default.xml and build.prop to match a sensation and its still not working... Any ideas.?
Sent from my HTC Pyramid using XDA App

bamajoker said:
Changed everything in default.xml and build.prop to match a sensation and its still not working... Any ideas.?
Sent from my HTC Pyramid using XDA App
Click to expand...
Click to collapse
grab the mms.apk from a sensation rom and see if that helps. if it doesnt. I could try hacking up mms_config.xml in a stock Inc2 mms.apk later
Sent from my Incredible 2 using XDA App

Grabbed to mmsmapk from a sensation that did not wotk. Also opened the mms.apk and I didn't don't see the xml u mentioned
Sent from my HTC Pyramid using XDA App

[Q] How to make a new mod?

please i need to learn how to make a mod...

More info please. What kind of mod. What rom.

umm yea what kind of mod are you talking about

like monkee os
Sent from my PC36100 using xda app-developers app

TemplaPR said:
like monkee os
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
You would know stuff about making a zip with binaries and the mod in the directory for theming go for framework-res.apk to theme some parts of the Rom. for battery saving set your CPU to 3xx and 844 deadline that's the best I got from that Rom.theming apps is like theming framework but the app and you should you PhotoShop or Gimp to theme pics and use UOT kitchen. For mods mods you need to know the right codes like for example if I wanted to make a photos look crisp and clean id use this in the build.prop file
"
Ro.media.dec.jpeg.memcap=8000000
Ro.media.enc.hprof.vid.bps=8000000
Ro.media.enc.jpeg.quality=100
Click to expand...
Click to collapse
"
And for init.d mods id do this
Goto (romname)/etc/init.d/01sysctl
Put this code for faster rom speed
#!/system/bin/sh
sysctl -p
net.ipv4.tcp_ecn=0
net.ipv4.route.flush = 1
net.ipv4.tcp_rfc1337 = 1
net.ipv4.ip_no_pmtu_disc = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_rmem = 4096 39000 187000
net.ipv4.tcp_wmem = 4096 39000 187000
net.ipv4.tcp_mem = 187000 187000 187000
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
Click to expand...
Click to collapse
Save and exit.
These are examples that will work and you need to know the right codes/strings to put in files or know how.to use PhotoShop or Gimp properly to theme.
This is just some of my basic knowledge
Sent from my PC36100 using xda premium

Papasmurph is a great mod. Why do we need to build a new one?
Sent from my SPH-L710 using xda app-developers app

Device incompatible for like every app there is...

I can't download words with friends, facebook, etc...says my device is incompatible.
I'ts VZW GN rooted unlocked. Liquid Smooth ICS 1.4
4.0.4 ICS
Thoughts? Awfully annoying.

Did you change DPI?
Sent from my Galaxy Nexus using xda premium

cam1john said:
I can't download words with friends, facebook, etc...says my device is incompatible.
I'ts VZW GN rooted unlocked. Liquid Smooth ICS 1.4
4.0.4 ICS
Thoughts? Awfully annoying.
Click to expand...
Click to collapse
the issue is that your build.prop file probably isnt identifying your phone properly, or you messed with your screen resolution. post your build.prop file here and we'll take a look at it. its in /system/build.prop/

simms22 said:
the issue is that your build.prop file probably isnt identifying your phone properly, or you messed with your screen resolution. post your build.prop file here and we'll take a look at it. its in /system/build.prop/
Click to expand...
Click to collapse
# begin build properties # autogenerated by buildinfo.sh ro.build.id=IMM76K ro.build.display.id=Liquid ICS v1.4 ro.build.version.incremental=336647 ro.build.version.sdk=15 ro.build.version.codename=AOSP ro.build.version.release=4.0.4 ro.build.date=Fri May 18 18:54:54 EDT 2012 ro.build.date.utc=1337381694 ro.build.type=user ro.build.user=liquid ro.build.host=ubuntu ro.build.tags=release-keys ro.product.model=Galaxy Nexus ro.product.brand=google ro.product.name=mysid ro.product.device=toro ro.product.board=tuna ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=Samsung ro.product.locale.language=en ro.product.locale.region=US ro.wifi.channels= ro.board.platform=omap4 # ro.build.product is obsolete; use ro.product.device ro.build.product=toro # Do not try to parse ro.build.description or .fingerprint ro.build.description=mysid-user 4.0.4 IMM76K 336647 release-keys ro.build.fingerprint=google/mysid/toro:4.0.4/IMM76K/336647:user/release-keys ro.build.characteristics=nosdcard # end build properties # This defines the max event window manager can # handle in 1 s. We may adjust this # for performance # reason later windowsmgr.max_events_per_sec=275 # end build properties # # system.prop for toro #
rild.libpath=/vendor/lib/libsec-ril_lte.so rild.libargs=-d /dev/ttys0 telephony.lteOnCdmaDevice=1
# Turn on IMS by default persist.radio.imsallowmtsms=1 persist.radio.imsregrequired=1
# Dalvik heapsize dalvik.vm.heapsize=256m dalvik.vm.heapstartsize=16m dalvik.vm.heapgrowthlimit=128m
# # ADDITIONAL_BUILD_PROPERTIES # keyguard.no_require_sim=true ro.rommanager.developerid=liquid ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html ro.com.google.clientidbase=android-google ro.com.android.wifi-watchlist=GoogleGuest ro.com.android.dateformat=MM-dd-yyyy ro.setupwizard.enterprise_mode=1 ro.com.android.dataroaming=false ro.media.enc.jpeg.quality=100 ro.kernel.android.checkjni=0 persist.sys.camera-sound=1 ro.config.ringtone=Hydra.ogg ro.config.notification_sound=Proxima.o gg ro.config.alarm_alert=Cesium.ogg ro.config.vc_call_vol_steps=7 ro.com.google.locationfeatures=1 ro.setupwizard.mode=OPTIONAL ro.telephony.call_ring.delay=500 ro.cdma.home.operator.numeric=310004 ro.cdma.home.operator.alpha=Verizon ro.telephony.call_ring.multiple=false ro.cdma.homesystem=64,65,76,77,78,79,8 0,81,82,83 ro.cdma.data_retry_config=default_rand omization=2000,0,0,120000,180000,54000 0,960000 ro.gsm.2nd_data_retry_config=max_retri es=infinite,default_randomization=2000 ,0,0,80000,125000,485000,905000 ro.cdma.otaspnumschema=SELC,1,80,99 wifi.interface=wlan0 wifi.supplicant_scan_interval=180 ro.opengles.version=131072 ro.sf.lcd_density=330 ro.modversion=liquid.toro.051812.18543 2 dalvik.vm.lockprof.threshold=750 dalvik.vm.dexopt-flags=m=y net.bt.name=Android ro.HOME_APP_ADJ=1 dalvik.vm.stack-trace-file=/data/anr/traces.txt

Thoughts? Thanks guys
Sent from my Galaxy Nexus using Tapatalk 2

LCD density is 330. What is it supposed to be?
Sent from my Galaxy Nexus using xda premium

Idk....
Sent from my Galaxy Nexus using Tapatalk 2

phio said:
LCD density is 330. What is it supposed to be?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its supposed to be 320.

phio said:
LCD density is 330. What is it supposed to be?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
320 I believe.

the only other flag i see is ro.build.display.id=Liquid ICS v1.4 but should be ro.build.display.id=IMM76K. i think changing the display to 320 instead of 330 should help. if not change the display id.

Good call guys. Switched to 320 hand rebooted. Worked!
Sent from my Galaxy Nexus using Tapatalk 2

[Mod] My Build.prop I use in most ROMs

I know there was a post just like with what I'm doing...but here's something for you to use in your own ROMs.
Code:
#Performance Enhancement
dalvik.vm.heapgrowthlimit=256m
debug.performance.tuning=1
windowsmgr.max_events_per_sec=300
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
debug.sf.hw=1
video.accelerate.hw=1
profiler.force_disable_err_rpt=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.execution-mode=init:jit
ro.kernel.android.checkjni=0
#Battery Enhancement
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=500
ro.mot.eri.losalert.delay=1000
persist.sys.purgeable_assets=1
# Signal Enhancement
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=7
media.stagefright.enable-meta=true
media.stagefright.enable-record=false
ro.ril.hep=1
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.tcp.buffersize.default=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.umts=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.hspa=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,87380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
# Video & Picture Enhancement
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Sound & Calls Enhancement
ro.telephony.call_ring.delay=0
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
af.resampler.quality=255
persist.af.resampler.quality=255
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
#AC!D Audio Volume Hack
-----------------------------
speaker volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.speaker.voice.0=20
audio.speaker.voice.1=21
audio.speaker.voice.2=24
audio.speaker.voice.3=26
audio.speaker.voice.4=28
audio.speaker.voice.5=31
-----------------------------
earpiece volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.earpiece.voice.0=20
audio.earpiece.voice.1=21
audio.earpiece.voice.2=24
audio.earpiece.voice.3=26
audio.earpiece.voice.4=28
audio.earpiece.voice.5=31
-----------------------------------
headset volume is from 9 to 14
this corresponds to -34dB to -19dB
----------------------------------
audio.headset.voice.0=16
audio.headset.voice.1=19
audio.headset.voice.2=22
audio.headset.voice.3=25
audio.headset.voice.4=28
audio.headset.voice.5=31
#Sony BRAVIA Engine
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
Note ** : Bravia Engine build.prop and AC!D build.prop edits still need required files. This is just to enable the settings to work with the files.

Did you get a gs3?
Sent from my SGH-T999 using xda app-developers app

Thanks for your contribution .

seshaz said:
Did you get a gs3?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Yes.

TheLastSidekick said:
Yes.
Click to expand...
Click to collapse
Nice
Sent from my SGH-T999 using xda app-developers app

exactly what files are required for the bravia engine?? I've been wanting to use that for awhile now and can't fine much info about it.

SimeonAS89 said:
exactly what files are required for the bravia engine?? I've been wanting to use that for awhile now and can't fine much info about it.
Click to expand...
Click to collapse
Your signature says you have a GS3 so check out this Bravia Engine thread.

Where can I find the volume hack for Ac!d? Version 4.0? I'm on V5 and I'm not sure if it'll work, any takers?

If I edit the build prop in my current Rom do I just reboot for the modified .xml to be loaded? ...or do I need to modify the file in the Rom zip and re-flash?

Do you just add these to the end of the build prop?
Sent from my SGH-T999 using Tapatalk 2

OhhCoreey said:
Do you just add these to the end of the build prop?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I did then deleted conflicting and duplicate entries. Still not sure if just a reboot reloads the file though. My data seems a bit faster. I'm on the latest miui port.
Sent from my SGH-T999 using xda app-developers app

I know this was posted somewhere else in XDA, but it's worth a read, much of this stuff seems to be placebo:
http://www.jeffmixon.com/series/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide/

[Mod] My Build.prop I use in most ROMs

I posted this after I lost my Galaxy S2 and was on my Galaxy S3. Here's an update finally, sorry I forgot where this thread was.
Code:
#Performance Enhancement
dalvik.vm.heapgrowthlimit=256m
debug.performance.tuning=1
windowsmgr.max_events_per_sec=90 (this was proven right, only set it to 90 for best effects)
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
debug.sf.hw=1
video.accelerate.hw=1
profiler.force_disable_err_rpt=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.execution-mode=init:jit
ro.kernel.android.checkjni=0
#Battery Enhancement
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=500
ro.mot.eri.losalert.delay=1000
persist.sys.purgeable_assets=1
# Signal Enhancement
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=7
media.stagefright.enable-meta=true
media.stagefright.enable-record=false
ro.ril.hep=1
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.tcp.buffersize.default=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.umts=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.hspa=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,87380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
# Video & Picture Enhancement
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Sound & Calls Enhancement
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=25
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
af.resampler.quality=255
persist.af.resampler.quality=255
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
#AC!D Audio Volume Hack
-----------------------------
speaker volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.speaker.voice.0=20
audio.speaker.voice.1=21
audio.speaker.voice.2=24
audio.speaker.voice.3=26
audio.speaker.voice.4=28
audio.speaker.voice.5=31
-----------------------------
earpiece volume is from 20 to 31
this corresponds to -2dB to +8dB
-----------------------------
audio.earpiece.voice.0=20
audio.earpiece.voice.1=21
audio.earpiece.voice.2=24
audio.earpiece.voice.3=26
audio.earpiece.voice.4=28
audio.earpiece.voice.5=31
-----------------------------------
headset volume is from 9 to 14
this corresponds to -34dB to -19dB
----------------------------------
audio.headset.voice.0=16
audio.headset.voice.1=19
audio.headset.voice.2=22
audio.headset.voice.3=25
audio.headset.voice.4=28
audio.headset.voice.5=31
#Sony BRAVIA Engine
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1

The Bravia Engine tweak wouldn't work unless the engine is installed, correct?

How do i make this into a zip file? Or can i
Sent from my SGH-T989 using xda premium

Very good job, thank you.

vassosman said:
The Bravia Engine tweak wouldn't work unless the engine is installed, correct?
Click to expand...
Click to collapse
Correct.
thakrew317 said:
How do i make this into a zip file? Or can i
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
You could, I just don't know how to make flashables.
Warren87 said:
Very good job, thank you.
Click to expand...
Click to collapse
No, thank you!

Flashable zips are not that difficult especially if you just use an already established zip file like the gapps zip and manipulate from there..
I usually make my tweaks and place it in a local.prop file that is placed in /data folder on your root. Unfortunately this method does not work with 4.2 for future notice
here is an attachment of your fixes in a local.prop setup... Feel free to take a look at it to make sure all is well. I flashed it on my phone as a local.prop file to make sure it flashes right and it does. Download and manipulate at your leisure people.
Just an an fyi - I have done nothing more than place OP's tweaks in a prop file and then inserted it into a flashable zip file....

thakrew317 said:
How do i make this into a zip file? Or can i
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
the above was for you

I tried making one but failed not very educated when doing things like that thank you!!!!
Sent from my SAMSUNG-SGH-T989 using xda premium

Do these mods really make a noticeable difference????

subnoize soulja said:
Do these mods really make a noticeable difference????
Click to expand...
Click to collapse
Try it and let us know I know the mods I used did but too some it may seem like it has not... Only one way too find out...
---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------
thakrew317 said:
I tried making one but failed not very educated when doing things like that thank you!!!!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Its actually very easy and if you need help or wanna learn just let me know... PM me
I manipulate more than I create its easier that way....

playya said:
Flashable zips are not that difficult especially if you just use an already established zip file like the gapps zip and manipulate from there..
I usually make my tweaks and place it in a local.prop file that is placed in /data folder on your root. Unfortunately this method does not work with 4.2 for future notice
here is an attachment of your fixes in a local.prop setup... Feel free to take a look at it to make sure all is well. I flashed it on my phone as a local.prop file to make sure it flashes right and it does. Download and manipulate at your leisure people.
Just an an fyi - I have done nothing more than place OP's tweaks in a prop file and then inserted it into a flashable zip file....
Click to expand...
Click to collapse
Hey playya, I have one question for you. The zip puts the tweaks to default.prop. Shouldnt't they be in the build.prop? If not, what does the default.prop do? I've seen a lot of ROM's that have a default.prop in data and always wondered what it did.
Sent from my Nexus 7 using xda app-developers app

playya said:
Flashable zips are not that difficult especially if you just use an already established zip file like the gapps zip and manipulate from there..
I usually make my tweaks and place it in a local.prop file that is placed in /data folder on your root. Unfortunately this method does not work with 4.2 for future notice
here is an attachment of your fixes in a local.prop setup... Feel free to take a look at it to make sure all is well. I flashed it on my phone as a local.prop file to make sure it flashes right and it does. Download and manipulate at your leisure people.
Just an an fyi - I have done nothing more than place OP's tweaks in a prop file and then inserted it into a flashable zip file....
Click to expand...
Click to collapse
Thank you for making it a zip!! I would love to learn
Sent from my SGH-T989 using xda premium

Interesting read on some build prop tweaks being busted:
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
Apparently Google have said a 'windowsmgr.max_events_per_sec' value above 90 doesn't add anything to performance and can even be detrimental to it.
After messing around with it I noticed 90 makes things more snappier than 300+. At least for me on all of the 4.0.3 ROMs.
Worth noting.
Sent from my SGH-T989 using Tapatalk 2

Reading over the individual prop edits, I'm noticing that my phone does not have all of the props to edit. Without making a paperweight, should I ignore the ones not present. Only asking since the ROMs that the OP has made and I've since flashed all of them, have been a lot quicker then the dated PA I'm running now and ID like to apply them but there are several missing so I figured ID ask here. Thanks with any knowledge you can toss my way
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Tmogalaxys2 said:
Hey playya, I have one question for you. The zip puts the tweaks to default.prop. Shouldnt't they be in the build.prop? If not, what does the default.prop do? I've seen a lot of ROM's that have a default.prop in data and always wondered what it did.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
sorry guys for not getting back to you sooner but i coach kids and adults so sometimes I miss stuff. Now what I did was put it in as a local.prop and this actually supersedes your build.prop and it can be used from one rom to another without having to go in and change each build.prop.
also if you update your rom and you do not do a clean install your tweaks should stick without a problem since it wont be overwritten on a flash.
I believe if I am not mistaken that the default.prop is kernel related and if you view it you will see info related to such like usb connection and adb root access
---------- Post added at 09:07 AM ---------- Previous post was at 09:01 AM ----------
tongueman87 said:
Thank you for making it a zip!! I would love to learn
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
No prob I use notepad ++ and total commander to do my manipulations... Send me a pm and we can mess around with stuff. Its really a lot of text and not as difficult as you may think.

playya said:
sorry guys for not getting back to you sooner but i coach kids and adults so sometimes I miss stuff. Now what I did was put it in as a local.prop and this actually supersedes your build.prop and it can be used from one rom to another without having to go in and change each build.prop.
also if you update your rom and you do not do a clean install your tweaks should stick without a problem since it wont be overwritten on a flash.
I believe if I am not mistaken that the default.prop is kernel related and if you view it you will see info related to such like usb connection and adb root access
---------- Post added at 09:07 AM ---------- Previous post was at 09:01 AM ----------
No prob I use notepad ++ and total commander to do my manipulations... Send me a pm and we can mess around with stuff. Its really a lot of text and not as difficult as you may think.
Click to expand...
Click to collapse
Thanks for the info man!
Sent from my Nexus 7 using xda app-developers app

Bumping with update, have more knowledge of the tweaks. And yes, I still do frequent these forums lol, and you guys did get 4.1.2 before GS3 did, but we just got it 3 days ago. Just can't test anything for the GS2. But these are universal, enjoy!

DigitaL BlisS said:
Interesting read on some build prop tweaks being busted:
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
Apparently Google have said a 'windowsmgr.max_events_per_sec' value above 90 doesn't add anything to performance and can even be detrimental to it.
After messing around with it I noticed 90 makes things more snappier than 300+. At least for me on all of the 4.0.3 ROMs.
Worth noting.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Yea I was reading this as well. There are actually two pages in his report can find both here:
http://www.jeffmixon.com/series/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide/

TheLastSidekick said:
Bumping with update, have more knowledge of the tweaks. And yes, I still do frequent these forums lol, and you guys did get 4.1.2 before GS3 did, but we just got it 3 days ago. Just can't test anything for the GS2. But these are universal, enjoy!
Click to expand...
Click to collapse
Welcome back old friend =/]