Well I suppose the easiest way to tell if you are close to get it going, is
to just adb reboot recovery. If you get the little android guy screen,
you already won half the battle.
Then its just a matter of getting your recovery application going and
making sure your recovery.fstab is correct.
Please check your logcat logs.
On serial console, type logcat, which will print all the logs related to
userspace, and there might be some crash in userspace which is causing this
issue.
Especially because of Graphics crash/Surface flinger, you will see the
untracked pid exitted, without any UI.
Hi Everyone,
Please help me understand how to properly disable CONFIG_NEON in android
(kernel and framework)
Thanks
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Assuming that the adbd is running, if you press enter key on the serial
port console it should give you adb shell prompt.
But if there are any new log messages on serial port, that output
overwrites the prompt.
-br
Arun
On Saturday, 27 October 2012 11:58:24 UTC+1, Nandi wrote:
I am able to
Hi,
How can i send and receive data from an external usb device ?
here is the dmseg :
new full speed USB device number 103 using ehci-omap
[ 7793.537719] usb 1-1.1.2: New USB device found, idVendor=0403,
idProduct=6001
[ 7793.545684] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2,
Hello all,
I am not able to do file test operations in android
if I am executing below command
-b /dev/ttyACM0
it is saying
*-b: not found*
if I am executing in script
device0=/dev/ttyACM0# / (root directory)
if [ -b $device0 ]
it is giving
*:] not found
*
I tried test -b
do you have terminal access to your board?
please provide your logcat output.
On 07/25/2012 09:14 AM, Duc Le wrote:
Hi all,
I tried to modified TI Android ICS for beagleboard XM to make it work with
devkit8000. But I got the following error:
*Freeing init memory:167*
*Warning: unable to open
