Android build didn't create contents of /data directory

by vishal bhoj » Thu, 09 Jul 2009 06:53:30 GMT


Sponsored Links
 content are loaded at boot time . On what device are you trying it out ?
How are you mounting the data. there are few changes needed to be done in
the init.rc script .







-- 
with regards vishal

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Android build didn't create contents of /data directory

by vishal bhoj » Thu, 09 Jul 2009 08:12:08 GMT


  u preparing the filesystem on sdcard or  creating the system image and
flashing it ?
Start Posting ur querries on android-porting group.
On Thu, Jul 9, 2009 at 12:56 PM, Saravanan <saravanan....@gmail.com> wrote:



--
with regards vishal

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Android build didn't create contents of /data directory

by vishal bhoj » Thu, 09 Jul 2009 08:57:34 GMT


 n android system and userdata are 2 different partitions which are mounted
by the init script. If you have a single filesystem do the changes as shown
in the init script used on omapzoom kit with filesystem on sdcard.


on init

loglevel 3

# setup the global environment
export PATH /sbin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
export BOOTCLASSPATH
/system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar

# Backward compatibility
symlink /system/etc /etc

# create mountpoints and mount tmpfs on sqlite_stmt_journals
mkdir /sdcard 0000 system system
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /sqlite_stmt_journals 01777 root root
mkdir /data/misc/ 0771 system system
mkdir /data/misc/wifi 0771 system system
mkdir /data/misc/wifi/sockets 0771 system system
mkdir /data/misc/dhcp 0777 system system
mount tmpfs tmpfs /sqlite_stmt_journals size=4m

# since system is also on root - we don't want to do this
# mount rootfs rootfs / ro remount

write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000

# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a
checkpoint
# mount yaffs2 m...@system /system
# mount yaffs2 m...@system /system ro remount

# We chown/chmod /data again so because mount is run as root + defaults
# mount yaffs2 m...@userdata /data nosuid nodev
chown system system /data
chmod 0777 /data

# Same reason as /data above
# mount yaffs2 m...@cache /cache nosuid nodev
chown system cache /cache
chmod 0770 /cache

# This may have been created by the recovery system with odd permissions
chown system system /cache/recovery
chmod 0770 /cache/recovery

# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/hcid 0770 bluetooth bluetooth
mkdir /data/local 0771 shell shell
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root

# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache

# create the lost+found directories, so as to enforce our permissions
# mkdir /data/lost+found 0770
# mkdir /cache/lost+found 0770

# change permissions for alsa nodes
symlink /dev/snd/pcmC0D0c /dev/pcmC0D0c
symlink /dev/snd/pcmC0D0p /dev/pcmC0D0p
symlink /dev/snd/controlC0 /dev/controlC0
symlink /dev/snd/timer /dev/timer
chmod 0777 /dev/pcmC0D0c
chmod 0777 /dev/pcmC0D0p
chmod 0777 /dev/controlC0
chmod 0777 /dev/timer

# change permissions for modem
chmod 0660 /dev/ttyS0
chown radio radio /dev/ttyS0

# change permissions for bridge. Symlink



Other Threads

1. Opening for Google Android Developer with Mobile app Development MNC in Bangalore

Salaam developers,
              I wanted to introduce to you guys about a niche
opportunity to work on the Android Platform for one of our MNC clients
who are into mobile application development. Following is the JD and
some information about out Client

Position: Sr. Software Engineer
Exp: 3-8
Location: Bangalore
CTC: Not a concern for the right candidate

Tech Skills:

Hands on experience on  the Android Platform (must)
Working knowledge of XHTML (must)

About Client:

      Found in the year 2000, our client enables mobile content and
applications for Mobile Network Operators (MNOs), Mobile Virtual
Network Operators (MVNOs), Content Providers and Enterprises.

      Our clients products and services assist its customers to create,
launch, manage, and monetize mobile content and applications across
multiple mobile devices and networks (3G & 4G).

      Our Client has office in US and India and serves a variety of global
customers including Fortune 500 Companies Alltel, AOL, Disney Mobile,
ESPN Mobile, Reliance Infocomm, TV Guide, Verizon Wireless, and Xerox


If this opportunity e{*filter*}s you, update me with your latest CV to
hr.molo...@gmail.com or call me at 080 - 40609618 for more information
on the same..

Looking forward to hear from you guys soon..

Cheers Developers!!

--~--~---------~--~----~------------~-------~--~----~

2. Debugging Android Native C Applications with gdb

Hi,

we used the following setup and able to communicate between gdb server
and gdb client. but couldnt accomplish to hit the breakpoints.
breakpoints are getting ignored. Please suggest if you have any idea
on this.



1.    Makefile already had the -g option and the code is compiled with
this option.

2.    Run the emulator and using following steps add a redirection of
port.

  localhost 5554
  add tcp:4444:4444
  exit

3.    On the emulator

    1. Give ps command and find the pid of the syncml service
(com.samsung.client:remote)

    2. Run gdbserver. (./gdbserver 10.0.2.2:1234 hello1)

4.    On the host

1.    run the gdb client

.../mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-
gdb  mydroid/out/target/product/generic/symbols/system/lib/
libsyncml_jni.so

2.   Connect to server : Target remote localhost:4444. When doing
this, emulator responds printing a message emote debugging from host
10.0.2.2
3.    Able to give gdb commands and able insert breakpoints.



The problem is it is not hitting the breakpoints inserted, and we
encuntered an issue saying "gdb: Unable to get location for thread
creation breakpoint: requested event is not supported"

So please suggest if you have any idea on this.

Thanks
Sudhindra



--~--~---------~--~----~------------~-------~--~----~

3. Cupcake timeline fixed

4. Problem accessing Google Weather API

5. accessing Gdata

6. visual performance analyser (vpa-rcp-6.3.0-linux-x86)

7. Multi-tasking method suggested; making Android more dynamic