| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Normally this kind of nasty hack could go into libaudio, but on this
particular device, we have no access to the source code of libaudio.
Put the nasty hack into audioflinger and wrap it in ifdefs.
Change-Id: I5e3e495e3bd6b671823967b61ba5ceb49e59a401
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | | |
Change-Id: I97c6dcd0cad3bca0741b1772edec82596633b77b
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
Change-Id: Idfdcf8ac657669b75c5a6219c2f91d20963bbe5b
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
- added 'none' to xml attributes for 'orientation' -
- Updated GestureOverlayView to allow an orientation of 'none.
This allows the lockscreen to recognize gestures in any direction,
and of any complexity.
|
| |
| |
| |
| |
| |
| |
| |
| | |
- User can now define unlock and sound toggle gestures.
- Lockscreen tabs can now be fully disabled, but ONLY if there is
some other method of unlocking the device enabled. This includes:
Trackball unlock, menu key unlock, and gesture unlock.
- Changed default gesture sensitivity to 3
|
|/
|
|
|
|
| |
the lockscreen messaging slider.
Change-Id: I56869f893573ff5b040b6343f531ee555c512c79
|
| |
|
|
|
|
| |
Change-Id: I4a73849fd5b0a3a24c113c2fd6c45636927febfc
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
System settings component.
Adds settings for gestures active, traces active, sensitivity.
Adds gesture overlay to lockscreen layouts.
Depends on change 540 and 565
|
|/
|
|
|
|
|
|
| |
Allow the overlay object to be destroyed whenever the destroy is
invoked. Currently the destroy call returns if there is an error
encountered, which results in open data and control channels.
Change-Id: I1f2ef4ebb5fb1dcabf05ab50b5bbf6e5e240a63a
|
|
|
|
| |
Change-Id: I18eaab33ea94efa0efff88350f137072b4841d92
|
|\
| |
| |
| | |
bc097e94dfd15ecaac4d057d30c68d9c77a54744 switchable." into froyo
|
| |
| |
| |
| |
| |
| | |
bc097e94dfd15ecaac4d057d30c68d9c77a54744 switchable.
Change-Id: I66c5e5bcda6b0bfa42dbdbcce6bca34abd880182
|
| |
| |
| |
| | |
Change-Id: Iec8448c86ee60c5dafae5ec0c403a0c595339388
|
|\ \
| |/
|/|
| | |
but subsequently erased by Ib6a7e284" into froyo
|
| |
| |
| |
| |
| |
| | |
2nd try: already merged (I255359ba) but subsequently erased by Ib6a7e284
Change-Id: I21376f4c423d2b567a288db03cfb09c95d452eba
|
|/
|
|
|
|
| |
SIM Card. This fixes the roaming problem with some virtual network providers, since some of them have an empty string (check with getprop gsm.sim.operator.alpha). For sure no provider will write empty in their SIM cards. Data roaming can be disabled after that. Roaming in foreign countrys will still work since it checks the MCC (Mobile Country Code). Thanks to my friend Sewi for helping me finding this. :)"
This reverts commit bc097e94dfd15ecaac4d057d30c68d9c77a54744.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libloc_api starts a thread as soon as the GPS is initialized, at
which time the xtra callback is also cleared. If libloc_api gets
a request for xtra data from the gps before the xtra callback has
been set, it gets silently ignored, and never requests the data
again. Since there is no method to see if data has been requested
in the interface, we must assume that data has been requested.
This would be better fixed in libloc_api by queuing the request
until gps-xtra is initialized, but libloc_api is still proprietary
for current devices.
This reverts part of commit 88606634d1fa0c6245f9b4c0c1bbe67842eab16f.
The typo fix was not reverted.
Change-Id: I99a50dd64ff588d379dafb2974dd8d6b9229b6c6
|
|\
| |
| |
| | |
list" into froyo
|
| |
| |
| |
| |
| |
| | |
In other words... No scrollbars, no overscroll for you.
Change-Id: I28bcd11151c323091d6447643341a7330dc913db
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The G2's keyboard lacks a number of special characters:
` ^ [ ] { } \ | < >
Some of these are handled by the character picker that pops up when
pressing alt-sym (alt and the space bar) but not all. This change adds
the last few missing characters so it is now possible to access the full
qwerty character set when using the physical keyboard.
I am only familiar with the G1/G2 phones so I do not know what
characters other phones may be lacking. Long term it may be useful to
make this character picker customizable for each phone model. For now
this trivial patch is sufficient to make me happy.
Change-Id: I8d1592ae6731620c1eeacfce39fbae8443db6884
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| | |
* Phone and Messaging label
Change-Id: Iaa6969a63b490181caeea8384787335f58341931
|
|/
|
|
|
|
| |
There's no reason for these to be public, other than asking for trouble.
Change-Id: Ic0d262e4f016752d8393a4aefcefb45a993cd801
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As per the MPEG4 specs, the contents of the skip atom are irrelevant
and can be ignored. Currently, the parser attempted to parse the skip
atom which doesn't have any structure.
Attempting to parse the skip atom causes a problem if the bytes immediately
following the atom type (which denote the size for most other atoms)
form a extremely large number. In that case we add this large number to
the offset. Eventually, we get out of this atom because we can't parse
it. But we fail the 'sanity check' in the previous recursive level
since '*offset != stop_offset' would not be true.
This change completely ignores the contents of the skip atom.
Change-Id: I837e8279aa1417f7c35ed66be80aa6d313a77722
|
|
|
|
|
|
|
|
|
|
| |
MediaScanner mistake Video_ID for Auido_ID when MediaScanner
register genre of mp4 video content that this content have
genre data.
Add an explicit check for audio.
Change-Id: Ic27638e9e59af44e388a8c38d774a077f23520b7
|
|
|
|
|
|
|
|
|
|
|
| |
After scanning the sdcard for the first time, the MediaScanner deletes
the micro thumbnail database files. The MiniThumbFile class attempts to
recreate the files but ends up with 0-sized db-files that it cannot
store any more micro thumbs in, resulting in that all micro thumbnails
that are results from thumbnail request are never stored properly until
the device is restarted.
Change-Id: I2b49580ae3360447525dbee80f6ba15b4bc658dd
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cyclic references can occur between a Service object held by an
application and a ServiceRecord object held by the system server.
A part of the problem is that binders are leaked and since many binders
are implemented by inner classes of services these services are also leaked.
This causes low memory problems. The solution is: When a Service is beeing
destroyed, go through the ServiceRecord's all IntentBindRecord and set its
binder references to null. This allows the binder and the service object to
be garbage collected.
Change-Id: I5a257521964851f34c08ffb3908feaad96b1bafe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the remote Jerry device is powered down the BT link to the
phone is dropped, and the Jerry firmware in the phone quite
immediately tries to re-connect to the Jerry device. Then
SDP and Discover Services is started, fetchRemoteUuids() ->
discoverServicesNative(). This results in an asynchronous dbus
call dbus_func_args_async() that is provided with a callback
function, onDiscoverServicesResult(), but before this callback
function is used Bluetooth is disabled according to the problem
scenario above. For some reason this discover services activity
is not cleared when Bluetooth is disabled, so when Bluetooth
is enabled again the (old) callback function
onDiscoverServicesResult() is executed, but the following
getAddressFromObjectPath() fails. The reason for this is that
the deviceObjectPath parameter contains an old value,
containg the process id of the old bluetoothd (the one running
before Bluetooth was disabled). Then the new updated
AdapterObjectPath /org/bluez/<new bluetooth hd pid>/hci0/dev_
is not a prefix of the old deviceObjectPath /org/bluez/<old
bluetooth hd pid>/hci0/dev_<BT_ADDR>, which results in that null
will be used as address in sendUuidIntent(), and later on,
ending up in the BluetoothDevice constructor where and
IllegalArgumentExceotion is thrown due to
Bluetooth address = null. Then the phone will crash.
Making sure sendUuidIntent() is not called when address is null
is a work-around for the problem.
Change-Id: I8ff60bad80de3b379cef0970402943dfa4de3cfd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When using sendOrderedBroadcast(..) with a BroadcastReceiver the
BroadcastReceiver instance was not released. The reason for this was that
the resultTo field in the BroadcastRecord kept a reference until it was pushed
out of the mBroadcastHistory. This reference in turn kept a reference to the
process side IIntentReceiver (implemented in ReceiverDispatcher$InnerReceiver).
This in turn had a strong reference (through mStrongRef) to the Context.
In order to keep the debug output the resultTo is also kept as a String in the
new resultToString variable.
Change-Id: I4382a22a541c27b3694fb2b78a04ee820b235f8f
|
|
|
|
|
|
|
|
|
|
|
| |
When an SMS is sent to a phone that is not turned on, the sending
phone receives a status report saying that the message is pending.
The pending intent that is to be matched with the status report
should then not be removed from the list but rather remain in the
list to await a success or fail status report.
Note that the status report notification will still be lost if the
sending phone is turned off before receiving the status report.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Key LED does not turn off when entering into sleep mode at
the brightness allignment mode in setting.
1 Open the brightness allignment mode in setting
2 Enter sleep mode
Make sure that the keyboard light is turned off.
Change-Id: Ib0436954164bcd9f6cb8d4453304e645e6ff70f0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Description: During system wide suspend/resume call, the state machine for
stagefright player & awesome player are reset and the flags are updated
accordingly. But the state variables inside Media player class are left
at the play/paused state depending on the current state while suspend call
is issued.
because of this mismatch in the states between media player and the awesome
player, the subsequent calls to isPlaying() query inside media player is
setting the state to Paused as a error correction mechanism. since the
media player state is incorrectly set as paused, even though it was in started
state during suspend, all the subsequent calls to pause will return without
any action.
Inorder to correct this, the suspend state is introduced in the media player.
The current state is saved during suspend and is properly restored on resume
call.
Validation: Tested AV playback pause/resume several times along with multiple
system wide suspend/resume transitions.
Change-Id: If7d40260c05899fac551edabaa8051bac1d0d020
Signed-off-by: Sunita Nadampalli <sunitan@ti.com>
|
|
|
|
|
|
|
|
|
| |
In MPEG4Extractor, buffers for the esds and avcC atoms was
statically allocated for 256 bytes. But the esds atom can
be much larger. Hence, this change replaces the static
allocation with a dynamic allocation.
Change-Id: Ifc082ec77a2d03a6fff08ed5df2247636747c550
|
|
|
|
| |
Change-Id: Ib6a7e284648212bcb90a6f54dea834b83cda26c0
|
|
|
|
| |
Change-Id: I544bc4216304d059b84e96fcafbbf849d6737324
|
|
|
|
| |
Change-Id: Ibad5ef7076361504fdf48b8178806ac3d91dfe46
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Surface.openTransaction and Surface.closeTransaction is not reentrant.
If we are updating the mouse surface when the WindowManager is also
updating the surfaces, the global transaction can be closed too early
by the other side. The results are random runtime exceptions and
unstable surface state.
Move the mouse surface update logic to the big surfaces update
loop, together with the other surfaces update logic.
Change-Id: I38a4f264f8de59899c3ac0fdaf9d8cd520d41947
|
|
|
|
| |
Change-Id: I3659587e4005f3fa0401981a2329744840f9ff10
|
|
|
|
| |
This reverts commit 1acb2fbadc3da3c3fdb4f57425449780c1a8e20b.
|
|\
| |
| |
| | |
applied to Settings app power widget)" into froyo
|
| |
| |
| |
| |
| |
| | |
(the same fix has been already applied to Settings app power widget)
Change-Id: I255359ba4a6ba3d384140c4c9bd5f73e780b9037
|
|\ \ |
|
| |/
| |
| |
| | |
Change-Id: I3ef2c9b2a9a456efe9366b3ca386d0b4950d4f80
|
|/
|
|
| |
Change-Id: Ib9b0b8fe532670cd334c61007782acf05c71c32d
|