Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- commit 4f18d27e5407f27fdab3ba956ae89a0949a896ab
- Author: Pedlar <pedlar88@gmail.com>
- Date: Wed Sep 15 00:49:38 2010 -0400
- Galaxy S Style Power Widget
- Not ready yet, uploaded for kmobs.
- commit dd699a2c08c820b9896289356d233be681d1fc8b
- Merge: 2acc5cc 586e36d
- Author: Keyan Mobli <persiansown@gmail.com>
- Date: Sat Sep 18 09:52:09 2010 +0000
- Merge "German: longpress close toast message" into froyo
- commit 2acc5ccf095651f16b00b5ba4b24d2dd4b211fa6
- Merge: 355dd72 d761466
- Author: Steve Kondik <shade@chemlab.org>
- Date: Sat Sep 18 04:25:15 2010 +0000
- Merge "Revert headset statecode patch Change-Id: I7339e589fd8df4dd3e24fe4c35e0285d806627a5" into froyo
- commit d76146601c58cd860cf82bd0171a8c22ff563eb3
- Author: mrpaulmanley <mrpaulmanley@gmail.com>
- Date: Fri Sep 17 22:02:03 2010 -0500
- Revert headset statecode patch Change-Id: I7339e589fd8df4dd3e24fe4c35e0285d806627a5
- Change-Id: Id2e61efc757bcf391f56f13315bee7ae90f11395
- commit 586e36d20a265f0f80ece76810f4f6f097fbb322
- Author: thiasB <m.buechner@gmail.com>
- Date: Fri Sep 17 18:07:50 2010 +0200
- German: longpress close toast message
- commit 355dd7282550cc00be5d86fd8c365098b32e6a92
- Author: Henrik Backlund <henrik.backlund@sonyericsson.com>
- Date: Mon Aug 30 11:59:42 2010 +0200
- Fix to get A2DP to connect after unpairing
- In this fix, A2DP profile will be connected when pairing with a
- previously paired headset. The reason for this error was that the
- connection of the A2DP profile was sent before the callback
- onCreatePairedDeviceResult was receied in BluetoothEventLoop.java.
- By not going to the state BOND_BONDED until after this callback has been
- received, the problem is fixed. However the use case is different if the
- pairing is initiated by the remote device. In these cases state
- BOND_BONDED will be set when onDevicePropertyChanged instead.
- Change-Id: I5dedca87d0a6872705ff3a933a99cce6eb37618a
- commit 83612a175769a6d068b5adfbee7826f149364388
- Author: Anthony Newnam <anthony.newnam@garmin.com>
- Date: Wed Sep 1 12:06:04 2010 -0500
- Avoid pre-processing images when they won't be used
- Change-Id: Iffa31228ca95a2e29ccc0aa81bda0fc66922d577
- commit ca4abef9a9e6da1947e9a7168f9b635e32025292
- Author: Pal Szasz <pal.szasz@sonyericsson.com>
- Date: Fri Sep 3 11:46:26 2010 +0200
- Allow two SurfaceViews inbetween the app and the wallpaper.
- When two SurfaceViews are used by an application, which is
- transparent and uses the wallpaper, only one of the SurfaceViews
- will be visible.
- The problem is that when trying to find the correct location
- for the wallpaper, the window manager locates the activity
- window and skips every window below it which is related.
- For the first SurfaceView this will be ok, since the
- SurfaceViews's attached window is the previous window.
- However for the second SurfaceView this condition will fail
- (the 2nd SurfaceViews attached window is not the previous
- window (which is the 1st SurfaceView)).
- The fix adds an extra check which detects this usecase
- (the windows are related if the attached window is the same
- as the attached window of the previous window).
- Change-Id: I368e9dd53455dc310f48d6d8c0be68350ff2b79e
- commit cc3d581a33d385c652f747c6917634c56ab9a8e8
- Author: Johan Alfven <johan.alfven@sonyericsson.com>
- Date: Thu Sep 2 14:26:54 2010 +0200
- Make sure OutOfMemoryError is handled by WallpaperManager
- Make sure exception OutOfMemoryError is handled when calling
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement