* Bypasses the literally infinite timeout for users who have
limited access to GitHub (before: 2m13.749s, after: 0m14.354s)
* The timeouts should be enough for users who have freedom internet
access, even ADSL network connection shouldn't take that long...
Test:
1. Execute `source build/envsetup.sh`
2. `breakfast` a existing device
3. Add "0.0.0.1 github.com" and "0.0.0.1 raw.githubusercontent.com"
to /etc/hosts
4. `breakfast` any device, observe that it should not take up to
minutes to quit
Change-Id: Ib90e69c75a50e66b47e6245cb6d0521351b5c71b
Some OEMs (for example: oplus) push their dtbs to their own folders which causes kernel build to error out, fix this by including non qcom dtbs as well.
Change-Id: I2f51db103475cd2609cd061e0ec66af5accb96ab
Safe Volume has many false alarms. And if overridden by the user, at
every 20 hours of accumulated(!) audio playback it will intentionally
reset - even while the audio is playing. This can ruin the listening
experience, and ironically pose a safety hazard when e.g. the user is
operating a vehicle...
AOSP already opted out of Safe Volume in the overlays for Mobile Country
Code 310-316 (= US). Make this universal.
Change-Id: Iadb3a16d0f4a2b458164fa5c805ec1b448da559b
Reviewed-on: https://review.statixos.com/c/android_vendor_statix/+/4483
Reviewed-by: Anay Wadhera <awadhera@berkeley.edu>
Reviewed-by: Sourajit Karmakar <sourajit@live.com>
Reviewed-by: Filippo Roggi <zzkw35@gmail.com>
Tested-by: Filippo Roggi <zzkw35@gmail.com>
This can happen when an out of tree module target uses a matching module
name from the base kernel. This causes two problems:
1) Depmod gets confused and only pulls symbols from one of the modules
2) Copying the modules to modules_out is not entirely deterministic and
is based on the first variant to be returned by find, meaning that
the variant that gets copied to the device could change build to
build.
To avoid these issues, fail the build if this happens and force the
build target to only generate one copy of each module name.
Change-Id: I2e47ba4e142054feabaa1ab80fbbe0332fd84a62
* When the boot image is modified, recovery updating fails because the patch no longer applies to the modified boot image, so ship a full recovery image instead of a patch so recovery updating always works.
Signed-off-by: Jarl-Penguin <jarlpenguin@outlook.com>
Change-Id: I56cf6c4d301afa88b39b31d488c5166903406637
- Selectively merge changes from com.google.android.dialer version
127.0.620688474-downloadable
- Remove obvious attempts to limit user freedom by forcing users to use
carrier VVM app for Cellcom and Metro by T-Mobile.
Change-Id: I72bc29e4db5382f02508669c1cdc65812f1fbb13
Reserving 8MB does not guarantee that free blocks will be >= 1%, so not
only this doesn't work properly, but also breaks builds for some
devices.
This reverts commit 3940fb4240.
Test: breakfast kebab && WITH_GMS=true m
Change-Id: I330570dc6fc9efca5629358a0b149f131d36ba18
This reverts commit bc8d7739ac.
Reason for revert: no longer needed when using blobs that match tag
DISPLAY.LA.3.0.r1-10700-KAILUA.0.
Change-Id: Ia89ce566a4cade6091a2dc6bc4e8b56ef7d1f73b
* When we remount partitions via `adb remount`, a scratch partition
is made for overlayfs to use - this takes up space and breaks OTA.
The end user /could/ run this to fix it:
`adb reboot fastboot && fastboot delete-logical-partition scratch && fastboot reboot`
But that's bad UX, remount should work. This ensures that with or without GMS,
we reserve some space on all dynamic partitions.
* Set amount to `8 * 1024 * 1024` + 1 for good measure.
* Don't reserve this amount of `-user` builds as we don't remount
there.
Change-Id: I969aea92747a17ceca299e109c6e0ab563951374
This was set to true by default prior to U QPR2.
Test: Open settings and notice that dual pane layout is back
Change-Id: Ide44ecbe7e30d6bf26d9c9358e46c71b35c66250
Build is now a group instead of a repo.
The actual repo got renamed to build_repo.
Change-Id: I61f65251896d18c3025d849109206d44e2686c70
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
