Problem with Calibration

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Build 0xdroid file system
2. Put the android.ubi on the sd card with other files and installer
3. Adding the vram = 12M option to install.conf boot optional args
4. Flash the System with the new android.ubi
5. Calibration App starts, calibrate the screen
6. Reboot to get device calibrated
7. After reboot launcher don't start. Just background + top bar

If skipped step 3 .. I get Error from the com.android.provision and the 
calibration don't complete

What is the expected output? What do you see instead?
Android Launcher

What version of the product are you using? On what operating system?
Devkit8000 128MB version + 7" LCD + Ubuntu

Please provide any additional information below.
Install.conf content:

[installer]

KERNEL_IMAGE  = 0xkernel.bin
ROOTFS_IMAGE  = android.ubi

# Uncomment the following to reflash the boot loader
U_BOOT_IMAGE  = flash-uboot.bin

# Uncomment the following to install to SD card
# INSTALL_TO_SD = y

# Uncomment the following to grab images from network
# NET_INSTALL=y
# IPADDRESS=192.168.0.202
# REMOTE_KERNEL_IMAGE=http://192.168.0.201/0xkernel-beagle.bin
# REMOTE_ROOTFS_IMAGE=http://192.168.0.201/android-beagle.ubi

# DEBUG=y

# [beagleboard]

# DEFAULT_DISPLAY = dvi
# DEFAULT_VIDEOMODE = dvi:1024x768MR-24@60

[devkit8000]

#7 inch
DEFAULT_DISPLAY = lcd
DEFAULT_VIDEOMODE = lcd:800x480
OPTION_ARGS = omapfb.rotate=0 vram=12M

#4.3 inch
# DEFAULT_DISPLAY = lcd
# DEFAULT_VIDEOMODE = lcd:480x272
# OPTION_ARGS = omapfb.rotate=1

Original issue reported on code.google.com by osama....@gmail.com on 28 Jun 2010 at 10:44

[GoogleCodeExporter]

I synced my source code with the latest source code ..
Clean the out using "make clean" and build it again ..

I removed the vram option from the install.conf
The Calibration UI doesn't appear at all !!

Original comment by osama....@gmail.com on 28 Jun 2010 at 1:04

[GoogleCodeExporter]

I'm sure now that the problem is that the calibration UI doesn't start at all..
May be someone have made changes to the code within the last month lead to 
that!!
Coz the built of the source code month ago lead to what happened in my first 
post here.

Original comment by osama....@gmail.com on 28 Jun 2010 at 3:59

[GoogleCodeExporter]

Hi,

Does this issue still exist?

Original comment by ckanru on 2 Jul 2010 at 9:32

[GoogleCodeExporter]

Nope fixed after your commit, Thanks

Original comment by osama....@gmail.com on 2 Jul 2010 at 6:34

[GoogleCodeExporter]

Great.

Original comment by ckanru on 2 Jul 2010 at 11:27

• Changed state: Fixed