e anything. And I'm not sure where to look
to turn on "DHCP" traces.
Thanks,
twebb
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Did you ever manage to get support into your driver for the:
DRIVER RSSI
DRIVER LINKSPEED
DRIVER MACADDR
etc...
commands?
Just curious because I'm having trouble with those using a TI wlan
driver.
twebb
On Jul 11, 9:41 am, Elvis Dowson wrote:
> Hi,
> I finally managed to
me exactly how.
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
ult in the code being built, but it only seems to result in
portions of the wlan tools being built.
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
On Jun 3, 12:35 pm, twebb wrote:
> On custom hardware, I've recently moved from android-1.0 to
> android-1.5 (cupcake) and seem to not be able to connect between linux
> host and target via adb. I've done this often enough in the past
> without problems using the foll
b version?
I've also recently moved to using an omapzoom-based kernel. Could
this be the source of the problem?
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
mass_storage/lun0
>
> }
>
> -Howard
I've tried this, plus a few other variations, but still no luck. Was
there more to your hack? I still have issues with vold looking for...
/sys/class/mmc_host/mmc0/mmc0:b368/block
but target fs only has...
/
I know where to get vold.conf now. My problem is that vold is not
recognizing my sd card (with what I think is a valid vold.conf file.
Mountd worked fine (in r1.0), but vold (in r1.5) has various issues
recognizing device paths, etc.
--~--~-~--~~~---~--~~
unsubsc
> for the record, the file lives in /system/etc/vold.conf
>
I didn't find it there, at least not in the git I'm looking at...
http://android.git.kernel.org/?p=platform/system/core.git;a=tree;f=rootdir/etc;h=a7dbd04b4031668782ed8259de72159fcb075731;hb=8fbedcf73c0bfd2ecdbb4d4c93edd3d39dc28fd4
I d
o get vold basically working as mountd did?
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Does anyone know how to launch the terminal emulator apk in the new
sdk-1.5? I see it listed amongst all the apps in ManageApplications,
but can't figure out how to launch it.
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+uns
this specific symptom?
I can't tell whether the problem is with the missing copybit.*.so and
overlay.*.so libraries, or something else that causing the exception
in the ActivityManager. Suggestions on how to debug this?
Thanks,
twebb
I/DEBUG ( 574): debuggerd: Apr 28 2009
18:34:23
E/flash_i
7;t know the IP addr that was assigned to the
target by the DHCP server, how can I start adb? Can ADBHOST be set to
a network, like 192.168.1.* ?
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.g
I'm porting android to a platform that has an LCD display which is
native landscape. What can I do to make Android come up initially in
portrait mode? Is there a specific android mechanism to do that?
Also, does android support display rotation or just display flipping?
Thanks,
in addition to, or instead of, the
existing...
LOCAL_MODULE_TAGS := samples
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
ize that some/most of the contents may be proprietary, but I'm
just looking to find out what the basic components are (like does it
include the bootloader itself?).
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups
Regarding recovery functionality, is platform/bootable/recovery the
place to focus or is is platform/recovery?
Has anyone ported this code/functionality for use on another target?
Thanks.
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups
I'm considering using the OTA update method for updating code on a new
device, but not using Google's OTA server(s). So effectively my
update sequence would start after the update.zip file arrives on the
device (ignore how it got there for the moment). Can someone (JBQ?)
describe the update sequ
Is there a particular reason that the update package file, update.zip,
is a zip file versus a tar/gzip file? Seems like an odd choice given
a linux-based system.
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups
> diskinstaller is only used for x86 to create a bootable installer.
>
Couldn't the same model be applied to ARM targets? Is use of the
diskinstaller or a description of how it works available?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@google
Other than the brief comments in recovery.c and firmware.c, are there
more detailed documents explaining the android startup process, from
power on to opening screen? I don't necessarily care about the G1
implementation details but am interested in the android-specific
features. In designing a n
> for the record, a future release of the SDK will feature "virtual machines",
> where each VM corresponds to a directory holding persistent disk images,
> including a cache.img disk image.
>
Could you add some detail to the "virtual machines" feature and to
what you mean by persistent disk image
are there general guidelines for how much flash
memory (perhaps as a percent of total flash memory) should be
allocated to /cache?
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
the make command line be? Is there any
general documentation that details incremental building?
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
>> Is something broken or did I miss a step?
>
> 5. in vendor/htc/dream/ there is a script that must be run (from that
> directory) to extract some proprietary binaries from your device.*
Yes, I see that I overlooked that - thanks. So without an actual HTC
Dream phone, I won't be able to run th
I followed the instructions at
http://source.android.com/documentation/building-for-dream
and the build failed with the following error:
make: *** No rule to make target `vendor/htc/dream/proprietary/akmd',
needed by`out/target/product/dream/system/bin/akmd'. Stop.
Is something broken or did I
roup/android-porting/browse_thread/thread/a67cbe36603d429a/63d47d07a71defa1?q=mmcblk0&lnk=ol&;
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Must adbd be configured in a
certain way when started on the target? I currently have functional
ethernet, but not USB or wireless. adbd/ddms is new territory for me
so any suggestions would be appreciated.
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe:
thing else? All other key related,
touchscreen related, and frame buffer related functionality seems
fine.
Thanks,
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
> Have you got the frame buffer driver work correctly? If not, maybe you could
> try making it work first and then see whether the keypad problem still exists.
I have frame buffer driver working OK. Unless of course it's a frame
buffer issue that is resulting in the cursor highlight not followi
On Dec 12, 4:49 pm, apoorv wrote:
> Is there any material available for porting android to OMAP?
> Apoorv
see...
http://elinux.org/Android_on_OMAP
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/gr
ging the keypad
driver." Did you change it from single GPIO per switch to matrix? or
did some other change fix the problem?
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
-
only every other key press. That's why I was looking for Reed's
changes to keyboard driver that he referred to in his original
response.
twebb
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
n you give a few more details on what you had to change in the
keypad driver? I'm having similar problem and my hardware is using
matrix keyboard mode. Since I can't change the hardware, I'd like to
know what you changed in the ke
34 matches
Mail list logo