* Allow both IPv4 and IPv6 protocols for data and mms
* Provide an apn name for the initial attach profile
With respect to initial attach, it seems at least the qcom ril blobs
on my device require the apn field to be set. The following error is
produced and data will not connect on boot unless radio resets (e.g.
airplane mode toggle) so that the default APN is used.
E RILQ : (0/231): RIL[0][cmd-111(680)] qcril_data_request_set_lte_attach_profile: ril_apn (provided NULL) is mandatory param for looking up profile.
E RILQ : (0/231): RIL[0][cmd-111(680)] qcril_data_request_set_lte_attach_profile: EXIT with FAILURE
E RILQ : (0/231): RIL[0][cmd-111(680)] qcril_qmi_nas_set_initial_attach_apn: Data RIL call for Attach APN failed with Error code 2
Change-Id: Ie983474780a7443c870911994234ea2f2025de12
We now use a temporary context when mounting /data, so add permissions
to do that, and add permissions necessary to do the recursive wipe.
Change-Id: Ic925c70f1cf01c8b19a6ac48a9468d6eb9205321
AdrianDC also in the crew now while Marcelo doesn't have the device anymore.
This patch was requested by AdrianDC.
Change-Id: I57a27655537d96c7f5dc33f33d8e7d7e3982d6db
Also allow apps to read the contents of mounted OBBs.
See AOSP Change-Id: I66df236eade3ca25a10749dd43d173ff4628cfad
and Change-Id: I49b722b24c1c7d9ab084ebee7c1e349d8d660ffa
Change-Id: I757a2a8831c69d41c0496025a39eaf79ceb0e65f
Maven APK (Why are these in maven anyways?) will crash due to it not
needing to generate a jack file. This wasn't noticed before as brunch
succeeded, however, doing an mmm on one will cause this to fail. This
adds in logic to not generate a jack file for an apk in maven.
Change-Id: I44036bfd51ae3edd9437b153898b419ffc6ba2d6
Prebuilts weren't generating their .jack file when doing an mm or mmm
but would work with a brunch or full make. This makes it so mmm/mm
will properly generate it.
Change-Id: If5ccd1b557ef124b3c57fa09b172ec11caff886e
There are two T-Mobile CZ APNs which specify the MMS proxy as http
proxy (which doesn't work). Get rid of them, there are correct APNs
available. Also remove duplicate IMS and wrong MMS APN.
Remove two wrong and one deprecated Vodafone CZ APNs. The separate
'ointernet' APN for prepaid cards has been deprecated since 2010.
Change-Id: Idf8e7c8df7bb843cdfafe7dbce710d09aa47eda1
Noverca is out of business, so the APN is unneeded. Vodafone IT
has duplicate entries and the type of APN associated to web.omnitel.it
is wrong, so fix it.
Change-Id: I4ddc0dbc13d44f8dc8ef2bc307496155230e720c
'COOPVOCE' is the same as 'WEB COOP', except for mvno_type and
mvno_match_data, so get rid of it.
'Unefon' uses the exact same APN of 'Iusacell', so duplicate the
entries and assign the right mvno_type and mvno_match_data.
Change-Id: Ibae12b3c179528ccd115849929995c79fa91ed0f
Now allows you to specify a target module to be
compiled prior to publish via LOCAL_MAVEN_TARGET_MODULE.
This utilizes the definition for intermediates-dir-for on
the target module after it sets an explicit dependency from
remote to local module.
Change-Id: I65b5e07fdcc3368e350b1935ccca381b74dce59e
Shells based on busybox, such as found in CM 12.1 recovery and TWRP, do not
properly handle pattern based parameter expansion for variables longer than
4kb. This throws our naive little XML parser into an infinite loop. Since
all such lines are associated with external app certs, just skip them.
Change-Id: I203b65c1ffd62bf3261b3ae315327314a5006952
After assimilating minivold into /sbin/recovery, we need to allow the
minivold service (a symlink to the recovery binary) to transition from
the recovery to the vold domain.
Change-Id: I112e6d371a8da8fc55a06967852c869105190616
Setup wizard asks for wifi password, location sharing and if you want share usage data with CyanogenMod. Only the locale setting would be needed by Replicant. Either it has to be switched to a general setup wizard or this one has to be customized heavily (also the graphics need to be replaced with Replicant ones)
It seems that F-Droid needs this setting enabled again on Android 6
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
This matches the policy for fsck.f2fs, although it still needs to run
as fsck_untrusted for public volumes
Change-Id: Ia04e7f8902e53a9926a87f0c99e603611cc39c5d
