Hi guys. Just wondering if anyone can help me. What i want to do is in the 'About Phone' section in 'Settings' i want to make the following changes if possible:
Model Number - change to Peter Griffin G1
Firware Version - 2.6
Mod Version - 9.2
Build Number - 1
I know it may sound a bit silly/stubid but itd be awesome if i could actually do tnat
Thanks in advance
ps im running Herver's 1.1.1 eclair build (its the best at the minute)
If you have adb setup this can easily be done
The information can be found in 1 or 2 files:
build.prop or build.trout.prop
use adb to pull these files as such
Code:
adb pull /system/build.prop /location/you/want/your/file (enter)
adb pull /system/build.trout.prop /location/you/want/your file (enter)
open the files in a txt editor, and look for the relevant fields based on the information already displayed on your phone, if your MOD Version is xROM-Eclair****** like mine or whatever it may say simply use ctrl+f to find that field in the txt editor and modify it. Once you've made all the relevant edits push the files back
Code:
adb push /location/of/file /system/build.prop (enter)
adb push /location/of/file /system/build.trout.prop (enter)
Then reboot your phone
Sorry to bother you again but is this correct :
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.sdk=7
ro.build.version.codename=AOSP
ro.build.version.release=2.1
ro.build.type=eng
ro.build.user=ctso
ro.build.host=h0meb0x
ro.build.tags=test-keys
ro.wifi.channels=
rild.libpath=/system/lib/libhtc_ril.so
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 = 140
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
# Default network type
# 0 => WCDMA Preferred.
ro.telephony.default_network = 0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.ril.hsxpa=1
ro.com.google.locationfeatures=1
ro.ril.gprsclass=10
ro.product.multi_touch_enabled=true
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.clientidbase=android-tmobile
net.bt.name=Android
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#
# RIL Hacks - Thanks Amon_RA
#
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
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
ro.modversion= #1
ro.ModelNumber= The Peter Griffin G1
ro.FirmwareVersion= 2.6
ro.BuildNumber= 1
Click to expand...
Click to collapse
push and reboot, to find out, keep a backup of your originals just incase
I was gonna say you should get a phone skin from Zagg or unique skins.
Thanks dude. I finally managed it this morning. Ended up having to change bits in both files
PS Im defo gonna try and get a Peter Griffin skin for my G1
I want to start working with dsixda's Android Kitchen, but unfortunately the Galaxy Ace isn't supported.
If someone is also interested in using this kitchen or just wants to help, please help me filling this in.
Till now I found this using #cat /proc/mounts
change_mnt=yes
sys_mnt=\/dev\/block\/stl12
cache_mnt=\/dev\/block\/stl14
boot_mnt=
data_mnt=\/dev\/block\/stl13
sdcard_mnt=\/dev\/block\/vold\/179:1
# The values below should be set in each file in this folder.
#
# Each file represents a device name (set in ro.product.device of
# build.prop)
#
# If yes, then this device requires changing the mount point
# names in the new updater-script or update-script
# DO NOT SET TO 'yes' IF DEVICE IS BY DELL
change_mnt=no
# If yes, the device is by Dell and requires changing the mount
# point names in the new updater-script or update-script
change_mnt_dell=no
#
# NOTE: The update-script will be converted to updater-script if the
# definition file for the device exists. If 'change_mnt' or
# 'change_mnt_dell' are set to 'yes' then the mount names will
# also be changed.
#
# Mention the mount point names if change_mnt=yes
# Use '\/' instead of '/'
# e.g. sys_mnt=\/dev\/block\/mcblk0p25
#
# If unknown, set to: ???
sys_mnt=
cache_mnt=
boot_mnt=
data_mnt=
sdcard_mnt=
# Set this mount point for the modem.bin in Samsung devices like the Galaxy S2
modem_mnt=
# Set this mount point if you know what it is (e.g. on Motorola Atrix)
webtop_mnt=
# Filesystem info for SYSTEM/DATA/CACHE/etc.
# e.g. param1=ext3, param2=EMMC
param1=
param2=
# If SDCARD filesystem is different from above, then mention it
# e.g. param1_sdcard=vfat, param2_sdcard=MTD
param1_sdcard=
param2_sdcard=
# If CACHE filesystem is different from above, then mention it
param1_cache=
param2_cache=
# If yes, the device does not require using a temp folder when
# flashing the boot.img in the updater-script
fix_boot=no
# Device uses /cache instead of /tmp, e.g. when writing boot.img
use_cache_not_tmp=no
Example of Galaxy S
# Samsung Galaxy S GT-I9000
change_mnt=yes
param1=yaffs2
param2=MTD
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/stl9
cache_mnt=\/dev\/block\/stl11
boot_mnt=\/dev\/block\/bml7
data_mnt=\/dev\/block\/mmcblk0p2
sdcard_mnt=\/dev\/block\/mmcblk0p1
modem_mnt=\/dev\/block\/bml12
Hey, i know this is old thread, but i'm interested. There are news about that???
Anybody? Have been stuck on this since yesterday.
i am new..
1jesper1 said:
I want to start working with dsixda's Android Kitchen, but unfortunately the Galaxy Ace isn't supported.
If someone is also interested in using this kitchen or just wants to help, please help me filling this in.
Till now I found this using #cat /proc/mounts
change_mnt=yes
sys_mnt=\/dev\/block\/stl12
cache_mnt=\/dev\/block\/stl14
boot_mnt=
data_mnt=\/dev\/block\/stl13
sdcard_mnt=\/dev\/block\/vold\/179:1
# The values below should be set in each file in this folder.
#
# Each file represents a device name (set in ro.product.device of
# build.prop)
#
# If yes, then this device requires changing the mount point
# names in the new updater-script or update-script
# DO NOT SET TO 'yes' IF DEVICE IS BY DELL
change_mnt=no
# If yes, the device is by Dell and requires changing the mount
# point names in the new updater-script or update-script
change_mnt_dell=no
#
# NOTE: The update-script will be converted to updater-script if the
# definition file for the device exists. If 'change_mnt' or
# 'change_mnt_dell' are set to 'yes' then the mount names will
# also be changed.
#
# Mention the mount point names if change_mnt=yes
# Use '\/' instead of '/'
# e.g. sys_mnt=\/dev\/block\/mcblk0p25
#
# If unknown, set to: ???
sys_mnt=
cache_mnt=
boot_mnt=
data_mnt=
sdcard_mnt=
# Set this mount point for the modem.bin in Samsung devices like the Galaxy S2
modem_mnt=
# Set this mount point if you know what it is (e.g. on Motorola Atrix)
webtop_mnt=
# Filesystem info for SYSTEM/DATA/CACHE/etc.
# e.g. param1=ext3, param2=EMMC
param1=
param2=
# If SDCARD filesystem is different from above, then mention it
# e.g. param1_sdcard=vfat, param2_sdcard=MTD
param1_sdcard=
param2_sdcard=
# If CACHE filesystem is different from above, then mention it
param1_cache=
param2_cache=
# If yes, the device does not require using a temp folder when
# flashing the boot.img in the updater-script
fix_boot=no
# Device uses /cache instead of /tmp, e.g. when writing boot.img
use_cache_not_tmp=no
Click to expand...
Click to collapse
hey man thanks for info .
i use to use xperia x8 and i heard bricked during flashing it.
now i have ace i. bt i still wanna make own Rom. this post May help me.
sorry for poor English.
List of build.prop tweaks for boost performance and for battery life
Checkout app ^^
Here!
~~~you can edit build.prop with File explorer that supports ROOT- you can start with File Manager
~~~Find build.prop file in /system
~~~if you have existing line,dont duplicate it (dont duplicate it)
~After you finish edit, save changes, CHECK PERMISSIONS must be -rw-r--r--, rebot to recovery and wipe cache and dalvik-cache ,rebot device
Click to expand...
Click to collapse
Thanks to @F4uzan
I read @LaraCraft304 thread HERE This help me too much
#disable the zygote loader for performance --- Crash, mostly
ro.wmt.blcr.enable=0
#help to free up unused ram --- this dont work on stock,you cant add this if kernel doesn't support purgeable of assets :/
persist.sys.purgeable_assets=1
# Video Acceleration
video.accelerate.hw=1
debug.performance.tuning=1
# Low Power Audio
lpa.decode=false
audio.decoder_override_check=true
use.non-omx.mp3.decoder=false
use.non-omx.aac.decoder=false
# Lock App In Memory
sys.keep_app_1=put-process-name-of-app-here --- Process name can find in /data/data, and put full name here
#battery savers
ro.ril.disable.power.collapse=0
ro.config.hw_power_saving=true
wifi.supplicant_scan_interval=180
power_supply.wakeup=enable
ro.ril.sensor.sleep.control=1
proximity_incall=enable
# Fast Reboot
persist.sys.shutdown.mode=hibernate
ro.config.hw_quickpoweron=true
#Enable Low Ram Device flag
ro.config.low_ram=true --- KITKAT ROMs ALREADY HAVE THIS LINE
#better scrolling
ro.max.fling_velocity=12000 --- this firs line already exist in KITKAT ROMs, I dont know to others (change it from 4000 to 12000)
ro.min.fling_velocity=8000
____but____
ro.maxfling_velocity=4000
ro.max.fling_velocity=4000
(4000 allows for a little more ram)
touch.presure.scale=0.001
windowsmgr.max_events_per_sec= max 90,every value over 90 decreas scroll
ro.min_pointer_dur=8
# Composition type
debug.composition.type=mdp
debug.composition.type=gpu -----choose------best-----you
debug.composition.type=cpu ----------------the--------for
debug.composition.type=dyn
#Dalvik tweaks --- @F4uzan said me: "It doesn't matter if it doesn't exist. Dalvik will set up default value. If you set it, Dalvik will prefer value in build.prop"
because I dont know this dalvik.vm.jmiopts=forcecopy --- I dont know what is that.. (someone say me?)
dalvik.vm.dexopt-flags=
Now you can set
~option 1- disable dalvik checking, increases free ram but less optimized dalvik cache
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,u=n,o=v
~option 2 (preferred)- enable more checking for a better performing dalvik cache but may use a little more ram
dalvik.vm.verify-bytecode=true
dalvik.vm.dexopt-flags=v=f,u=n,o=v
dalvik.vm.jit.codecachesize=0 --- this Disable JIT
# Enable Surface Dithering Which Will Raise Image Quality At The Cost Of Performances - 1=ON;0=OFF
persist.sys.use_dithering=0
#disable send data to google
ro.config.nocheckin=1
#Disable Kernel Error Checking
persist.adb.notify=0
vm.stat_interval=1
ro.kernel.android.checkjni=0
I add this to my build.prop, dont need but i prefer
#Enable Adaptive Multi-Rate Wideband
ro.ril.enable.amr.wideband=1
#More volume steps in call
ro.config.vc_call_steps= --- you can set as long as you want |||7 is default||| just put the number after the equal sign
#Better signal.
persist.cust.tel.eons=1
# Signal Tweaks
ro.ril.enable.amr.wideband=1
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1 --- dont use this if your carrier dont support
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
#Phone rings immediately.
ro.telephony.call_ring.delay=0
ring.delay=0
# Net Speed 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
net.tcp.buffersize.hspa=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hspda=4096,87380,256960,4096,16 384,256960
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
# Google DNS
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
#Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=true
#Increase photo and video recording quality
ro.media.enc.hprof.vid.bps=8000000
ro.media.capture.maxres=8m
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
ro.media.enc.hprof.vid.fps=65
# I dont know for what is it, but if your camera dont work on CM10 (I dont know for others) remove this line.
debug.camcorder.disablemeta=1
# Enables 270 Degree Rotation --- In Custom ROMs already have this
windowsmgr.support_rotation_270=true
#Increase jpg quality to 100%
ro.media.enc.jpeg.quality=100
#Better Flashlight intensity & camera-flash quality
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=65
ro.media.capture.flashIntensity=70
#Phone rings immediately.
ro.telephony.call_ring.delay=0
ring.delay=0
This tweaks dont work on LG devices, thanks to @F4uzan
pm.sleep_mode won't work
The sleep mode itself is hardcoded to kernel since ICS (or GB, I forgot), so changing it from build.prop won't work.
ro.mot.eri.losalert.delay is for Motorola device
Explained above
ro.config.nocheckin is actually ro.htc.config.nocheckin, so ro.config.nocheckin doesn't exist
Again, explained above
dalvik.vm.execution-mode is JIT, so no need to enable it via build.prop
Uh... explained again
profiler.force_disable_ulog is HTC specific properties
Found in services.jar of HTC ROMs but not on AOSP or LG ROMs
ro.mot.buttonlight.timeout, another properties for Motorola
Everything that starts 'ro.mot', 'ro.htc' won't work with LG phone, something that LG specific is 'lge.' or 'ro.lge'
windowsmgr.max_events_per_sec is a performance degrading thing
As quoted from Google, Android maxes 60fps which is windowsmgr.max_events_per_sec=90 setting it to higher value decreases scroll and touch speed, increase memory usages for UI events and such.
ro.kernel.checkjni, doesn't exist. Not in kernel or even frameworks.
Explained above.
dalvik.vm.checkjni and ro.kernel.android.checkjni won't work.
Already set to false by Android itself
ro.media.dec.jpeg.memcap value is hardcoded
Explained above.
ALL EXPLAINED HERE:
http://www.jeffmixon.com/examining-b...-guide-part-1/
http://www.jeffmixon.com/examining-b...-guide-part-2/
Click to expand...
Click to collapse
init.d tweaksThis init.d tweaks edited by me
You already know the process:
1. Go to recovery
2. Install zip
3. Rebot device
### ATTENTION ###
after flashing this device need about 3 minutes to boot
you do not need to worry, I already have this on my device
Sqlite_optimization
Click to expand...
Click to collapse
Downloads:
zipalign tweak zipalign all apps every 24 hours.
In:
all apps zipaligned
and now usage of this apps in RAM are lesser
Downloads:
View attachment 3133760
Zipalign_24_hours --- thanks to @kien_vip
Click to expand...
Click to collapse
RW_full_speed
Boost Read and Write speed
Downloads:
RW_full_speed
Click to expand...
Click to collapse
Apps for better battery life and performance
I use apps from playstore
Mediaserver Killer --- This app kills media server to save battery,and expand their life
Battery Doctor --- Also use this to expand your battery life
JuiceDefender - battery saver --- Battery saver app
Greenify --- Use this to hibernate apps
CPU Adjuster --- You can set CPU profiles, overclock device if you have overclock kernel
No-frills CPU Control --- I dont know, but I love this app more
[ROOT] Kernel Tweaker --- GPU, CPU tweaks, LMK
Voltage Control --- Undervolt processor to use less power
Android Tweaker 2 --- Tweak everything
This is cool brother, but I think some lines don't apply with stock roms, like purgeable assets. I will post the source.
chrisdlc119 said:
This is cool brother, but I think some lines don't apply with stock roms, like purgeable assets. I will post the source.
Click to expand...
Click to collapse
If kernel doesnt support this, you cannot add :/
Paget96 said:
If kernel dont suport this, you cannot add :/
Click to expand...
Click to collapse
Yes, that's more specific ?
chrisdlc119 said:
Yes, that's more specific ?
Click to expand...
Click to collapse
If you find something else, tell me
When i try to save the edition, its appear a litle box saying that i dont have root acess...but i have x)
What could be ?
jonnybigodesPT said:
When i try to save the edition, its appear a litle box saying that i dont have root acess...but i have x)
What could be ?
Click to expand...
Click to collapse
You have to mount the /system partition using an explorer that supports that function, for example, ES File Manager.
You also can download an app to edit Build.Prop from itself, it's very easy if you already have root access.
chrisdlc119 said:
You have to mount the /system partition using an explorer that supports that function, for example, ES File Manager.
You also can download an app to edit Build.Prop from itself, it's very easy if you already have root access.
Click to expand...
Click to collapse
The problem is solved. I thought I had edited the previous post x)
Thanks mate.
Thx bro i'll use these for my new rom!!!!
Sent from my LG-E400 using XDA Free mobile app
giaki3003 said:
Thx bro i'll use these for my new rom!!!!
Sent from my LG-E400 using XDA Free mobile app
Click to expand...
Click to collapse
now I edit sqlite and zipalign init.d tweak for kitkat
ahh, make for all roms check
Paget96 said:
ahh, make for all roms check
Click to expand...
Click to collapse
Flashed your scripts, device started but after a few hours I noticed that my phone was closed and when I tried to open it, it ended in bootloop. Restored my system backup, everything's fine. So must be your scripts. I think something is wrong with your flash zips. I checked with root explorer and extract the script but Root Explorer shows double file (f.e. 2 METADATA folders, 2 system folders etc.). I checked now in PC but zips seems OK.
I might put some note on build.prop tweaks here :
pm.sleep_mode won't work
The sleep mode itself is hardcoded to kernel since ICS (or GB, I forgot), so changing it from build.prop won't work.
ro.mot.eri.losalert.delay is for Motorola device
Explained above
ro.config.nocheckin is actually ro.htc.config.nocheckin, so ro.config.nocheckin doesn't exist
Again, explained above
dalvik.vm.execution-mode is JIT, so no need to enable it via build.prop
Uh... explained again
profiler.force_disable_ulog is HTC specific properties
Found in services.jar of HTC ROMs but not on AOSP or LG ROMs
ro.mot.buttonlight.timeout, another properties for Motorola
Everything that starts 'ro.mot', 'ro.htc' won't work with LG phone, something that LG specific is 'lge.' or 'ro.lge'
windowsmgr.max_events_per_sec is a performance degrading thing
As quoted from Google, Android maxes 60fps which is windowsmgr.max_events_per_sec=90 setting it to higher value decreases scroll and touch speed, increase memory usages for UI events and such.
ro.kernel.checkjni, doesn't exist. Not in kernel or even frameworks.
Explained above.
dalvik.vm.checkjni and ro.kernel.android.checkjni won't work.
Already set to false by Android itself
ro.media.dec.jpeg.memcap value is hardcoded
Explained above.
References :
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
http://www.jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2/
Thanks to Jeff Mixon site.
pkatsaras said:
Flashed your scripts, device started but after a few hours I noticed that my phone was closed and when I tried to open it, it ended in bootloop. Restored my system backup, everything's fine. So must be your scripts. I think something is wrong with your flash zips. I checked with root explorer and extract the script but Root Explorer shows double file (f.e. 2 METADATA folders, 2 system folders etc.). I checked now in PC but zips seems OK.
Click to expand...
Click to collapse
hm, I'll try to fix, thanks for test
sorry for bootloop
F4uzan said:
I might put some note on build.prop tweaks here :
pm.sleep_mode won't work
The sleep mode itself is hardcoded to kernel since ICS (or GB, I forgot), so changing it from build.prop won't work.
ro.mot.eri.losalert.delay is for Motorola device
Explained above
ro.config.nocheckin is actually ro.htc.config.nocheckin, so ro.config.nocheckin doesn't exist
Again, explained above
dalvik.vm.execution-mode is JIT, so no need to enable it via build.prop
Uh... explained again
profiler.force_disable_ulog is HTC specific properties
Found in services.jar of HTC ROMs but not on AOSP or LG ROMs
ro.mot.buttonlight.timeout, another properties for Motorola
Everything that starts 'ro.mot', 'ro.htc' won't work with LG phone, something that LG specific is 'lge.' or 'ro.lge'
windowsmgr.max_events_per_sec is a performance degrading thing
As quoted from Google, Android maxes 60fps which is windowsmgr.max_events_per_sec=90 setting it to higher value decreases scroll and touch speed, increase memory usages for UI events and such.
ro.kernel.checkjni, doesn't exist. Not in kernel or even frameworks.
Explained above.
dalvik.vm.checkjni and ro.kernel.android.checkjni won't work.
Already set to false by Android itself
ro.media.dec.jpeg.memcap value is hardcoded
Explained above.
References :
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
http://www.jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2/
Thanks to Jeff Mixon site.
Click to expand...
Click to collapse
i deleted
]windowsmgr.max_events_per_sec when is value over 90 scrolls decreases??
can you help me to add more build.prop tweaks for LGs ??
Yes, decreases. I set this value to 60.
And
ro.min.fling_velocity=16000
ro.max.fling_velocity=20000
mikesa said:
Yes, decreases. I set this value to 60.
Click to expand...
Click to collapse
"Many build.prop tweaks set this value to 300, but it seems this is a bad idea. As Google points out, Android maxes out at 60fps. The default value is already allow for a possible max_events_per_sec of 90. Even if you allow for 300 max_events_per_sec, you’ll only ever see 60 of these events in any given second. Therefore, any value much higher than 90 is unlikely to have any noticeable impact on your experience in general. Additionally, setting this value too high can starve other UI events that need to get processed, viz. touch inputs. You’re not likely to feel like your device is running very smoothly when it is busy processing thousands of scroll events instead of responding immediately to you clicking to try and open a link or an app. There may be some specific scenarios where increasing this value does appear to improve system feedback, but changing this value for all UI events across the board will likely cause more problems than it will solve."
copied from: http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/[/URL
you can go to 90 ]
I tired to 90, but I seems, my phone (Huawei p7) better the 60.
mikesa said:
I tired to 90, but I seems, my phone (Huawei p7) better the 60.
Click to expand...
Click to collapse
yes all mobiles are different
your scripts port from Fly on mod? your zipalign script will run on every boot, not every 30 hours. here is my zipalign script will run every 24 hours and correct permission 644 after zipaligning to avoid bootloop. may be some one like it:
Code:
#!/system/bin/sh
LOG_FILE=/data/zipalign.log;
ZIPALIGNDB=/data/zipalign.db;
# Interval between ZipAlign runs, in seconds, 86400=24 hours
RUN_EVERY=86400
# Get the last modify date of the Log file, if the file does not exist, set value to 0
if [ -e $LOG_FILE ]; then
LASTRUN=`stat -t $LOG_FILE | awk '{print $14}'`
else
LASTRUN=0
fi;
# Get current date in epoch format
CURRDATE=`date +%s`
# Check the interval
INTERVAL=$(expr $CURRDATE - $LASTRUN)
# If interval is more than the set one, then run the main script
if [ $INTERVAL -gt $RUN_EVERY ];
then
if [ -e $LOG_FILE ]; then
rm $LOG_FILE;
fi;
if [ ! -f $ZIPALIGNDB ]; then
touch $ZIPALIGNDB;
fi;
echo "Starting ZipAlign $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;
for DIR in /system/app /data/app /system/framework; do
cd $DIR;
for APK in *.apk; do
if [ $APK -ot $ZIPALIGNDB ] && [ $(grep "$DIR/$APK" $ZIPALIGNDB|wc -l) -gt 0 ]; then
echo "Already checked $DIR/$APK" | tee -a $LOG_FILE;
else
ZIPCHECK=`/system/xbin/zipalign -c -v 4 $APK | grep FAILED | wc -l`;
if [ $ZIPCHECK == "1" ]; then
echo "Now aligning $DIR/$APK" | tee -a $LOG_FILE;
/system/xbin/zipalign -v -f 4 $APK /data/local/$APK;
busybox mount -o rw,remount /system;
cp -f -p /data/local/$APK $APK;
chmod 644 $APK;
busybox rm -f /data/local/$APK;
grep "$DIR/$APK" $ZIPALIGNDB > /dev/null || echo $DIR/$APK >> $ZIPALIGNDB;
else
echo "Already aligned $DIR/$APK" | tee -a $LOG_FILE;
grep "$DIR/$APK" $ZIPALIGNDB > /dev/null || echo $DIR/$APK >> $ZIPALIGNDB;
fi;
fi;
done;
done;
busybox mount -o ro,remount /system;
touch $ZIPALIGNDB;
echo "ZipAlign finished at $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;
fi;
Hello, I'm new here so please excuse me if I post this in the wrong section.
I have a OnePlus 7t on Android 11 with Magisk installed.
I am trying to swap the R3 with Circle on my controller. In the keylayout file it shows that R3 is in fact Circle but doesn't work in games. ( Reverts to default controller mapping)
I have already edited and successfully changed the keylayout file for my PS4 Controller ( Vendor_054c_Product_09cc.kl ) by creating a magisk module since I'm on a stock Os and cant copy the .kl file over to system/usr/keylayouts . SEE BELOW
Code:
# Copyright (C) 2017 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Sony Playstation(R) DualShock 4 Controller
#
# Mapping according to https://developer.android.com/training/game-controllers/controller-input.html
# Square
key 0x130 BUTTON_X
# Cross
key 0x131 BUTTON_A
# Circle
key 0x132 BUTTON_THUMBR
# Triangle
key 0x133 BUTTON_Y
key 0x134 BUTTON_L1
key 0x135 BUTTON_R1
key 0x136 BUTTON_L2
key 0x137 BUTTON_R2
# L2 axis
axis 0x03 LTRIGGER
# R2 axis
axis 0x04 RTRIGGER
# Left Analog Stick
axis 0x00 X
axis 0x01 Y
# Right Analog Stick
axis 0x02 Z
axis 0x05 RZ
# Left stick click
key 0x13a BUTTON_THUMBL
# Right stick click
key 0x13b BUTTON_B
# Hat
axis 0x10 HAT_X
axis 0x11 HAT_Y
# Mapping according to https://www.kernel.org/doc/Documentation/input/gamepad.txt
# Share
key 0x138 BUTTON_SELECT
# Options
key 0x139 BUTTON_START
# PS key
key 0x13c BUTTON_MODE
# Touchpad press
# The touchpad for this joystick will become a separate input device in future releases
# and this button will be equivalent to left mouse button
# Therefore, map it to KEYCODE_BUTTON_1 here to allow apps to still handle this on earlier versions
key 0x13d BUTTON_1
I've made sure the permissions are set correctly as well as seen in the install.sh
Code:
##########################################################################################
#
# Magisk Module Installer Script
#
##########################################################################################
##########################################################################################
#
# Instructions:
#
# 1. Place your files into system folder (delete the placeholder file)
# 2. Fill in your module's info into module.prop
# 3. Configure and implement callbacks in this file
# 4. If you need boot scripts, add them into common/post-fs-data.sh or common/service.sh
# 5. Add your additional or modified system properties into common/system.prop
#
##########################################################################################
##########################################################################################
# Config Flags
##########################################################################################
# Set to true if you do *NOT* want Magisk to mount
# any files for you. Most modules would NOT want
# to set this flag to true
SKIPMOUNT=false
# Set to true if you need to load system.prop
PROPFILE=false
# Set to true if you need post-fs-data script
POSTFSDATA=false
# Set to true if you need late_start service script
LATESTARTSERVICE=false
##########################################################################################
# Replace list
##########################################################################################
# List all directories you want to directly replace in the system
# Check the documentations for more info why you would need this
# Construct your list in the following format
# This is an example
REPLACE_EXAMPLE="
/system/app/Youtube
/system/priv-app/SystemUI
/system/priv-app/Settings
/system/framework
"
# Construct your own list here
REPLACE="/system/usr/keylayout/Vendor_054c_Product_09cc.kl"
##########################################################################################
#
# Function Callbacks
#
# The following functions will be called by the installation framework.
# You do not have the ability to modify update-binary, the only way you can customize
# installation is through implementing these functions.
#
# When running your callbacks, the installation framework will make sure the Magisk
# internal busybox path is *PREPENDED* to PATH, so all common commands shall exist.
# Also, it will make sure /data, /system, and /vendor is properly mounted.
#
##########################################################################################
##########################################################################################
#
# The installation framework will export some variables and functions.
# You should use these variables and functions for installation.
#
# ! DO NOT use any Magisk internal paths as those are NOT public API.
# ! DO NOT use other functions in util_functions.sh as they are NOT public API.
# ! Non public APIs are not guranteed to maintain compatibility between releases.
#
# Available variables:
#
# MAGISK_VER (string): the version string of current installed Magisk
# MAGISK_VER_CODE (int): the version code of current installed Magisk
# BOOTMODE (bool): true if the module is currently installing in Magisk Manager
# MODPATH (path): the path where your module files should be installed
# TMPDIR (path): a place where you can temporarily store files
# ZIPFILE (path): your module's installation zip
# ARCH (string): the architecture of the device. Value is either arm, arm64, x86, or x64
# IS64BIT (bool): true if $ARCH is either arm64 or x64
# API (int): the API level (Android version) of the device
#
# Availible functions:
#
# ui_print <msg>
# print <msg> to console
# Avoid using 'echo' as it will not display in custom recovery's console
#
# abort <msg>
# print error message <msg> to console and terminate installation
# Avoid using 'exit' as it will skip the termination cleanup steps
#
# set_perm <target> <owner> <group> <permission> [context]
# if [context] is empty, it will default to "u:object_r:system_file:s0"
# this function is a shorthand for the following commands
# chown owner.group target
# chmod permission target
# chcon context target
#
# set_perm_recursive <directory> <owner> <group> <dirpermission> <filepermission> [context]
# if [context] is empty, it will default to "u:object_r:system_file:s0"
# for all files in <directory>, it will call:
# set_perm file owner group filepermission context
# for all directories in <directory> (including itself), it will call:
# set_perm dir owner group dirpermission context
#
##########################################################################################
##########################################################################################
# If you need boot scripts, DO NOT use general boot scripts (post-fs-data.d/service.d)
# ONLY use module scripts as it respects the module status (remove/disable) and is
# guaranteed to maintain the same behavior in future Magisk releases.
# Enable boot scripts by setting the flags in the config section above.
##########################################################################################
# Set what you want to display when installing your module
print_modname() {
ui_print "*******************************"
ui_print " Ps4 Controller Crouch Fix "
ui_print "*******************************"
}
# Copy/extract your module files into $MODPATH in on_install.
on_install() {
# The following is the default implementation: extract $ZIPFILE/system to $MODPATH
# Extend/change the logic to whatever you want
ui_print "- Extracting module files"
unzip -o "$ZIPFILE" 'system/*' -d $MODPATH >&2
ui_print "- deleting package cache"
rm -rf /data/system/package_cache/*
}
# Only some special files require specific permissions
# This function will be called after on_install is done
# The default permissions should be good enough for most cases
set_permissions() {
# The following is the default rule, DO NOT remove
set_perm_recursive $MODPATH 0 0 0755 0644
set_perm $MODPATH/system/usr/keylayout/Vendor_054c_Product_09cc.kl 0 0 0744
# Here are some examples:
# set_perm_recursive $MODPATH/system/lib 0 0 0755 0644
# set_perm $MODPATH/system/bin/app_process32 0 2000 0755 u:object_r:zygote_exec:s0
# set_perm $MODPATH/system/bin/dex2oat 0 2000 0755 u:object_r:dex2oat_exec:s0
# set_perm $MODPATH/system/lib/libart.so 0 0 0644
}
# You can add more functions to assist your custom script code
So basically everything seems to be correct but yet in games and gamepad tester the control functions as default ( R3 is not circle)
I've attached images showing im rooted and have the module succesfully installed and enabled, also showing the permissions of the .kl file in the keylayout folder.
Please help! and thank you in advance.