{"shas":[["cc45a6dc068d343137415b57f6545231c8282be3","cee1112a4be735590b9eb368e0011db397f99f43@zenthought.org","Don't drop the drawable cache completely on configuration change\n\nThere was a lot of fancy code just above the clear to ensure\nthat drawables that aren't affected by the change are kept,\nthen the entire array was cleared.  This patch removes the\nclear, so that the drawables that haven't changed are really\nkept, matching the logs, comments and larger part of the code.\n\nThis patch also fixes the various constant states to return\ncorrect ChangingConfigurations.\n\nChange-Id: Ic11f6179537318d3de16dc58286989eb62a07f15\nOld-Change-Id: I22495e6ed232dfe056207ce5155405af1fa82428","Christopher Lais"],["d48995a48bb5f6ca6fe50b4b9ec8877155637af3","5c89f952786ec530a5a3e9788b1ce5b1f86195f2@gmail.com","Added a separate reboot recovery icon for the Global Actions dialog\n\nChange-Id: I7041eaf9340578c3a9cd86a42d9b4a3aa5f10ce3","Austen Dicken"],["b58e5ae98ba80cdf7be6ec4e3df1b43d21d771cc","7f235e6976b4a59617dc0fd2e298ebc8d7025a24@gmail.com","Asset redirections are now managed by a system service.\n\nAdjusted the asset redirection design to use a common system service\n(AssetRedirectionManagerService) for synchronization and cache\nmanagement.  This replaces the old /data/res-cache design completely\n(nothing is written to disk now).\n\nThis change also moves a large amount of code from the C++ layer to Java\nfor parsing the theme meta data and redirection XML files, though the\nactual redirection still occurs at the native layer.\n\nChange-Id: I8820e39425135269f5e723534c4b9c8dc6841779","Josh Guilfoyle"],["a6d290691188c118058ee6192565751481eb3508","521f5b4a9cea91e07c4c33ce864192bce066505d@T-Mobile.com","Properly refresh cached drawables on theme change.\n\nNow that the resources drawable cache is not wiped on every config\nchange we need to be sure that theme change triggers a wipe.\n\nChange-Id: I6622dcfb2551618f3c7b48ee6496930095e8ce9f","Josh Guilfoyle"],["7d8b1bbb118cdb71c16c97dbc73390d9351c238c","521f5b4a9cea91e07c4c33ce864192bce066505d@T-Mobile.com","Fixed a regression causing theme switch to fail.\n\nThis would only occur when switching from one theme APK to another,\nwhich apparently was not tested on the experimental branch (??).  The\nbug would not repro if switching between system default and a theme APK.\n\nChange-Id: I9fc0b5c50c1dff4a0b2d548980977faaa0a51167","Josh Guilfoyle"],["3dc4cedd443ed5dbb6d25df2fbf5c6c64f29b997","521f5b4a9cea91e07c4c33ce864192bce066505d@T-Mobile.com","Improved \"assetredirection\" dumpsys output.\n\nAs a convenience, the dump output now performs conversions from resource\nidentifiers to the fully qualified resource name (package:type/entry).\n\nChange-Id: I87cd5cbf75f5c8ec6c600c5cb977afca22f92538","Josh Guilfoyle"],["0a0566834607facdbae3f6c28727b0d387463b01","7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","Revert \"Merge \"Don't drop the drawable cache completely on configuration change\" into gingerbread\"\n\nThis reverts commit 7314c3690e35d6fb7a1905958ce48ea08e319e4c, reversing\nchanges made to 87b6d2db50f8a517595e42094df36cf099f96cf0.","Steve Kondik"],["433de557b0ed9e30599f86572b4ea8b8ee0908a8","2a8ffc07e8f57d80a2934ccc3dd1949354d82b2d@googlemail.com","Canvas.drawVertices: correct color range-check\n\nThe range-check in drawVertices previously checked that the color\ncount was equal to the vertex count. However, the vertex count is\nspecified in array elements, and there's two array elements per\nvertex for the positions, but only one array element per vertex\nfor the colors.\n\nCorrect the code so the check is consistent with the element count.\n\nChange-Id: Id043f1003f9245f18adc91bac49dc33727ca765e","Erik Faye-Lund"],["d7cf9c65cd37c60b855ab5f97ffac7e153dec89a","292887e14ab3ac1a8c5241e4b7e800905a1e03d4@sonyericsson.com","Fixed problem with proxy server sometimes responds with 400 Bad Request when trying\nto connect to a site using https.\n\nThe CONNECT to the server lacks the 'host' header which is mandatory according to the\nspecification. Some proxy servers are strictly following the specification and sends\nback the 400 Bad Requst error code.","Henrik Baard"],["84a478f428249eb2214be12f7fcede5af0f5c008","a36874480cb10f6a6616c85e950c2ec8d750b255@ti.com","Bluetooth:LCD wakeup during remote BT pairing request.\nThis change fixes the issue of LCD not coming up during remote\ninitiated pairing request when android is in suspend\n\nChange-Id: I658954857584ae1a4737261b1ae1749f4d0a7998\nSigned-off-by: Bheemsen Kulkarni <x0099674@ti.com>","Bheemsen Kulkarni"],["5c5c03462fe3ab1a7746157a0169ef60cf3eef8c","d46c311a75d57946b0bb8d04f44534a10b599c04@sonyericsson.com","Fix incorrect calculation of start and end indices of changed text\n\n- The problem is taht the calculation of indices does not take the\n  difference in original and modified text lengths into account.\n- If reportExtractedText() is called from the onDraw() function,\n  mInputMethodState is not reset.\n\nThe error can occur when the user is editing formatted text using a full screen editor.\nOne example of formatted text is phone numbers (e.g. dashes are added to North American\nnumbers by the PhoneNumberFormattingTextWatcher class).\nIf the two first digits are removed from the number 555-666-777, the new number becomes 566--777.\nThis is due incorrect calculation of start and end indices of the changed text. The error is in\nthe TextView class and the problem is that the calculation does not take the difference in original\nand modified text lengths into account.\n\nChange-Id: If12d0f571873a6f1874102377432affb64ee21e8","Viktor Yakovel"],["4322ec004748087aa37edbe7689ae42ee5aed50a","1f919e53c294adb672cacd7bf9d73c131aafbbb0@gmail.com","Should accept \"application/vnd.wap.multipart.alternative\" message.\n\nUnfortunately, PduParser does not allow application/vnd.wap.multipart.alternative as M-RETRIEVE.CONF but some Mobile carrier send message with this type.\nThis patch allows that and take the first part of multipart as message body.\n\nIt fixes http://code.google.com/p/android/issues/detail?id=8957\n\nChange-Id: Ic93259c91331d1e67100439114b7c4f43a834368","takuo"],["361d32a2c941d4b12333a5bbc53c02e3ae3a5ff7","1fbfd099b57f3c51d7b129902e7cedd97d92f832@gmail.com","replaced deprecated getIntent with parseURI\n\nChange-Id: Ice9e74fd8f729d7efad934d2de4c747d73be562e","Christian Mehlmauer"],["dba0a3480f09c32ed2524ce58b1cb060156e2255","100b614fecbc19893e09c99549592cc8ae9f24cf@sonyericsson.com","Corrected SPN and PLMN name handling\n\nSPDI-file on SIM and BCD encoded PLMN-entries wasn't parsed correctly\ncausing us to display wrong networknames.\n\nChange-Id: I09d80deec45b4b3ad525a9359b4866de7549e39e","Fredrik Jagenheim"],["b9543d70bbb1a39a56ae997b469487c009b920f0","77ae32e3a64dac569a3f8f44781b05c0188f7358@sonyericsson.com","Fix data type of RIL_UNSOL_RESPONSE_NEW_BROADCAST_SMS in RIL.\n\nFixing incorrect data type of RIL_UNSOL_RESPONSE_NEW_BROADCAST_SMS\nin Android RIL.\n\nThe Android RIL specifies that the unsolicited response signal\nRIL_UNSOL_RESPONSE_NEW_BROADCAST_SMS should contain a raw byte\narray (ril.h). However, in the implementation of the Java RIL and\nthe C++ RIL daemon, the data is unpacked as a string. This causes\ndata delivered from the network stack to be garbled.\n\nChanging so that both the C++ RIL deamon in platform/hardware/ril\nand the Java RIL in frameworks/base follows the specification.\n\nChange-Id: I9b9b26d16cd39422c43d9fa7aadfcff3e60c78ae","Henrik Hall"],["ae17b739df95baa73e1d47bc4c69966a274a82ec","48dc0ccae71fd4b2b804edce215c2e98388445d5@gmail.com","Fix the ssid display issue\n\nReproduce steps:\n1. Set a special AP name that contains \"=\" (looks like \"-=^-^=-\");\n2. Connect to this AP;\n3. The display of ssid will be incorrect;\n\nChange-Id: Idc7433a42cf59932f5fb147f5500e0175f745399","Kenny"],["ef6341dc469d1ddb738193ddca2c96ba4657c166","c9304087bbc0787b2323d16315dac583f7b846cd@sonyericsson.com","Change in media scanner to set correct date\n\nWhen the media scanner scanned a single file, the modified\ndate (DATE_MODIFIED) was not correctly set in the content\nprovider. It was set as milliseconds but should have been\nset as seconds. This caused downloaded media items to display\nwrongly in the camera album, since the date was wrong.\n\nChange-Id: I24cd92215c26f579eb33a4a3890f96c6ef9ec8c0","Mikael2 Svensson"],["10bc7e5cf2db8e0c28d62768076e516336b2e5d6","5f927b3b58ac050f8f37f6cfc59ff541d4681cd8@gmail.com","fillWindow's start position must be smaller than getCount value\n\nChange-Id: I3664ae8f6172f02bf6e2472320e79e3bf8683cc0","Tatsuo Nagamatsu"],["bfb9bdb797420189e824a70b07863d6adea17011","ba9385f009973727ee5a11522e9bc44628a9e8df@sonyericsson.com","Support custom themes with AlertDialog.Builder\n\nAdd a constructor to AlertDialog.Builder with a 'theme' parameter so\nthat e.g. the buttons in a dialog built with AlertDialog.Builder can\nbe themed.\n\nChange-Id: Ie1b1c9706ad2146c8b64dd91fe249c6855c6ac65","Martin Nordholts"],["7d975a41c6c7cc87937165f7a7dcbe4028669275","5fba59cc7ca3bf88e26a6b6b54fab2014e9027ef@gmail.com","Fixing counting the number of days in call log screen.\n\nCounting the number of days in call log screen when a\ncall was made/received within a week is not correct.\n\nIssue 3132: Call Log Reporting Wrong\n\nChange-Id: I99c3cb40267b4b5938ccc4225993b7aac7e2d018\nSigned-off-by: David Sobreira Marques <dpsmarques@gmail.com>","David Sobreira Marques"]],"repo":"thiasB/android_frameworks_base","actor":"thiasB","ref":"refs/heads/gingerbread","size":83,"head":"83e8eb891476c4d7efa172a43ad709a694b3478a","actor_gravatar":"eafb85ce9878240127ec2d8110607b66","push_id":23536375}