This forces set UA string to Nexus5 for SoftBank MCC:440 MCN:20.
Tested send/receive & confirmed working by yours truly.
Change-Id: I1831c329eb38507a957111052bb5f56350c49361
In theory, could have been a good idea, but ultimately just leads to
headaches for device maintainers that need to overlay any of these.
Revert "overlay: remove Verizon specific eri.xml"
This reverts commit 5f92da62c6.
Revert "Add Japanese APNs/eri for au, docomo MVNO, EMOBILE and SoftBank"
This reverts commit eeeb0888d4.
Revert "Add apns/eri for Boost Mobile"
This reverts commit b207e2eda3.
Revert "add more vzw eri's"
This reverts commit 82e10af192.
Revert "multi-carrier overlays: Add eri and config for US Cellular"
This reverts commit 1af75f1ba7.
Revert "Multi-carrier overlays: Fix Mms"
This reverts commit f8b0737a43.
Revert "Generic multi-carrier overlays based on hammerhead"
This reverts commit 6f5758c9c3.
Change-Id: I3495a89ce405362dc558f7ec7f0e61adea9fa507
Restore order to the universe by removing that which is evil.
For some strange reason, Verizon devices do not agree on the eri.xml to
use, even on the same spn. Since it is not universal, it does not belong
in vendor/cm (at least while there is no automatic method to check which
eri.xml should be used). Remove these so that we don't end up with
strange double-overlay issues for devices.
Change-Id: If5a28ed03c8cc6b145c151c7ebf95fabdf81f434
Companion change to I8a648014873319ea0d0f1089495d6777b8a1b8bf,
config_mms_user_agent_profile_url can't be empty either
Change-Id: Ib6b34972439818da47c389377664e75263dfd21b
The default user-agent isn't set, which makes
TelephonyManager.getMmsUserAgent() return an empty string when a
device doesn't have one in its own overlays. Every hardware should
set its own unique name for this, but add a default value for cases
in which is is forgotten.
Fixes android.telephony.cts.TelephonyManagerTest#testTelephonyManager
Change-Id: I8a648014873319ea0d0f1089495d6777b8a1b8bf
Add a separate list of default lockscreen unlock targets for devices
without voice capability.
http://review.cyanogenmod.org/#/c/52966/1
Change-Id: Ifbb066faade39b1cd98a6d1bfb7b5021eb51ab95
This reverts commit ea14a88a2a.
Using the Package Manager prevents any danling wakelock from
killed service/receiver.
Change-Id: Ie3162ca4b18a7bc9c55613af39e88ea980407e5f
Dictionary files have been moved to a new name format.
Dictionary files can also have a new JellyBean format that
can provide next word suggestions.
Updated dictionaries used where available.
Squashed commit from: http://review.cyanogenmod.com/#/c/19404/
Fix Issue 5781: Danish keyboard crashes
The process libjni_latin.so crashes because the danish dictionary has a corrupted line that
exceeds the maximum word defined in native defines.h (#define MAX_WORD_LENGTH_INTERNAL 48) and
the BinaryDictionary (MAX_WORD_LENGTH = 48).
Also, the hebrew dictionary has inconsistent lines (http directions, english words, numbers,
dates, ...), and more of the them exceeds the 48 chars by word limit. I found an hebrew
dictionary in http://softkeyboard.googlecode.com/svn/trunk/DictionaryTools/xml/he.xml that looks
ok.
Change-Id: I33f88d672707388e76db656632b00b8e370f957a
In CM, this is a user-configurable setting, and that setting doesn't
work unless the default is disabled
Change-Id: I2f009a48d1d730c804cb0887f445b5ef54ea738e
In ICS the binary dictionary format for dictionaries
has changed. I decompiled them all to xml and then
recompiled with ICS makedict. They will still not be
considered installed however. I have confirmed the
files work by messing with LatinImeDictionaryPack.apk
though, a part of the gapps.
I'm just submitting this in the hope that someone
else will also try to figure it out.
It also decreases the size of LatinIME.apk slightly
as the new format results in greater compression.
Change-Id: Ia4d1305bf64e6529cd90b44aa9af39dcefae1282
Since CyanogenMod has the "trebuchet" preferences shortcut in Settings,
we can remove it from the main menu. This is a config to show that we
are running cm.
Change-Id: I3e749a5774b6ec87734913544d5c24fbb2cc65de
This is currently done for each individual device that uses bcm fm,
but the overlay should be the same for all bcm devices.
Change-Id: Iba2f99d8fe2bdc9bac438b463cf7a4a088ee35ea
Introduces a new Ring style - 2 rings on left/right to unlock/silence.
1 ring in the middle to launch up to 4 custom apps.
Rings can be dragged anywhere on lockscreen - not just in one direction.
Unlock/silence rings are triggered by dragging the ring far enough away from its neutral posi$
Custom apps are triggered by releasing the middle ring while over the app icon.
Demo video: http://www.youtube.com/watch?v=VnQzT9QyJFQ
Change-Id: I7cbc02de5eb23f786bc7419d3506e2f2bc7d1819
After searching, testing and compiling nearly two days I finally
found a way arround that issue.
(http://code.google.com/p/cyanogenmod/issues/detail?id=3587)
I used the mdpi images and only changed the height and the
nine-patch-bars, but not the width.
That seems to do the trick and all buttons look good as
far as I can see on my wildfire.
Packed the images to the overlay instead of editing the theme.
Please test on your ldpi devices, especially with apps
that use buttons with default style.
Change-Id: Ic48c6c44d23d0e6c8a6c3822f17fda653796ea62
