buglabs / android Goto Github PK

-SMS
-Data service

Features:

1. HDMI works in a predefined, well supported resolution out of the box.
2. This resolution is supported in the SDK, allowing apps to be written for monitor vs lcd module
3. Some strategy for user input, perhaps by supporting "mouse as touch input"

BUG thinks it has a vibrator. Track that down in the build and disable it.

Here is the output from my serial console. GPS module is inserted into slot 2. You can see where the EEPROM is found and read for LCD and GPS but then you only see the LCD driver load.

http://pastebin.me/1a05c599123ef181510442d7c50d99a5

The display should go to sleep after a period of rest. Currently the system is setup to not allow this sleep mode since there is no way to make the device return from a sleep state.

The widgets and fonts do not fit on the small screen. See if they can be configured to be smaller.

Reproduced in build 82 & 89, happened in one prior build (I don't recall the build#), and Reboot fixed the issue.

STR:

1. Boot BUG with a freshly written build
2. Go to Settings > Wireless & Networks and select Wi-Fi
3. Appears to hang, then status goes to 'Error'

serial output:
libertas_sdio: Libertas SDIO driver                                             
libertas_sdio: Copyright Pierre Ossman                                          
libertas_sdio: Libertas SDIO driver                                             
libertas_sdio: Copyright Pierre Ossman 

Note: I couldn't get adb connected to pull logcat.

From Vish via IRC.

• Phone app

Enable the BUG GPS module in android, so location aware apps can use the location service API.

The Wiki (http://wiki.buglabs.net/index.php/Experimental:Building_Android_image_for_BUG_YT#Touchscreen_calibration) describes touchscreen calibration process, including existing calibration file. This file is not in the current build nor does the pointer calibration program run.

Upon inserting Video module, serial console becomes unresponsive. Console output:

[15137.429534] bmi_lcd: Module Removed...
[15137.497222] sharp_spi_panel display0: sharp_spi_lcd_disable
[15137.511108] MUX: setup DSS_D18 (0xfa002100): 0x0002 -> 0x0007
[15137.518646] MUX: setup DSS_D19 (0xfa002102): 0x0002 -> 0x0007
[15137.529876] MUX: setup DSS_D20 (0xfa002104): 0x0004 -> 0x0007
[15137.535705] MUX: setup DSS_D21 (0xfa002106): 0x0002 -> 0x0007
[15137.551422] MUX: setup DSS_D22 (0xfa002108): 0x0004 -> 0x0007
[15137.560699] MUX: setup DSS_D23 (0xfa00210a): 0x0004 -> 0x0007
[15140.740142] BMI: IRQ Triggered on slot: 1

The goal being: when running the QEMU-based SDK virtual device, be running the BUG API stack, and any necessary internals underneath to make them work to the degree that they are useful for development.

The current init.rc has a line:

write /sys/power/wake_lock my_lock

which prevents BUG from going to suspend mode after no activity. W/ user key support, its now possible to let device enter suspend. After commenting out this line, rebooting, when device goes to suspend, this data via logcat:

PM: Syncing filesystems ... done.
Freezing user space processes ...
Freezing of tasks aborted after 0.00 seconds (197 tasks refusing to freeze):

Restarting tasks ... done.
suspend: exit suspend, ret = -16 (2000-01-30 18:06:04.280273366 UTC)
PM: Syncing filesystems ... done.
E/gralloc ( 987): ioctl FBIPAN_Freezing user space processes ... DISPLAY failed!!
(elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s) (use no_console_suspend to debug)

From this point device cannot be woken up. It's possible that enabling the power button will fix this, or there may be other issues w/ suspend.

The current android boot procedures require setting specific scripts in u-boot. This makes the task of running Android on BUG more difficult than it should be.

This issue is to research the feasibility of booting Android SD image with the same u-boot configuration that BUG20 ships with.

For GPS to work on BUG20, AGPS must be disabled. It is enabled by default in the Android build but seems only configurable at runtime, via a system setting. See

frameworks/base/location/java/com/android/internal/location/GpsLocationProvider.java Line 909 for details

The hack solution is to hardcode to non-assisted GPS. A better approach would be to utilize some kind of build flag so the framework java code would not have to change from upstream.

Another key question is how easy / difficult is it to plug a module in and have it be recognized from any port. GPS test is only for slot 2 at the moment... what would it take to be autorecognized from any one upon cold start? Hot-plugging is overrated and I think we can do without it.

STR:

1. execute an adb install command and the install hangs and the BUG locks up

adb window

bcruskie@bdclap:~/android-sdk-linux_x86/platform-tools$ ./adb install GPSTEST.apk 
2459 KB/s (181264 bytes in 0.071s)
    pkg: /data/local/tmp/GPSTEST.apk

Serial output:

request_suspend_state: wakeup (3->0) at 177092224076 (2011-04-15 00:41:29.871063122 UTC)
android_usb gadget: high speed config #1: android
alarm_release: clear alarm, pending 0
alarm_release: clear alarm, pending 0
alarm_release: clear alarm, pending 0
binder: 1078:1148 transaction failed 29189, size 76-4

Note: Repro'd 4 times, only saw binder message once though

Intented for the user wishing to write apps w/ Android on BUG 2.0.

BUG has 4 LED spots. Logo, wifi, bt, and battery. These LEDs should be accessable by Android.

A critical question that needs to be answered is if the switch to Android can accommodate our existing modules. I spoke to Izzy and he said all the config at the kernel/driver layer is the same pretty much as standard Linux. Since VonHippel differentiates us from smartphones, I would vote to get this up/running first... be able to control things, etc.

BUG20 has one user-accessible button. Android devices typically have 4 buttons:
HOME
BACK
PROPERTIES
SEARCH

The PROPERTIES button is necessary in many applications. Also, BACK and HOME are obviously important. This issue is to determine how these buttons can be triggered on BUG w/out having hardware buttons available.

The build is set to enable BT support. It's not yet configured to ship the necessary programs to intialize the BT device, bccmd, hciattach, and hciconfig. hci* are built but not shipped. bccmd needs to be added to the build. init.rc needs to be modified to perform the initialization via bccmd, and then binding via hciconfig.

See:
http://www.mailinglistarchive.com/html/[email protected]/2010-04/msg00349.html
http://source.android.com/porting/bluetooth.html

Occurred in build 58. Kernel output:

Unable to handle kernel paging request at virtual address 00200200
pgd = c0004000
[00200200] *pgd=00000000
Internal error: Oops: 805 [#1] PREEMPT
last sysfs file: /sys/power/state
Modules linked in: bmi_lcd_core bmi_video_core
CPU: 0 Not tainted (2.6.32.9-g4461c4b #1)
PC is at musb_g_giveback+0x18/0x114
LR is at nuke.clone.0+0xbc/0xe4
pc : [] lr : [] psr: 200001d3
sp : c04d9df0 ip : 00000000 fp : 00000000
r10: fa0ab000 r9 : 000000f0 r8 : 800001d3
r7 : 00000001 r6 : 0000fffc r5 : cf8922cc r4 : cfa27ec0
r3 : 00100100 r2 : ffffff94 r1 : 00200200 r0 : cf8922cc
Flags: nzCv IRQs off FIQs off Mode SVC_32 ISA ARM Segment kernel
Control: 10c5387d Table: 8e06c019 DAC: 00000017

PC: 0xc025c39c:
c39c c03a86b4 c047a04e c03a88e8 c047a069 c047a096 c047a0ac e5103bfc e1d300bc
c3bc e12fff1e e1a03000 e2511000 13a01001 e3a00000 e5532008 e7c72391 e5432008
c3dc e12fff1e e92d4010 e5100bf0 e5903024 e3530000 03e0005e 08bd8010 e12fff33
c3fc e8bd8010 e12fff1e e92d41ff e1a04001 e591101c e1a05000 e5943018 e5d07044
c41c e5813000 e5831004 e5943020 e59f10d0 e3730073 e59f30cc e594602c 05842020
c43c e584301c e3a03001 e5841018 e5c03044 e1a00006 eb04b335 e5d43032 e594c020
c45c e3530000 13e03000 15843008 12833001 15c43032 e35c0000 e59f308c 1a00000b
c47c e5933000 e3530004 9a000015 e594e024 e3a0208e e594c004 e5953004 e59f106c

LR: 0xc025e1f4:
e1f4 13002408 03a02010 11c320b2 13a02008 01c320b6 11c320b2 01c320b6 e5940038
e214 e1a0e00f e595f014 e59f206c e5922000 e3500000 e1a0c000 13a03001 03a03006
e234 e1520003 3a000005 e59f0050 e3a020bc e59f104c e2843018 e58dc000 eb04a0c6
e254 e5940038 e1a0e00f e595f00c e3a03000 e5843038 e284503c ea000000 ebfff863
e274 e594303c e1a00004 e3e0206b e1530005 e2431018 1afffff8 e8bd803e c09112c0
e294 c047a84e c03a8a74 e92d41f0 e5905028 e5d0602c e3a030bc e1a04000 e1a00005
e2b4 e0235693 e59370bc eb04ac2a e5d4202e e595309c e3520000 e1a08000 0a000006
e2d4 e1d320b6 e3a01001 e1c26611 e1c360b6 e3a03000 e1c730b0 ea000004 e1d310b8

SP: 0xc04d9d70:
9d70 00000000 200001d3 ce03df24 c04d8000 00000000 600001d3 00000001 800001d3
9d90 000000f0 ffffffff c04d9ddc 0000fffc 00000001 c002ca2c cf8922cc 00200200
9db0 ffffff94 00100100 cfa27ec0 cf8922cc 0000fffc 00000001 800001d3 000000f0
9dd0 fa0ab000 00000000 00000000 c04d9df0 c025e274 c025c41c 200001d3 ffffffff
9df0 cf8922cc cfa27ec0 ffffff94 cfa27ed8 cf8922cc cf892308 0000fffc fa0ab110
9e10 800001d3 c025e274 cf8922cc 0000fffe 00000000 cf8922cc cf8920e8 c025e314
9e30 00000000 cfa309c0 00000001 cf892d80 00000004 c026390c cfa309c0 cf8cb3c0
9e50 a00001d3 c0261d68 cf8cb3c0 cf8cb3f8 a00001d3 c02621b8 cf8920e8 fa0ab000

R0: 0xcf89224c:
224c 00000000 00000000 00000000 cf8920e8 fa0ab024 fa0ab110 00000001 02000200
226c 00000000 00000000 fa0ab088 00000000 00000000 00000101 cfa309c0 cf89229c
228c c03a89cc cf8922d8 cf892d88 00000200 69317065 0000006e 00000000 cf892258
22ac cf8920e8 00010201 00000200 00000000 00000000 cf8922c0 cf8922c0 00000001
22cc cfa309c0 cf8922e4 c03a89cc cf89234c cf892290 00000200 6f317065 00007475
22ec 00000000 cf892258 cf8920e8 00000201 00000200 00000000 00000000 cfa27ed8
230c cfa27ed8 00000001 cf8920e8 fa0ab028 fa0ab120 00000002 02000200 00000000
232c 00000000 fa0ab090 00000000 00000000 00000101 00000000 cf892358 c03a89cc

R4: 0xcfa27e40:
7e40 cfa06000 00000018 ffffffff 00000000 c0263d60 00000000 cfa30a40 cfa27e98
7e60 00000000 00000018 cf892284 cf8920e8 00000101 00000000 00000000 00000000
7e80 cfa03000 00000017 ffffffff 00000000 c0263d60 00000000 cfa27e58 cfa27dd8
7ea0 00000000 00000017 cf892284 cf8920e8 00000101 00000000 00000000 00000000
7ec0 cfa47000 00000018 8fa47000 00000000 c02639dc 00000000 00100100 00200200
7ee0 ffffff94 00000000 cf8922cc cf8920e8 00000100 00000000 00000000 00000000
7f00 756e694c 2e322078 32332e36 672d392e 31363434 20623463 6273756d 6463682d
7f20 c04dc100 c04fa2ec cfa27fac c0069098 00000000 00000000 c006901c ffffffff

R5: 0xcf89224c:
224c 00000000 00000000 00000000 cf8920e8 fa0ab024 fa0ab110 00000001 02000200
226c 00000000 00000000 fa0ab088 00000000 00000000 00000101 cfa309c0 cf89229c
228c c03a89cc cf8922d8 cf892d88 00000200 69317065 0000006e 00000000 cf892258
22ac cf8920e8 00010201 00000200 00000000 00000000 cf8922c0 cf8922c0 00000001
22cc cfa309c0 cf8922e4 c03a89cc cf89234c cf892290 00000200 6f317065 00007475
22ec 00000000 cf892258 cf8920e8 00000201 00000200 00000000 00000000 cfa27ed8
230c cfa27ed8 00000001 cf8920e8 fa0ab028 fa0ab120 00000002 02000200 00000000
232c 00000000 fa0ab090 00000000 00000000 00000101 00000000 cf892358 c03a89cc

R10: 0xfa0aaf80:
af80 ******** ******** ******** ******** ******** ******** ******** ********
afa0 ******** ******** ******** ******** ******** ******** ******** ********
afc0 ******** ******** ******** ******** ******** ******** ******** ********
afe0 ******** ******** ******** ******** ******** ******** ******** ********
b000 ******** ******** ******** ******** ******** ******** ******** ********
b020 ******** ******** ******** ******** ******** ******** ******** ********
b040 ******** ******** ******** ******** ******** ******** ******** ********
b060 ******** ******** ******** ******** ******** ******** ******** ********
Process swapper (pid: 0, stack limit = 0xc04d82f0)
Stack: (0xc04d9df0 to 0xc04da000)
9de0: cf8922cc cfa27ec0 ffffff94 cfa27ed8
9e00: cf8922cc cf892308 0000fffc fa0ab110 800001d3 c025e274 cf8922cc 0000fffe
9e20: 00000000 cf8922cc cf8920e8 c025e314 00000000 cfa309c0 00000001 cf892d80
9e40: 00000004 c026390c cfa309c0 cf8cb3c0 a00001d3 c0261d68 cf8cb3c0 cf8cb3f8
9e60: a00001d3 c02621b8 cf8920e8 fa0ab000 00000001 c025c5a0 cf8920e8 fa0ab000
9e80: 00000099 00000099 00000004 c025c6cc cf8920e8 00000002 cf8920e8 00000001
9ea0: 00000099 c025aa68 400001d3 c025af7c 0000005c 00000001 0000001f 00000000
9ec0: cf8920e8 400001d3 0000005c 00000001 c04d8000 0000001f 00000000 c025afbc
9ee0: cf8c3740 00000000 00000000 c0081bd4 c04ef118 0000005c c04ef154 cf8c3740
9f00: 00000001 c00838e4 0000005c 00000000 00000003 00000002 00000001 c002c06c
9f20: ffffffff fa200000 00000003 c002ca84 00000000 00000000 01362162 01362162
9f40: c051cfe0 00000003 00000003 c051cfc4 80026db4 411fc083 0000001f 00000000
9f60: 3b9ac9ff c04d9f78 c003bc84 c003bc8c 60000053 ffffffff 00000000 01362162
9f80: 4d9355e5 044f9dbd 4d9355e5 03197c5b c0911a18 c04dec90 c04ded00 c0911a18
9fa0: c04dc168 c02777dc c04d8000 c04dc170 c051c604 80026db4 411fc083 0000001f
9fc0: 00000000 c002dbf8 c090331c c0028e18 c0028e14 c0008900 c0008474 00000000
9fe0: 00000000 c0028e18 00000000 10c53c7d c051c6f0 80008034 00000000 00000000
from
from
from
from
from
from
from
from
from
from
from
from
from
Exception stack(0xc04d9f30 to 0xc04d9f78)
9f20: 00000000 00000000 01362162 01362162
9f40: c051cfe0 00000003 00000003 c051cfc4 80026db4 411fc083 0000001f 00000000
9f60: 3b9ac9ff c04d9f78 c003bc84 c003bc8c 60000053 ffffffff
from
from
from
from
from <80008034>
Code: e591101c e1a05000 e5943018 e5d07044 (e5813000)
---[ end trace 0fa1e3ae011ac84a ]---
Kernel panic - not syncing: Fatal exception in interrupt

Currently (as of build 47) the power button causes no change on an Android-booted BUG.

I think you know what I mean here... for us to become believers and to commit to the switch, I think we need to prove the following (some of which I'll be throwing into our next sprint meeting on Mon/Tues):

• 3G/4G wireless. I imagine getting one working would make us believers.
• Get a complicated BUGmodule working. If it works for one, shouldn't it work for all?
• (Maybe: get a slot to autorecognize the module from coldstart)

What else is missing from this core list?

In build 89 I see the state reversed for this.

When AC power is attached battery GUI icon is displayed without charging status
When AC power is detached Battery icon shows charging status (to further verify press and release power button to show charging status on lock screen)

Update: Upon 1st boot the power state of the battery is correct. Here are the STRs

1. boot BUG with AC power attached
2. Verify battery icon displays "charging" state
3. Remove AC power from BUG
4. Verify battery icon still displays "charging" state (like the gui missed this message from the kernel space)
5. Attach AC power from BUG
   6 Verify battery icon now displays battery "usage" state

Issue can be repro'd if you reverse the AC power steps, e.g. boot the BUG without AC power etc

Allow userspace to turn on/off modules via sysfs interface.

Audio out was implemented by Tarent for the VDZ release, but I don't think anyone has ever tried it. Would be good to know if it works or not...

Upon boot, device/serial console become unresponsive. Serial console output:

...
[ 38.496582] input: TSC2004 Touchscreen as /class/input/input0
[ 38.505096] input: ML8953 Accelerometer as /class/input/input1
[ 38.512573] bmi_lcd.c: probe...
[ 38.515747] bmi_lcd bmi-dev-1: Probe returned: 0x0
[ 38.521881] bmi_lcd.c: BMI_LCD Driver...

BUG 2.0 has a user key. Currently Android does not recognize the button.

Sensor should be available for use by Android applications.

When booting Android VDZ, BUG LCD screen does not turn on after boot completes.

STR:

1. boot VDZ on BUG 20 w/ LCD module
2. Note no display on LCD

Can we put the BUG into sleep mode? Is this easier than current stack? At the very least, would be good to sleep the LCD display.