Originally Posted by PoXFreak

Okay, this is the EXACT build.prop file from Scoot's CM 7 and, after looking, there are things in this build prop that don't belong ANYWHERE near a Kaiser/Polaris/Vogue.
Nothing against Scoot at all as most devs overlook small performance details such as this. I have all the respect for Scoot and other devs, without them we wouldn't be where we are now.

I won't go into detail but some of the things are:
1. Number of available CPUs'
2. Kernel and dalvik jni checking
3. Missing fields for assigning data rates to different packet carriers (GPRS, EDGE, UTMS).
4. JPEG memcap set way too high, should be no more than 6000000-8000000.

AND the entries that I would have to make would have to overwrite both local.prop and buildinfo.sh, that way all those files (build.prop/local.prop/buildinfo.sh) can be merged via an androidupdate.tar, OR (how I would prefer it be done), edit/merge the files individually inside the androidinstall.tar file.
This is just my opinion, of course... the way I would do it.

Anyone have a better idea?... Msg me or post here.

Please tell me how can I create androidupdate file from my build.prop.
Thank you in advance!

Originally Posted by ZLodei

Please tell me how can I create androidupdate file from my build.prop.
Thank you in advance!

Since you are going to install it anyway, I'll tell you how to do it.
Very easy, just create a folder named /system, copy your build.prop inside of the new folder, make a 7-zip tarball, uncompressed, and name it androidupdate.tar.
It's just that simple...
DISCLAIMER!
I am not responsible for any mistakes you make or if it screws up your device!
All I can do is to tell you to MAKE SURE you made a backup of your current device, achieved by holding D-pad center when booting and selecting "Backup Data" from the replimenu. Whole process should take no more than 5 minutes.
That way, if something does get ruined, all you have to do is "Restore Backup" from replimenu and all should be right in the world...

Originally Posted by PoXFreak

Okay, this is the EXACT build.prop file from Scoot's CM 7 and, after looking, there are things in this build prop that don't belong ANYWHERE near a Kaiser/Polaris/Vogue.
Nothing against Scoot at all as most devs overlook small performance details such as this. I have all the respect for Scoot and other devs, without them we wouldn't be where we are now.

I won't go into detail but some of the things are:
1. Number of available CPUs'
2. Kernel and dalvik jni checking
3. Missing fields for assigning data rates to different packet carriers (GPRS, EDGE, UTMS).
4. JPEG memcap set way too high, should be no more than 6000000-8000000.

AND the entries that I would have to make would have to overwrite both local.prop and buildinfo.sh, that way all those files (build.prop/local.prop/buildinfo.sh) can be merged via an androidupdate.tar, OR (how I would prefer it be done), edit/merge the files individually inside the androidinstall.tar file.
This is just my opinion, of course... the way I would do it.

Anyone have a better idea?... Msg me or post here.

Hi, ProXFreak!
What do you think about this build.prop for scoots CM7? I tied to build a combination of your tweaks and the 'original'. I would be glad to benefid of your knowledge.

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRJ22
ro.build.display.id=GRJ90
ro.build.version.incremental=eng.scooter.20110807. 101617
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Sun Aug 7 10:20:10 BST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=scooter
ro.build.host=scooter-N50Vc
ro.build.tags=test-keys
ro.product.model=HTC Kaiser
ro.product.brand=htc
ro.product.name=soju
ro.product.device=kaiser
ro.product.board=
ro.product.cpu.abi=armeabi
#ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=kaiser
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=soju-user 2.3.4 GRJ22 121341 release-keys
ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=Pixie Dust.ogg
ro.config.ringtone=Road Trip.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
rild.libpath=/system/lib/libhtcgeneric_ril.so
ro.com.android.dataroaming=false
ro.ril.hsxpa=4
ro.ril.gprsclass=5
ro.ril.hep=1
ro.ril.hsdpa.category=10
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskwl.bitmask=4294967295
ro.ril.htcmaskwl=268449905
ro.ril.hsupa.category=6
ro.telephony.default_network=0
ro.ril.call_ring.delay=0
#ro.kernel.android.checkjni=0
#dalvik.vm.checkjni=false
ro.com.google.locationfeatures=1
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
ro.media.dec.jpeg.memcap=6000000
#ro.opengles.version=65536
video.accelerate.hw=1
debug.sf.hw=1
#dalvik.vm.execution-mode=int:fast
#dalvik.vm.dexopt-data-only=1
dalvik.vm.lockprof.threshold=500
#persist.sys.use_dithering=0
#persist.sys.purgeable_assets=1
#ro.tether.denied=true
dalvik.vm.heapsize=24m
dalvik.vm.startheapsize=4
debug.performance.tuning=1
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.enable.dtm=1
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=180
ro.sf.lcd_density=120
ro.compcache.default=26
ro.workaround.noautofocus=1
view.fading_edge_length=8
view.touch_slop=15
view.minimum_fling_velocity=25
view.scroll_friction=0.008
ro.rommanager.developerid=cyanogenmod
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.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
ro.com.android.dateformat=dd-MM-yyyy
ro.com.android.dataroaming=false
ro.modversion=CyanogenMod-7.1.0-RC1-kaiser-KANG
#ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Sorry for the late reply...
All I can say at this point is to plug it in through androidupdate or via cut + paste method through root explorer.
Make a databackup.img before you install it, so if something is wrong you can go back and start over without messing up your current setup.

tank's for dhe help.

Which kernel would you recommend for that fresh froyo build (on nand)?

Originally Posted by mkrle

Which kernel would you recommend for that fresh froyo build (on nand)?

For any rom nand on Kaiser I recommend nothing except the kernel with separate cache. I can still build kernels and roms for Kaiser but seriously nothing was developed after that kernel. One developer at about the same time made great strides toward enabling dynamic overclocking but his last attempt came before the separate cache breakthrough. It would be great if that could be finished and given a separate cache. But I think all the former developers of this phone have moved on.

Sent from my Galaxy Nexus using XDA

This is true, I think devs have all but stopped working on this and moved on to bigger and brighter things.
As n2 stated, kernel with cache is your best bet, just be sure to set your /system partition as small as possible to gain extra /data space.
For fresh froyo that would be no less than 78MB with a 20MB cache, leaving about 112MB for data.

Sent from this addictive thumb magnet...