Remove unneded stuff:
* migt module does not exist
* persist.sys.miui_optimization property is used by MIUI only
* the following are not shipped for any device
- cnss_diag
- dc_cal
- displaycount
- energy-awareness
- ftcupdate
- hbtp_daemon
- init.panel_info.sh
- sec_nvm
- spdaemon
* vendor.audio.cit.spkcal.copy is used for calibration and we don't
need it
* all commented stuff
Change-Id: I2dd4b936f57b18fc96fda0faf5a3d128a3add764
Keep only copying of modem files because setting of printk and
qemu.hw.mainkeys is superfluous and msm_irqbalance we can start
automatically during late_start.
Change-Id: If8ef0cfd9fdd7447e7375cbccae6b1edf103d8f3
Remove unneeded script init.qcom.class_core.sh because there is
nothing for sdm710 and console service is started elsewhere.
Change-Id: I0fb02f632358092fdfd213a2affe15eb98c45e6f
Clean-up init.qcom.early_boot.sh so it just check (re)boot reason
and sets ro.vendor.alarm_boot appropriately. The rest of the script
can be removed as
* we don't want to override lcd_density
* setting of vblankoffdelay is being moved to init.qcom.rc
* chown/chmod of several sysfs knobs as well
* vendor.media.target.version and vendor.sys.media.target.version
properties are being set in vendor.prop
* service vendor.atfwd is started automatically
Change-Id: I7cc9ade191a3c3707f6cb534ba6d962d9193e07b
Move the rest of static configuration parameters from
init.qcom.post_boot.sh to init.qcom.power.rc.
Change-Id: I18d8aa7bdd4f2807246dafd9c47fc7fb9b65dc71
* /data/tombstones and /data/vendor/tombstones are both created by
the system's init.rc.
* Creating /tombstones at the root isn't allowed since the root is
mounted read-only.
Change-Id: I6c3a287056a2264d9e9ffe4557ecca8c6e03c0bb
Apart from useless battery capacity faking, all this does is to
start/stop data and radio services based upon the baseband type
of several QCOM targets. Since all the supported targets in this
common tree are of the same type, simply start all relevant services
unconditionally and get rid of one more shell script.
Change-Id: I1297b2537fcbea31d514bab5e248691cabdf523c
* Remove devfreq and cpuset parameters from init.qcom.post_boot.sh
as they are set in init.qcom.power.rc
* Remove powerkey input boost as our kernel does not support this
* Remove 'ondemand' governor sysfs items that do not exist as we
are using schedutil
Change-Id: I652fa62e3b600c4c9c0b5e9a5480ad017e27379e
* Remove code based on ro.config.low_ram property
* Simplify setting of ZRAM disk size as we always have 4GB or more
Change-Id: Ia9fb878f3f87fce9e13aa8c80a36638b841d1c50
* Remove code-paths for product names different from our ones
* Remode code that depends on ro.config.low_ram as we are not using
it and all our targets have 4GB or more RAM
* Remove enable_swap() that enables file based swap file
* Remove non-aarch64 code
Change-Id: I14dc70ed3acf18e96a8a884f0b0c344b0f6f5fa7
Remove all code-paths for targets different from 'sdm710' and
adjust indentation of sdm710 code-paths.
Change-Id: Ieaeebc6324c0310b3a0a5d36c5883f00e4042acc
We do not have AdrenoTest.apk or SWE_Browser.apk so it does not make
sense to try to install them.
Change-Id: I0615e2e50526f960d5a6c221798ab5ebd1162d7b
from: device_google_bonito commit e02e4813256e51bacdecb
- fstab: use fsync_mode=nobarrier
This patch proposes to skip FLUSH commands for UFS when fsync(2) for non-atomic
files is called.
== Pros ==
- huge gain on random write/fsync test from 30MB/s to 90MB/s
(e.g., Androbench)
- extented flash lifetime
(FLUSH command requires for FTL to write its metadata)
== Cons ==
In terms of stability,
1) checkpoint issues FLUSH, so this doesn't hurt F2FS consistency.
2) atomic write issues FLUSH, so SQLite w/ journal mode would be safe.
3) non-atomic fsync() doesn't issue FLUSH, so there is one scenario to consider
where:
a. fsync() flushes data blocks to disk, and then node blocks. The last node
block contains a flag as the candidate for roll-forward recovery.
b. assuming that storage is able to flush disk cache in out-of-order manner,
all the cached node blocks are written to the flash cell, followed by all
the data blocks.
c. cut power
d. F2FS conducts roll-back to the last checkpoint w/o risk. Then, it starts
roll-forward recovery which traverses the node block chain and finds node
blocks written by b. lastly.
e. After mount, user can see old or zero data from the recovered node blocks.
Three points persuaded me to go with this:
1) In the above scenario, it won't hurt filesystem consistency.
2) Generally, firmware in embedded UFS/eMMC doesn't do out-of-order writes,
since it doesn't have large cache to reorder write IOs likewise SSDs.
3) It'd be okay to lose the last-called fsync() due to power-cut, since users
won't be aware of it mostly.
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Change-Id: I6d0fee62c081d55b462371412f390861f5f73a68
* The discard on ext4 of kernel 4.9 is not perfect, it will greatly
reduce the speed when deleting a large number of random small files,
especially eMMC devices (such as sirius)
* f2fs discard is enabled by default, so it's useless to leave it here
This reverts commit bec522caca.
Change-Id: I35d6f7b26005ff9235c6d0644dd96dd6bf038e69
Eliminate drmdiagapp entries in init scripts. This app was deprecated
hence these entries were causing boot time degradation.
Change-Id: Ia8b14ef200a17b37c393f3e62c7be8849d575c71
Remove logdumpd service that cannot be and should not be used
as we are using logdump partition for metadata.
Change-Id: I4f058dc6482a5ce8133d87e2eb10667ad483b28f
* focaltech_touch_mi used in pyxis exposes fod_status sysfs node
in /sys/touchpanel
Signed-off-by: Ivan Vecera <ivan@cera.cz>
Change-Id: I9707e1837c41b0cbc3f03180774af1b53c4b2f6d
* Add entry for SD card as Pyxis unlike Grus supports it
Signed-off-by: Ivan Vecera <ivan@cera.cz>
Change-Id: Ia4aa49b4ea4b0d632ec56ba48a4a2882fdcc2563
* Make your bet, is it mount persist command or fs classes triggers that kills AOSP off mode charging? :xiaomi:
Change-Id: I608316b928b63e37ec82a2d160a316a606b3365e
