I am not sure what exactly goes where and I'm tired of messing with it.
This is what I'm looking at:
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing
# ppp.password - The password used to connect to the network when dialing
# ppp.apn - Set apn of your provider
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "board-htckaiser.panel_type=0 ppp.apn=www.vodafone.net.nz ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=324 mddi.height=432 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Please just send me the file to [email protected]
C'mon, search the wiki. It took me a whole 30 sec to find this!
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd "\Storage Card\initrd.gz"
set cmdline "[email protected] ppp.password=CINGULAR1 board-kaiser-keypad.atttilt=0 pm.sleep_mode=4 board-htcvogue.panel_type=0 msm_sdcc.msmsdcc_fmax=20000000 no_console_suspend"
boot
Click to expand...
Click to collapse
Dave
Still not connecting to internet. Do I need to erase all the other stuff out of the middle?
Do you need to ask this in another thread?
DaveTheTytnIIGuy said:
C'mon, search the wiki. It took me a whole 30 sec to find this!
Dave
Click to expand...
Click to collapse
Thanks. It worked. However, now all the icons and fonts are huge. I have to zoom out every time I go to a new page. Plus my dialing pad numbers are all smushed together and the home screen icons as well.
I am using the latest HTC TOUCH DIAMOND android port released 9/9/9 released at connect-utb and after having to add the ramaddr line to the startup then change the startup.txts name to default.txt and starting it up the command line runs and the penugin comes up then after a bit of alot of text scrolling it goes to a complete black screen except a "_" underscore blinking at the very top left.. If anyone has a default.txt that works for the htc touch diamond with this release id love to have it.. any help? it just sit sthere and every now and then the underscore unfreezes and blinks a few time then freezes for awhile. how do i get past this i want to play with android!
Anyone help please?.
Also its a diam500 and heres my startup.txt that im using..
Code:
set RAMSIZE 0x06000000
set ramaddr 0x10000000
set MTYPE 1805
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Hitachi 2=Topoly 3=Samsung
# mddi.width - width of the scaled display
# mddi.height - height of the scaled display (these should be multiples of 16 for the camera to work I think)
set cmdline "msmts_calib=115.105.863.911 msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=240 ppp.apn=movistar.es ppp.username=MOVISTAR ppp.password=MOVISTAR no_console_suspend"
#set cmdline "no_console_suspend"
# fbcon=rotate:1
# console=ttyMSM0"
boot
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
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