| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Change mksdcard to a minimum of 9 MiB, which is what
we enforce in the UI (I believe the 8 MiB min was obsoleted
by the 9 MiB one.)
Also warn the user about the min/max sdcard size properly
directly in the creation dialog, instead of relying on
mksdcard to fail later.
Change-Id: I30bc425ed6b75d8a00965e9e2e25890bd9bd8b39
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes:
- Issue 13277: mksdcard fails to create insanely large sdcard.
- Issue 14429: better error message when disk full.
Details:
- Actually report fopen/fwrite errors (instead of silently failing.)
This alone fixes the 2 reported issues.
- Check size argument parsed correctly and isn't larger than
the FAT format can handle.
- Actually indicate in the usage text the min/max size values.
- Added support for a 'G' postfix, to make gigabyte sdcards.
Change-Id: I4986c2c7c031f3b9bfd580b015b56d741aba778f
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use create_thread_cb instead of pthread_create to create gps_state_thread
so it can safely call into the Java framework.
BUG: 3375089
Change-Id: Ie7b2bd4bea519702d4238ba375bf83b059095b9e
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|/
|
|
|
|
|
| |
The sensor HAL in libhardware was recently updated, this
change updates the sensor emulation to match the new HAL.
Change-Id: I1cf60665ec3cc59a14859de487a65b399ff9e343
|
|
|
|
| |
Change-Id: I787601e3ab3ac4ce3d5ef5691788af62abbf91e9
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
A proximity sensor is added to the sensors, the proximity sensor has
resolution 1 and maxRange 1. This means that it can be either 0 or 1.
Change-Id: I60e27ebe673d493124be19158e56a19b0e4813de
|
| |
| |
| |
| |
| |
| | |
Also respect 'Wipe User Data' by disabling snapshot launch, and support 'Edit AVD'.
Change-Id: I5bc94c316e550b2585ca80185a02ffbe6d3e8401
|
| |
| |
| |
| |
| |
| | |
They are now in development.git
Change-Id: I9b8ec2c65892cb7635b6be77a7c8929f62d018b8
|
|\ \
| |/
| |
| | |
Change-Id: Idf12fbcb5508ca53047fcde3c35a96f9a971d305
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When epoll_wait detected a state change of fd, an events
structure including pointer appointed in epoll_ctl is
returned by epoll_wait. The data of each returned structure
will contain the same data the user set with a epoll_ctl(2)
(EPOLL_CTL_ADD,EPOLL_CTL_MOD) while the events member will
contain the returned event bit field.
When older hook and epoll_event are deleted after hook and
epoll_event are added newly, this problem occur.
So, when hook is closed, rewrite physical address of epoll_event
which is pointing hook.
Change-Id: I90f01ba5fbf307b3483da67d993cb874ba56d155
|
|\ \ \
| |/ /
| | |
| | | |
Change-Id: I577a12b8961cd28dcb3238a1e484c689c0d578e7
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
is off.
Bug: 3083496
Change-Id: I9b456cf002a8a9d953d631c163054f8ccc9572fa
|
| | |
| | |
| | |
| | | |
This reverts commit 1fc95cae8ec2ccfe134ff279ed9082311ad0d877.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Moved Android.mk and keymap files except AVRCP.kl from sdk/emulator/keymaps
to build/target/board/generic. This causes the keymap files to copied into
the system image of generic and sdk products, but not into the system image
of HW products. Originally the qwerty.kl was copied to target no matter
if the target had a qwerty keyboard or not, which is the case for e.g.
the Nexus One.
Change-Id: I6f76bcd4e23b8478f36f213090d22d7d3ea1255b
|
|\ \ \
| | |/
| |/|
| | | |
Change-Id: I904122226e2940610970b75588884c2efe2d2000
|
| | |
| | |
| | |
| | | |
This reverts commit 246e0ee6968ed0030fe99cc12ca154a1513b8645.
|
|\ \ \
| |/ /
| | |
| | | |
Change-Id: If9dd02177b9e33556969be3b8eda46a362a424a6
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Moved Android.mk and keymap files except AVRCP.kl from sdk/emulator/keymaps
to build/target/board/generic. This causes the keymap files to copied into
the system image of generic and sdk products, but not into the system image
of HW products. Originally the qwerty.kl was copied to target no matter
if the target had a qwerty keyboard or not, which is the case for e.g.
the Nexus One.
Change-Id: I37ad5fb11fa70640433594c18953b626d1e9c186
|
|/
|
|
| |
Change-Id: I42b7e24a824d42bf53efcc6cf487102021c7b8d8
|
|
|
|
| |
Change-Id: I16f8c8b370f42c6229b3deabd66d2aaabd0b7937
|
|
|
|
|
| |
BACK == ESC
MENU == F10
|
|\
| |
| |
| | |
Change-Id: If11d893ba56c1189620e00f86b7f51bf4d698e49
|
| |
| |
| |
| | |
Change-Id: I1e3159ac3d322ca70c2d9d7faf3a0ecac4313468
|
|/
|
|
|
|
|
| |
This will replace equivalent code in libhardware_legacy
Change-Id: I611e34a187ed8460490f793538446c11c7c83cab
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|
|
|
|
|
|
| |
This gets rid of a bug where the control fd would be closed when the
data channel is opened, making the later activation of sensors impossible.
Also add more debugging messages.
|
|
|
|
|
| |
The emulator sensor code could enter a busy loop on certain
failure cases in poll.
|
|
|
|
| |
Change-Id: Icb3327e2371800029844a869df6abd68a8516aff
|
|
|
|
| |
Change-Id: Ic43873545dd7a9482e4214ed3750a8e2108cafc6
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Merge commit '62410fc5a983bd1057622bc51801ad36cd316811' into eclair
* commit '62410fc5a983bd1057622bc51801ad36cd316811':
Fixed QVGA skin and added WQVGA432 skin.
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit 'e058cf98bc44cf0492c0eb3da25a61c9419cbdc7' into eclair
* commit 'e058cf98bc44cf0492c0eb3da25a61c9419cbdc7':
Revamped QVGA skin and new WVGA 800/854 skins
|
| |\
| | |
| | |
| | |
| | | |
* changes:
Revamped QVGA skin and new WVGA 800/854 skins
|
| | |
| | |
| | |
| | | |
BUG: 1944280
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
Merge commit '45519a23b06c7f01ce2337816128c9d285f47a73' into eclair
* commit '45519a23b06c7f01ce2337816128c9d285f47a73':
New HVGA skin.
|
| |/
| |
| |
| | |
BUG: 1944280
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '6675fec474d86d77947cf68d47dd36e9744b9f14'
* commit '6675fec474d86d77947cf68d47dd36e9744b9f14':
First pass at a WVGA skin.
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit 'e0f85e6c7379c053cd3ece5bdd934337ff66cd45'
* commit 'e0f85e6c7379c053cd3ece5bdd934337ff66cd45':
Delete non rotating skins and create a QVGA rotating skin.
|
| |
| |
| |
| |
| | |
HVGA-P and HVGA-L were redundant with HVGA which supports both orientations.
QVGA-P and QVGA-L has been replaced with QVGA which supports both orientations.
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '8aa42da0f27be2437e02f43c203dc55ca085ee77'
* commit '8aa42da0f27be2437e02f43c203dc55ca085ee77':
Skins can now provide their own hardware support (via AVDs)
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '8b057ed6f6ec4e9eb829b230d6f2d35eaef8658e'
* commit '8b057ed6f6ec4e9eb829b230d6f2d35eaef8658e':
Fix bad qemud crash on emulator startup.
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
emulated system.
Merge commit 'af45b39d887ad4ec4a806d352009cdc28238f21f'
* commit 'af45b39d887ad4ec4a806d352009cdc28238f21f':
This adds a new helper program (qemu-props) to support the emulated system.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Its purpose is to contact the 'boot-properties' service during the
boot process and to set the list of system properties read from the
emulator program through it.
It must be launched from /system/etc/init.goldfish.rc as root.
It depends on the 'boot-properties' service being implemented by the
emulator (in a later patch). If not available, it will simply timeout.
This also fixes a potential crash in qemud which can happen in the following case:
- client sends a command to a service
- the service responds with one or more message
- the service immediately closes the connection before the client can read the data
what happened is that the FDHandler object was buffering out-going packets to the
client, but the Multiplexer acted on the disconnection immediately. This resulted
in:
- client_free() being called
- fdhandler_shutdown() being called
- the FDHandler being placed on the 'closing' list to be able to send
buffered packets later. And 'receiver_close' being called
- client_fd_close() being called, which would call client_free()
recursively
- the second client_free() call would free the object
- the first client_free() call would try to free the object again
- ==> dlmalloc() detects a double-free and immediately aborts.
the fixes simply avoids the calle to receiver_close() in fdhandler_shutdown()
since this function is called from an explicit shutdown request from the multiplexer,
it doesn't correspond to the case where the client has closed the connection itself.
|