[Q] Build.prop edit for headphones? P880 - LG Optimus 4X HD

do you guys think i can edit the build.prop file in the system folder to change the highest amount of volume to a lower value?
that way my headphones are not as loud.
# -----------------------------
# 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
persist.tegra.nvmmlite = 1

You can just edit it from the hidden menu
Made possible by my sexy LG Optimus 4X HD (P880)

Nothing for audio in the hidden menu
theofficialpimp said:
You can just edit it from the hidden menu
Made possible by my sexy LG Optimus 4X HD (P880)
Click to expand...
Click to collapse
I didn't find anything related to audio there some stuff but not quite if you can point me in the right direction please?
also i'm using 3845#*880# to get into it is there another one?

Related

HD Slow Motion - Experimenting

I took a stab recently at modifying the build.prop in order to capture slow motion video in 1280x720 (and also in 720x480).
The slow video mode by default caputres in QVGA (320x240). I started by changing every instance of 320x240 to 1280x720. No avail. I tried it again at 720x480 - also with no result.
I also tried changing the instances of 30 fps to 60 fps. Nothing worked. I gave up with the plan to approach it again later. Now it is later.
My head must be more clear now because I see that most of the changes I was making were in lines that describe encoding, not capturing. I see now that there is no mention of 24fps in the build.prop, so the regular HD recording must be getting its capture instructions from elsewhere.
The only mention of capture fps is fast mode and slow mode which are 4 fps, and 60 fps, respectively.
As a side note, I also changed the HD video encoding bitrate from bps=8000000 to bps=12000000, and even greater, but I saw no noticeable difference in quality.
I know that capturing slow motion at 60 fps in 1280x720 is likely more than the phone can handle. So - I'm not looking for that response. I am just curious to see what limit I can push it to. Maybe it can handle 60 fps at 720x480. I won't know until I can figure out how to try it.
If it isn't evident by the direction I already tried, I am no expert here. I think I know enough to prevent any serious screw ups of my phone. I am looking for a little guidance here on where to look next for changing the capture settings. Any thoughts?
The build.prop is shown below. NOTE: This has been edited to change any URLs to xxx, due to restrictions of the forum.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=VZW
ro.build.display.id=VZW
ro.build.version.incremental=1.13.604
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Thu Jul 1 18:30:48 CDT 2010
ro.build.date.utc=1278027048
ro.build.type=user
ro.build.user=w30471
ro.build.host=il93lnxdroid08
ro.build.tags=test-keys
ro.product.model=DROIDX
ro.product.model.internal=MB810
ro.product.brand=verizon
ro.product.name=shadow_vzw
ro.product.device=cdma_shadow
ro.product.board=shadow
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=shadow_vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_shadow-user 2.1-update1 VZW 1.13.604 ota-rel-keys,release-keys
ro.build.fingerprint=verizon/shadow_vzw/cdma_shadow/shadow:2.1-update1/VZW/13604:user/ota-rel-keys,release-keys
# end build properties
#
# system.prop for CDMA Shadow
#
# rild.libpath=/system/lib/libril-moto-umts-1.so
rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.default_usb_mode=0
# BEGIN Motorola, a18772, 05/19/2010, IKSHADOW-5584
# Add 411 to DAN List for VZW.
ro.mot.ril.danlist=611,*611,#611,411
# END IKSHADOW-5584
persist.ril.ecclist=911,*911,#911
persist.ril.modem.mode =1
# 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=55
# This defines the min duration between two pointer event
ro.min_pointer_dur=10
# USB modes allowed for UI and switching
ro.ngp_available=1
ro.modem_available=0
# Default network type.
# 4 => CDMA / EVDO.
ro.telephony.default_network=4
ro.com.google.clientid=android-motorola
ro.url.legal=xxx
ro.url.legal.android_privacy=xxx
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
# wlan interface
wifi.interface = tiwlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=30m
# The URL for safety information
ro.url.safetylegal=xxx
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=
# Enable HAC to also display Call Setting Menu Option.
ro.mot.hw.HAC=1
# Motorola, a19622, 12/28/2009, IKSHADOW-204 / Location Settings for android
# Property to set enabling state of the location privacy setting feature.
# Motorola, a19622, 03/16/2010, IKSHADOW-2141 / Disable feature 33067
#ro.mot.settings.locprivacy=1
# ERI feature
# 0 OFF
# 1 ON
ro.mot.eri=1
# Motorola, a22976, 13/5/2010, IKSHADOW-5203
# Delay for Loss Of Service alert
ro.mot.eri.losalert.delay=2000
# If time from last RoamInd change to SID change less than below, not play alert
ro.mot.eri.sidalert.delay=1000
# END IKSHADOW-5203
# Motorol,a6889c,02/Feb/2010,IKSHADOW-619
# Proximity Sensor feature
# 0 disable
# 1 enable
persist.mot.proximity.touch=1
# End IKSHADOW-619
# BEGIN Motorola, a22976, 25-Feb-2010, IKSHADOW-702, FID 31841
# VZW Requirement Specifications: NETWORK BASED PLUS CODE DIALING
# 0 disable
# 1 enable
ro.cdma.nbpcd=1
# END IKSHADOW-702
# BEGIN Motorola, a22976, 12-Mar-2010, IKSHADOW-1784, Power Up Tone
# Motorola, a22976, 12-Apr-2010, IKSHADOW-3298, Remove temporary power up tone
# BEGIN Motorola, wbdq68, 21-May-2010, IKSHADOW-3372, Turn ON Power Up Tone
# Motorola, a22976, 26-May-2010, IKSHADOW-6164, Remove power up tone to keep the same as Droid
#persist.mot.powerup.tone=/system/media/bootup.ogg
# END IKSHADOW-3372
# END IKSHADOW-1784
# BEGIN Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
ro.com.android.dataroaming=true
# END Motorola, a22417, 22-Mar-2010, IKSHADOW-2345,default data roaming is on
persist.mot.a2dp.direct = 0
# System property for SMC
ro.service.start.smc=1
# BEGIN Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
# 0 disable
# 1 enable
persist.mot.usb.mediasync = 1
# END Motorola, a21951, 17-Apr-2010, IKSHADOW-3602
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal BUA is preloaded, not allow to install standalone version of BuA from Android Market
# false Horizontal BUA is not preloaded
ro.HorizontalBUA=true
#Proximity sensor debounce time
mot.proximity.delay=450
mot.proximity.distance=60
# BEGIN Motorola, pkd348, 26-Apr-2010, ISHADOW-4035
# true Horizontal VVM is preloaded, not allow to install standalone version of VVM from Android Market
# false Horizontal VVM is not preloaded
ro.HorizontalVVM=true
# BEGIN Motorola, a22976, 21-May-2010, IKSHADOW-5385
# For Shadow only, NOT applied to Droid2 as requirement different
ro.mot.buttonlight.timeout=1
# END Motorola IKSHADOW-5385
ro.mot.master_clear.shredsd=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.kernel.android.ril=yes
persist.ril.mux.noofchannels=7
persist.ril.mux.ttydevice=/dev/ttyS0
persist.ril.modem.ttydevice=/dev/ttyUSB0
persist.ril.features=0x07
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
ro.config.notification_sound=Droid.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.default_usb_mode=0
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.1_r7
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.url.safetylegal=xxx
ro.setupwizard.enable_bypass=1
ro.com.google.clientid=android-motorola
ro.com.google.clientidbase=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.url.legal=xxx
ro.url.legal.android_privacy=xxx
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.com.motorola.smartsensor=true
ro.media.enc.hprof.file.format=mp4
ro.media.enc.hprof.codec.vid=m4v
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.enc.hprof.vid.fps=30
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.aud.bps=96000
ro.media.enc.hprof.aud.hz=16000
ro.media.enc.hprof.aud.ch=1
ro.media.enc.hprof.duration=60
ro.media.enc.lprof.file.format=mp4
ro.media.enc.lprof.codec.vid=m4v
ro.media.enc.lprof.codec.aud=amrnb
ro.media.enc.lprof.vid.width=320
ro.media.enc.lprof.vid.height=240
ro.media.enc.lprof.vid.fps=15
ro.media.enc.lprof.vid.bps=225000
ro.media.enc.lprof.aud.bps=12200
ro.media.enc.lprof.aud.hz=8000
ro.media.enc.lprof.aud.ch=1
ro.media.enc.lprof.duration=30
ro.media.enc.dprof.file.format=mp4
ro.media.enc.dprof.codec.vid=h264
ro.media.enc.dprof.codec.aud=aac
ro.media.enc.dprof.vid.width=720
ro.media.enc.dprof.vid.height=480
ro.media.enc.dprof.vid.fps=30
ro.media.enc.dprof.vid.bps=4000000
ro.media.enc.dprof.aud.bps=96000
ro.media.enc.dprof.aud.hz=16000
ro.media.enc.dprof.aud.ch=1
ro.media.enc.dprof.duration=60
ro.media.enc.file.format=3gp,mp4
ro.media.enc.vid.codec=h264,m4v,h263
ro.media.enc.aud.codec=aac,amrwb,amrnb
ro.media.enc.vid.h264.width=176,720
ro.media.enc.vid.h264.height=144,480
ro.media.enc.vid.h264.bps=64000,8000000
ro.media.enc.vid.h264.fps=1,30
ro.media.enc.vid.h263.width=176,320
ro.media.enc.vid.h263.height=144,240
ro.media.enc.vid.h263.bps=64000,8000000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.m4v.width=176,1280
ro.media.enc.vid.m4v.height=144,720
ro.media.enc.vid.m4v.bps=64000,8000000
ro.media.enc.vid.m4v.fps=1,30
ro.media.enc.aud.amrnb.bps=4750,12200
ro.media.enc.aud.amrnb.hz=8000,8000
ro.media.enc.aud.amrnb.ch=1,1
ro.media.enc.aud.amrwb.bps=6600,23850
ro.media.enc.aud.amrwb.hz=16000,16000
ro.media.enc.aud.amrwb.ch=1,1
ro.media.enc.aud.aac.bps=8192,131072
ro.media.enc.aud.aac.hz=16000,16000
ro.media.enc.aud.aac.ch=1,1
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=60
ro.media.capture.flash=led
ro.media.capture.classification=classD
ro.media.capture.useDFR=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.url.legal=xxx
ro.url.legal.android_privacy=xxx
ro.mot.hw.uaprof=xxx
ro.build.version.full=Blur_Version.1.13.604.MB810.Verizon.en.US
ro.config.ringtone=DroidRollin.ogg
I would love to be able to capture video at higher frame rates! Slow motion is awesome.
Sent from my DROIDX using XDA App
any more luck with this. I was thinking and im no dev so tell me if im retarded, but have you changed the capture fps to 60 as well as the encode to 60 and what would happen if you changed not only the instances of 30 to 60 but the instances of 1 to 30 also. just throwing some ideas off the wall because this sound like a cool idea
I thought about that, but I am holding off until I find out where the the instruction to capture 24fps for the HD video is located. I think if I find that, I will also find the settings for the slow motion.
grndnpnd said:
any more luck with this. I was thinking and im no dev so tell me if im retarded, but have you changed the capture fps to 60 as well as the encode to 60 and what would happen if you changed not only the instances of 30 to 60 but the instances of 1 to 30 also. just throwing some ideas off the wall because this sound like a cool idea
Click to expand...
Click to collapse
anymore luck man
try to find a way to slow down time and you'll be all good mang
ixobelle said:
try to find a way to slow down time and you'll be all good mang
Click to expand...
Click to collapse
way to be productive with your comments man
i wish you the best of luck at this and if i can help with testing at all pm me my dx will be on my doorstep in a couple days
Have you looked here?
http://alldroid.org/default.aspx?g=posts&t=504
Sent from my DROIDX using XDA App
Just because you didn't initially see a difference in quality when you bumped up the bit rate doesn't mean its not there. I've been doing green screen tests and have yeilded impressive results so far. Solid colors are still pretty blocky and a higher would definately help. I've been doing side by side tests with an iphone4 as well. So far the dx's higher bitrate yields a cleaner key. Im using a professional cyc and lights of course and primate to key it out.
Sent from my DROIDX using XDA App
gunkle said:
Have you looked here?
http://alldroid.org/default.aspx?g=posts&t=504
Click to expand...
Click to collapse
Yes - I posted in that thread (post 16) and never got a response.
michael_bolton said:
Just because you didn't initially see a difference in quality when you bumped up the bit rate doesn't mean its not there. I've been doing green screen tests and have yeilded impressive results so far. Solid colors are still pretty blocky and a higher would definately help. I've been doing side by side tests with an iphone4 as well. So far the dx's higher bitrate yields a cleaner key. Im using a professional cyc and lights of course and primate to key it out.
Click to expand...
Click to collapse
At what bitrate do your tools tell you the video quality is better?
The data rate on the X is almost twice that of the iphone4. In real life the effect may give iphone more aparent contrast but in reality there is less information in the video. This is quite obvious when chroma keying.
When I have more down time i'll post some studio examples
Sent from my DROIDX using XDA App

[TWEAKS] List of build.prop tweaks (can be applied to stock ROM)

I'll share with you the /system/build.prop tweaks I have in the upcoming Nova.
You can do this on any ROM, even on stock, you just need a file manager with root access and built-in editor. Edit this file and add/change/remove values as follows.
Here we go:
Code:
# Force launcher into memory
ro.HOME_APP_ADJ=1
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
# VM Heapsize; 512MB RAM = 48 is better
dalvik.vm.heapsize=48m
# Render UI with GPU
debug.sf.hw=1
# Decrease dialing out delay
ro.telephony.call_ring.delay=0
# Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
# Save battery
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
# Disable debugging notify icon on statusbar
persist.adb.notify=0
# Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Photo and video recording quality tweak
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Signal tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# Net tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
# Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
# Fix some application issues
ro.kernel.android.checkjni=0
# Phone will not wake up from hitting the volume rocker
ro.config.hwfeature_wakeupkey=0
# Force button lights on when screen is on
ro.mot.buttonlight.timeout=0
# Disable boot animation for faster boot
debug.sf.nobootanimation=1
# Miscellaneous flags
ro.config.hw_menu_unlockscreen=false
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
# LG flags
persist.service.pcsync.enable=0
persist.service.lgospd.enable=0
Adding some more (14/08/11) for Nova v4...
Code:
# Change ROM name
# (forgot to add this one before)
ro.build.lge.version.release=My ROM name
# Disable LG ****
# (flex must be enabled or phone app will FC) - [U]needs moar testing[/U]!
user.feature.flex=true
user.feature.lgdrm=false
user.feature.lgresource=false
user.feature.lgpoweroff=false
user.feature.ls_event=false
user.feature.ls_normal=false
user.feature.sui=false
If anyone has some other tweaks or better values (tested of course) please do share.
Thanks! I go to try with the Orange stock rom v10b.
Nice Noejn.
# Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
Here I use 260 and it is very smooth and responsive. The maximum value for this tweak is 300.
# Save battery
wifi.supplicant_scan_interval=180
180 is the scan interval in seconds so you can use a lower or higher value.
Good topic
Noejn said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Code:
# Net tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
I don't know what those values used to be in their default state, but I am sure that it isn't sensible to use the same values for all networks. TCP buffer sizes should consider bandwidth and delay of the connection, which are both vastly different between edge and wifi for example.
Other values which seem interesting are:
Code:
user.feature.lgdrm=false # disable lg drm service
I can confirm this will disable the lg drm service - I have no idea what it does, but apparently I don't need it.
Code:
user.feature.flex # don't disable this
flex must be enabled, else com.android.phone and com.android.mms will crash constantly.
These can be disabled without visibly breaking something:
Code:
user.feature.lgresource
user.feature.lgpoweroff
user.feature.ls_event
user.feature.ls_normal
user.feature.sui
Anyone know what they do?
Click to expand...
Click to collapse
launcher into memory
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
can also be used using another launcher, like Launcher7 or Zeam? Have i change something?
Wady el-Natrun said:
can also be used using another launcher, like Launcher7 or Zeam? Have i change something?
Click to expand...
Click to collapse
Of course =) It will do the same for every launcher. It isn't specific for LG.
I really don't get it... If this value actually given a better performance, why didn't those LG's engineer use this value for stock ROM?
They do know aren't they?
i04055 said:
I really don't get it... If this value actually given a better performance, why didn't those LG's engineer use this value for stock ROM?
They do know aren't they?
Click to expand...
Click to collapse
Ask them, they come to this forum.
don't tell me they come here to learn how to make a better ROM...
Maybe the factory setting is for failsafe defaults. Like ones on computer BIOS, only advanced user dare to change to their own setting.
Sent from my LG-P970 using Tapatalk
Noejn, but...his change are already in your NOVA rom?
Becouse when i open the build.prop i found all this tweaks. (i have your rom)
of course, it is already included in teh Nova ROM....
digitalfrost said:
Noejn said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Click to expand...
Click to collapse
I would also prefer a quality factor of 90-95% in Nova as 100% results in much larger files and only slightly better quality.
Click to expand...
Click to collapse
lesp4ul said:
Maybe the factory setting is for failsafe defaults. Like ones on computer BIOS, only advanced user dare to change to their own setting.
Click to expand...
Click to collapse
My guess is they can't lose time on experimental values.
They will go for stable and heavily tested ones already.
digitalfrost said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Click to expand...
Click to collapse
Irrelevant. You have plenty of space in /system partition and having this really won't affect your internal memory because:
a) you already have reserved space for system partition
b) we're talking about 3 MB, tops. considering I removed 80% of LG applications which account for like 150 MB do you think that system partition is that small?
So it's a luxury we can perfectly have. Besides, I do notice 10% of quality difference.
digitalfrost said:
Other values which seem interesting are:
Code:
user.feature.lgdrm=false # disable lg drm service
I can confirm this will disable the lg drm service - I have no idea what it does, but apparently I don't need it.
Click to expand...
Click to collapse
Nice tip.
But they have a whole partition for that service, it's strange you don't notice a difference.
Wady el-Natrun said:
Noejn, but...his change are already in your NOVA rom?
Becouse when i open the build.prop i found all this tweaks. (i have your rom)
Click to expand...
Click to collapse
In the new version yes. In the old one I guess a missed a few.
@Noejn
build.prop tweak. it can use in stock firmware v10e?
Noejn said:
My guess is they can't lose time on experimental values.
They will go for stable and heavily tested ones already.
Click to expand...
Click to collapse
Yes it could be, too, LG r&d guys surely knew about this and decided to setup this defaults. That's why smart devs like you and other nova contributors should maximize this phone potential, what next?
Sent from my LG-P970 using Tapatalk
i04055 said:
of course, it is already included in teh Nova ROM....
Click to expand...
Click to collapse
Yeah, I didn't found any changeable because they are already tweaked haha.
Sent from my LG-P970 using Tapatalk
Is it right that i must add the most of your tweaks in stock rom?
Because i can't find these lines in stock rom build.prop!
There is only "dalvik.vm.heapsize=32m" to find!
And if i add these tweaks, i can simply write them on the end of the page?
With or without the "#" line?
Thank you
# Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
this option didn't work for me... I even tried to change do 10, 3, even 1, I didn't see any difference...
Applied only few tweaks to stock 10e:
mod sql by Noejn
ro.HOME_APP_ADJ=1
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
And now UI seems a bit too responsive and fast in some cases, heheheh

[HELP, MIUI, BOOTANIMATION] Droid Razr BootAnimation On MIUI

Hi Help! All Droid Bootanimations, are very slow with MIUI, how or who can help me modify it to be normal/fast?,
This is the new dorid razr bootanimation, but with MIUI is very slow.......
This is the bootanimation http://www.droid-life.com/2011/11/02/download-droid-razr-boot-animation-and-sounds/
DESC.TXT
# 540 wide, 960 tall 15 frames per second
540 960 15
# p means we're defining a part
# first number is repeat count, 0 means infinite
# second number is delay in frames before performing the next part
# so if you are playing 15 frames a second 15 would be... one second
# string defines the directory to load files from
# files will be loaded in order but names don't matter
# s defines a sound for a part
# sounds will be loaded from /system/media
# oggs with loop points will loop automatically
# only one sound will play at a time
# timing is driven by the part, not the sounds
# if you want no sound, leave blank
# droid
p 1 7 01_droid
# mobility
p 1 0 02_mobility
s droidhd.ogg
# loop
p 0 0 03_loop
i'd love to use this if any of you clever boffins can get it working on miui
APEX.7 i open on my phone with es explorer old flash theme and get him .zip then i open it on pc and put to him droid raxr boot animation then i install it in recovery and wala-wala!)

[TUT] Build.prop Modifications how to !

Hello all from research and test o my rom dev discovered this and want share it with all can help ^^
The following lines in the build.prop file can be added and edited to change several properties in your device:
debug.sf.hw = 1
Render UI with GPU (relieves pressure on CPU)
dalvik.vm.heapsize = 32m
Set size of Dalvik VM heap (how much RAM each instance of the VM is allowed); depending on how much RAM that is available to a device, this can be increased.
persist.adb.notify = 0
Stop debugging icon from appearing in status bar
windowsmgr.max_events_per_sec = 120
Increase to improve scrolling response
persist.sys.use_dithering = 0
Do not use surface dithering (surface dithering improves image quality)
debug.sf.nobootanimation = 1
Disable boot animation
ro.HOME_APP_ADJ = 1
force home launcher into memory
ro.sf.lcd_density = 240
Set screen density; change according to your device or what suits you, a lower value will display more but may be too small to use on a device with a smaller screen. Also note that changing the pixel density will make some applications in the new market ‘incompatible with your device’.
mot.proximity.delay = 150
Lower to fix black screen after calls issue
ro.telephony.call_ring.delay = 0
Decrease dialling out delay
ro.gsm.2nd_data_retry_config = max/_retries=3, 2000, 2000, 2000
Change MMS APN retry timer from 5s to 2s
wifi.supplicant_scan_interval = 120
ro.ril.disable.power.collapse = 0
pm.sleep_mode = 1
Increase battery saving potential
ro.com.android.dataroaming=true
Enables data-roaming by default in the build
ro.com.android.dateformat=dd-MM-yyyy
Changes default date format to day-month-year
ro.config.alarm_alert=*.ogg
ro.config.ringtone=*.ogg
ro.config.notification_sound=*.ogg
Changes the default sounds for each item. Must correlate to ogg files available in /system/media/audio/
ro.build.display.id=NAMEOFROM
In Settings>About Phone, it lists the name of the build number. This is where you set it.
ro.product.locale.language=en
ro.product.locale.region=GB
Sets the default region and language. You must have the correct letter combo, and the language must be available for this to work.
video.accelerate.hw=1 or 0
Whether to use hardware acceleration to render videos, doesn’t work on all devices​
Some of those lines are missing from my build.prop. Can I place them anywhere in my build.prop or not?
jayrome876 said:
Some of those lines are missing from my build.prop. Can I place them anywhere in my build.prop or not?
Click to expand...
Click to collapse
yes after all line add thos you want

[APP] CpuFloat [March27] Floating cpu, gpu, temperatures, deep sleep, network monitor

CpuFloat
Uses a floating window or the status bar to show
# the cpu frequencies
# the cpu temperature if (available)
# the text will turn red when the cpu temperature rises above the throttle temperature. You can set custom throttle temperature in preferences.
# the gpu frequency
# Gpu load; not normalised
# the gpu temperature if (available)
# the text will turn red when the gpu temperature rises above the throttle temperature.
# awake time; the time the phone has been awake since starting the app
# deep sleep time; the time the phone has been asleep since starting the app
# battery current
# battery current
# current upload and download speed
In preferences you can choose
# floating window layout; vertical or horizontal layout
# to show the window in the status bar instead of a floating window
# the categories to monitor; all, cpu, gpu, time, network
# which temperature sensor to use for cpu and gpu temperature
# to show the temperature in Fahrenheit instead of Celsius
# cpu throttle point; cpu temperature when the text should turn red
The app uses following permissions:
"android.permission.SYSTEM_ALERT_WINDOW" Needed for floating window, draw over other windows.
"android.permission.READ_EXTERNAL_STORAGE" Read data to show e.g. Cpu frequency, temperature etc.
"android.permission.VIBRATE"
Credits to:
CM Calculator apk for user interface logic
@m11kkaa for temperature file paths and thread http://forum.xda-developers.com/xposed/modules/mod-cputemp-statusbar-t2494170
@existz for awake and deep sleep time method http://forum.xda-developers.com/google-nexus-5/themes-apps/app-cpu-spy-material-v1-0-t2948627
@Grarak for GPU frequency file paths http://forum.xda-developers.com/android/apps-games/app-kernel-adiutor-t2986129
consp1racy for SeekBarPreference https://github.com/consp1racy/android-support-preference
The Tester for catching exceptions and throwing ideas
For automatic updates:
Request
If you´d like to use the app in your native language, you can!
How?
Download the string resource file, copy it and the translate the underlined part, for example
<string name="settings">Settings</string>
becomes
<string name="settings">Instellingen</string>
and post it in this thread.
Thanks!
ChangeLog:
March 17
-startup bug, thanks to Bryan
-GPU frequency on some devices
+battery temperature
Older changelogs:
September 26
- bugs
+ battery current correction
+ clear data dialog in case of fatal crash
September 24
+ battery current monitor
+ notification; enable if CpuFloat suddenly disappears
+ set monitor defaults
+use android M (6) permissions
+important notice about app permissions for android M (6) and up
+transparent background
+GPU trippoint
+ changelog
- some bugs
June 14
Fixed crash
Improve right to left layout
June 12
Added
#Text size
#Show window on the navigation bar
#Update interval (100ms - 3000ms)
#Number of CPUs to monitor
#First time helpful animation
#About screen
#Now on Google Play Store
Fixes and improvements
#Don´t update when the screen is off
#Don´t kill service when changing the window layout
#Language in settings
#Support more GPUs
#Use SeekBarPreferences in settings
November 12
# added some animations
# 'material' window look
# layout changes in case of more than 7 cpu cores
# broadcast listener for landscape/ portrait change
in preferences
# turn on/off vibration
# restore default values
November 3
# user interface logic
November 1
# fixed preference bugs
October 31
# manually set which temperature sensor to use for the cpu and gpu temperature
October 25
# hopefully fixed force close on start
October 23
# fix bug, window not showing on start
# custom cpu temperature trippoint in preferences
October 19
# used some icons instead of text
# option to show window in status bar
October 17
# started to make it work on other phones
# cpu and gpu temperature file info in preferences
October 14
# more layout options
# bugs and performance fixes
October 11
# no more StandOutWindow library
# no notification
# improved long press detection
October 4
# monitor up and download speed
# option to show the temperature in Fahrenheit
October 1
# warning in case the temperature reaches the throttle temperature of cpu or gpu
# tap app window to close
# long press app window for preferences
Preferences:
# choose horizontal / vertical layout
# choose what to monitor
September 27
# rewritten to make it easier to use on other phones
# new app icon
# smaller window
//TODO make preferences
Very nice app.
Thanks dude
That's a nice idea. The app is working without problems as far as I can tell. Great job man!
Sent from my OPO running Sultanxda's CM 12.1
Amazing app! Thanks man!
Nice app
Nice app - similar to the one developed by Chainfire (called Perfmon) but this one shows you the awake time and the temps.
Thank you for this
update:
# rewritten to make it easier to use on other phones
# new app icon
# smaller window
Nice app. Would be nice to have a widget like that.
Sent from my Oneplus One using XDA Free mobile app
Update
# warning in case the temperature reaches the throttle temperature of cpu or gpu
# tap app window to close
# long press app window for preferences
Preferences:
# choose horizontal / vertical layout
# choose what to monitor
Bugfix
Temperature warning not showing in horizontal layout
Thank you for this! Really helpful for monitoring governor and hotplug.
Update
Rewritten
Much smaller now
# no notification
# no more StandOutWindow library
# improved long press detection
Because of a change in package name,
please delete previous version, else you'll end up with 2
waterdaan said:
Update
Rewritten
Much smaller now
# no notification
# no more StandOutWindow library
# improved long press detection
Because of a change in package name,
please delete previous version, else you'll end up with 2
Click to expand...
Click to collapse
Very nice.
Thank you
arifqur said:
Very nice.
Thank you
Click to expand...
Click to collapse
Thanks for the positive reactions
Update
# more layout options
# bugs and performance fixes
Update
# started to make it work on other phones
# cpu and gpu temperature file info in preferences
Request
I'm trying to get the app to work on other phones, so if you have another phone, please test what's working.
If there's no cpu temperature, that probably means that the app can't find the temperature files. These are not the same on every phone.
If the phone is rooted, you can help me by copying and pasting below code in command line, with for example this app https://play.google.com/store/apps/details?id=jackpal.androidterm
And posting the outcome here, so I can add the missing file.
Code:
su
find /sys -type f -name *temp* -print0|while read -d $'\0' f;
do printf "$f= "&&cat "$f";done;
Thanks!
Gpu temperature is a bit more difficult, because you need to find out which temperature sensor is for the gpu, I found that information for the oneplus in
/etc/thermal-engine-8974.conf
Reported working on:
OnePlus fully working
Moto X gpu temperature not working
Samsung S4 gpu temperature not working
Thank you!!
Update
# used some icons instead of text
# option to show window in status bar
Edit
The app is fully working on the Sony Z3 Compact, it even uses the same files for cpu temperature and gpu temperature, maybe because it also has a snapdragon 801, but I'm not sure about that.
I must be missing something but how do I reopen the window after having tapped on it to close it?
Because opening the app from the drawer takes me to the preferences screen.
Killerkip said:
I must be missing something but how do i reopen the window after having tapped on it to close it?
because opening the app from the drawer takes me to the preferences screen.
Click to expand...
Click to collapse
You're right, that's not very clear, I'll see if I can change that.
For now just change something in the preference screen and a new window will open.
Thank you for your reaction
Update
# fix bug, window not showing on start @Killerkip
# custom cpu temperature trippoint in preferences

Categories

Resources