| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I0512a0f7a089b748c199f1a8933c6323cda86a1e
|
|
|
|
|
|
|
|
|
| |
Apps and database file sizes have increased in recent Android versions,
which makes it practical to increase our read-ahead value from 128 kb.
General user experience seem to have improved a bit.
Change-Id: I35788444a8552a8f376c699ead163e951ed06b30
|
|
|
|
|
|
|
|
| |
References:
https://source.android.com/devices/tech/config/low-ram.html
https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1
Change-Id: I8ec35dad3a65c213d1843d01957b308c3ab84a6e
|
|
|
|
|
|
|
| |
With the lz4-backed zRAM we're using, it seems like we can use larger
values without noticeable slowdowns.
Change-Id: I6a7921d0741c6b54629b456cc5387407956d98d8
|
|
|
|
| |
Change-Id: I84f26a40e5b89d100b5a1fd2eab1ba59e5957750
|
|
|
|
| |
Change-Id: I2a758e866c4518a1cbbd360bd3a06f3d922161f5
|
|
|
|
|
|
|
| |
These are not built since Android 4.1 by Google.
However, since switching to hardware/ti/omap4, they get built again, just to start and crash.
Change-Id: Ia729d01a3e9bf77b5e21d6acea09eb5ffdcff591
|
|
|
|
| |
Change-Id: I0509465046ae5b22f4ab1e857db0645075d66628
|
|
|
|
| |
Change-Id: I4fbbc086e0f01001cecd764b7a726787bb41a4dc
|
|
|
|
|
|
|
| |
This eliminates the inital 60 second blocking in the kernel while trying to load firmwares.
It also makes adb avaliable, which can be handy in some situations.
Change-Id: I4c8a64aafbcdc07b6cc206dda001af5ed1aad48d
|
|
|
| |
Change-Id: I503112a3d892b489abb89520292fab9826e2bd8c
|
| |
|
|
|
|
|
|
|
| |
Conflicts:
rootdir/init.tuna.rc
Change-Id: I27575da0e3b0884ba75b0beef59cdb08e2900f03
|
|
|
|
|
|
| |
This replaces fRom, which was a proprietary non-pie executable.
Change-Id: I04bed63542f02400059968e012641c14e1a28293
|
| |
|
| |
|
|
|
|
| |
Change-Id: I2483138a786934f65eb3f17723d8be813942e166
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Adaptive backlight
- Color and gamma calibration
- LTO
- Vibrator control
Also switched to cyanogenmod_tuna_defconfig,
since these features require non-stock kernel configs.
Change-Id: I5d5b0999c91690eb4c46ce33b6040bc52c0d9cb9
|
|
|
|
| |
Binary is non-pie.
|
| |
|
| |
|
|
|
|
|
|
| |
Recent changes have obsoleted the need to call
restorecon on any of /data files and dirs. This
patch drops those restorecons from the file.
|
| |
|
|
|
|
| |
From Android 5.0, these are present in the main init.rc file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, we do the following sequence on every bootup:
1. mount /factory ro (fstab)
2. remount /factory as rw
3. update selinux labels on the partition
4. remount /factory as ro
By mounting /factory in rw mode from the fstab, we can avoid the second step,
simplifying the bootup sequence.
Also replaced the restorecons with one restorecon_recursive,
which does the same task in one line.
And lastly, removed some unnecessary chown/chmods - remounting
does not overwrite the permissions and the owner.
|
|
|
|
|
|
|
|
| |
Otherwise on toro you get:
D/TelephonyManager( 131): No /proc/cmdline exception=java.io.FileNotFoundException:
/proc/cmdline: open failed: EACCES (Permission denied)
Change-Id: I2685959d485be3e29a738bc6287fdd99dc52b771
|
|
|
|
|
|
|
|
|
|
| |
HUGE thank you to @stargo for figuring this out.
Conflicts:
device.mk
rootdir/init.tuna.rc
Change-Id: I88c9c8f63a85b533bfbb459b2042aedda90ac0d8
|
|
|
|
|
|
|
| |
Change-Id: Iff82f5be1b25c4806e842319fb5b333d9a8223a0
Conflicts:
device.mk
|
|
|
|
|
|
| |
Tested with ntfs and worked great.
Change-Id: I18d562db32738274d9b472305b8d6ada6f2af60f
|
|
Change-Id: I6341fd2da5941d6e6861c499aa65656b1fcd2d65
|