Android on OMAP35x ?

[mattsranch]

Has there been progress on porting Android to Zoom OMAP35x Development
Kit ? Site omapzoom.org contains the older OMAP34x, however OMAP35x
better meets my needs.

[伊泽]

Beagle Board?

============

自由之精神，独立之人格
============

[Nishanth Menon]

伊泽 said the following on 11/09/2008 10:50 AM:
>
> Beagle Board?
>
No, it is zoom MDK[1]

>
> ============
>
> 自由之精神，独立之人格
> ============
>
>
> On Mon, Nov 10, 2008 at 12:33 AM, mattsranch <mgil...@gmail.com
> <mailto:mgil...@gmail.com>> wrote:
>
>
> Has there been progress on porting Android to Zoom OMAP35x Development

> Kit ? Site omapzoom.org <http://omapzoom.org> contains the older

> OMAP34x, however OMAP35x
> better meets my needs.
>

There is some amount of information in [2]. There are lots of progress
happening on Android on Zoom see [3]. join the mailing list[4] and get
more info..
Regards,
Nishanth Menon
Ref:
[1] http://www.logicpd.com/products/devkit/ti/zoom_mobile_development_kit
[2] http://elinux.org/Android_on_OMAP
[3] https://omapzoom.org/gf/project/omapandroid/wiki/
[4] https://omapzoom.org/gf/project/omapandroid/mailman/

[Sean McNeil]

Wind River has used the TI OMAP Zoom platform as a reference target for
a long time. They even showed it at the Barcelona conference early this
year.

[Maxime Petazzoni]

Hi,

I have successfully ported Android to an OMAP3EVM board last week, and
will most likely get it working soon on the OMAP Zoom as well. Details
of how much I'm allowed to talk about it still need to go through some
company processes though -- but the system does work pretty nicely.

The http://elinux.org/Android_on_OMAP wiki page does cover some of the
issues that you need to address to get it running, so it's a good (but
old/non updated) starting point.

- Maxime

[Eugenio]

Did you try the instructions that are posted on omapzoom.org website?
Maybe it will help you.

-Eugenio

[Maxime Petazzoni]

Works on Zoom. System runs nice and fast. I'm doing the final
touchscreen adjustments right now.

On Nov 10, 12:39 am, Maxime Petazzoni <maxime.petazz...@gmail.com>
wrote:

> Hi,
>
> I have successfully ported Android to an OMAP3EVM board last week, and
> will most likely get it working soon on the OMAP Zoom as well. Details
> of how much I'm allowed to talk about it still need to go through some
> company processes though -- but the system does work pretty nicely.
>

> Thehttp://elinux.org/Android_on_OMAPwiki page does cover some of the

[kapare]

Hi Maxime,

I have a OMAP3EVM and I'm interested in porting it with android.

OMAP3EVM come with OMAP35x_SDK_0.9.5 that contain 2.6.22.18.

1- Did you port the kernel to 2.6.25 or just used 2.6.22.18 + android
patch - goldfish stuff ?

2- Did you try to directly use the OMAP zoom on a OMAP3EVM, It seem to
work very slow and bugy!

Can you provide these information?

Thx

kap

On Nov 10, 4:02 pm, Maxime Petazzoni <maxime.petazz...@gmail.com>
wrote:

> Works on Zoom. System runs nice and fast. I'm doing the final
> touchscreen adjustments right now.
>
> On Nov 10, 12:39 am, Maxime Petazzoni <maxime.petazz...@gmail.com>
> wrote:
>
> > Hi,
>
> > I have successfully ported Android to an OMAP3EVM board last week, and

> > will most likely get it working soon on theOMAPZoom as well. Details

> > of how much I'm allowed to talk about it still need to go through some
> > company processes though -- but the system does work pretty nicely.
>

> > Thehttp://elinux.org/Android_on_OMAPwikipage does cover some of the

[Maxime Petazzoni]

Hi,

On 26 nov, 00:28, kapare <kevyn.alexandre.p...@gmail.com> wrote:
> Hi Maxime,
>
> I have a OMAP3EVM and I'm interested in porting it with android.
>
> OMAP3EVM come with OMAP35x_SDK_0.9.5 that contain 2.6.22.18.
>
> 1- Did you port the kernel to 2.6.25 or just used 2.6.22.18 + android
> patch - goldfish stuff ?

No, I've used MontaVista Linux 2.6.24 :
http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-Linux-for-Android.html
, on top of which I added the Android drivers (that needed a bit of
work because of some differences between 2.6.25 and 2.6.24, especially
in sysfs).

> 2- Did you try to directly use the OMAP zoom on a OMAP3EVM, It seem to
> work very slow and bugy!

Sorry, I don't understand your question :(

- Maxime

[kapare]

RE,

On Nov 26, 4:57 am, Maxime Petazzoni <maxime.petazz...@gmail.com>
wrote:

> Hi,
>
> On 26 nov, 00:28, kapare <kevyn.alexandre.p...@gmail.com> wrote:
>
> > Hi Maxime,
>
> > I have a OMAP3EVM and I'm interested in porting it with android.
>
> > OMAP3EVM come with OMAP35x_SDK_0.9.5 that contain 2.6.22.18.
>
> > 1- Did you port the kernel to 2.6.25 or just used 2.6.22.18 + android
> > patch - goldfish stuff ?
>

> No, I've used MontaVista Linux 2.6.24 :http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-L...

> , on top of which I added the Android drivers (that needed a bit of
> work because of some differences between 2.6.25 and 2.6.24, especially
> in sysfs).
>
> > 2- Did you try to directly use the OMAP zoom on a OMAP3EVM, It seem to
> > work very slow and bugy!
>
> Sorry, I don't understand your question :(

I was wondering if you used OMAP zoom src code and try it directly on
the OMAP3EVM. If so do you know the diff between OMAP3EVM src and OMAP
zoom src.

thx

[kapare]

Another one(s)?

Did you try with ?
http://source.mvista.com/git/?p=linux-omap-2.6.git

What is your sugested way to processed, easiest one to port OMAP3 EVM?
We have all src code given buy TI with support for opengl and other
drivers and don't want to loose all that support! We are a bit lost in
all those git tree from monta vista src, TI src, muru, linux arm,
android, etc

> No, I've used MontaVista Linux 2.6.24 :http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-L...

> , on top of which I added the Android drivers (that needed a bit of
> work because of some differences between 2.6.25 and 2.6.24, especially
> in sysfs).

Did you get the src code from git our from support of monta vista?

thx for helping a guy a bit lost!

kap

On Nov 26, 4:57 am, Maxime Petazzoni <maxime.petazz...@gmail.com>
wrote:

> Hi,
>
> On 26 nov, 00:28, kapare <kevyn.alexandre.p...@gmail.com> wrote:
>
> > Hi Maxime,
>
> > I have a OMAP3EVM and I'm interested in porting it with android.
>
> > OMAP3EVM come with OMAP35x_SDK_0.9.5 that contain 2.6.22.18.
>
> > 1- Did you port the kernel to 2.6.25 or just used 2.6.22.18 + android
> > patch - goldfish stuff ?
>

> No, I've used MontaVista Linux 2.6.24 :http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-L...

[Maxime Petazzoni]

Hi,

On 26 nov, 18:36, kapare <kevyn.alexandre.p...@gmail.com> wrote:

> > No, I've used MontaVista Linux 2.6.24 :http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-L...
> > , on top of which I added the Android drivers (that needed a bit of
> > work because of some differences between 2.6.25 and 2.6.24, especially
> > in sysfs).
>
> Did you get the src code from git our from support of monta vista?
>
> thx for helping a guy a bit lost!

I work at MontaVista, and the press release up there depicts our work
on Android. We used our kernel as the base for the Android port, so we
already have OMAP3EVM and OMAP3LDP board support. Except from small
keypad mapping changes between EVM and Zoom, I only had to rebuild the
kernel for the correct board to move from the EVM to Zoom. I haven't
tested yet, but I suspect it will go as smoothly for the BeagleBoard
as well.

- Maxime

[kapare]

Nice I'm happy to speak and exchange with MontaVista guy!

I imagine that your demo with OMAP 3 EVM and montavista src have been
ship for Embedded Technology 2008 in Yokohama, Japan, November 19-21 ?

I'm still wiondering why you used 2.6.24 and not minimally 2.6.25 or
higher, since android is 2.6.25.

I will try to go with 2.6.22.18 TI src and patch android on it!

thx for infos

kap


On Nov 26, 1:45 pm, Maxime Petazzoni <maxime.petazz...@gmail.com>

[Anil Sasidharan]

Hi,

We have ported android-1.0 onto OMAP3EVM (from Mistral)
with 2.6.26 kernel. If you are interested in getting some info/support
on this, please let us know.

Warm Regards,
Anil
Mistral

Warm Regards,
Anil

[Nimit Manglick]

Hi Anil / Maxime

I am also trying my hands on android..

I have also ported android on OMAP 35X (from Mistral) ..

I am getting the home screen with touchscreen working..

Now i want to move ahead with some queries :-

1. How to enable to Network sso that i can start playing with browser ?

2. Can I interface this board with GSM module so that i can have my call working ?

3. Is this released source code have working Bluetooth & WiFi ?? If yes then what

changes  & where I need to do to make them work (this board doesn't have bluetooth 7 WiFi support , I am asking for general steps )


Thanks & Regards
Nimit

[Maxime Petazzoni]

Hi,

On 27 nov, 03:04, kapare <kevyn.alexandre.p...@gmail.com> wrote:
> Nice I'm happy to speak and exchange with MontaVista guy!
>
> I imagine that your demo with OMAP 3 EVM and montavista src have been
> ship for Embedded Technology 2008 in Yokohama, Japan, November 19-21 ?

Indeed, we had a demo of Android running on OMAP Zoom at ET2008, as
the press release states.

> I'm still wiondering why you used 2.6.24 and not minimally 2.6.25 or
> higher, since android is 2.6.25.

That's simply because our base kernel at the time I started working on
Android was still a 2.6.24.

> I will try to go with 2.6.22.18 TI src and patch android on it!

Good luck!

- Maxime

[Anil Sasidharan]

Hi Nimit,

To enable networking do the following in the init.rc file

setprop net.gprs.local-ip <board's-ip-address>
setprop net.dns1 <primary-dns-server-ip>
setprop net.dns2 <secondary-dns-server-ip>

We've not tested Bluetooth, GSM on OMAP3EVM board.

Warm Regards,
Anil

[kapare]

Hi Anil,

You said that you have done the porting for 2.6.26, yes I'm
interested.

Did you start with 2.6.22.18 from OMAP35x_SDK_0.9.5 then port to
2.6.26 + android ?

Can you guide me from the beginning? I mean what are the first steps
and where did you take that 2.6.26?

Regards

kap

On Nov 27, 8:34 am, "Anil Sasidharan" <anil...@gmail.com> wrote:
> Hi Nimit,
>
>            To enable networking do the following in the init.rc file
>
>            setprop net.gprs.local-ip <board's-ip-address>
>            setprop net.dns1 <primary-dns-server-ip>
>            setprop net.dns2 <secondary-dns-server-ip>
>
> We've not tested Bluetooth, GSM on OMAP3EVM board.
>
> Warm Regards,
> Anil
>

> On Thu, Nov 27, 2008 at 11:56 AM, Nimit Manglick <nimitandr...@gmail.com> wrote:
> > Hi Anil / Maxime
>
> > I am also trying my hands on android..
>
> > I have also ported android on OMAP 35X (from Mistral) ..
>
> > I am getting the home screen with touchscreen working..
>
> > Now i want to move ahead with some queries :-
>
> > 1. How to enable to Network sso that i can start playing with browser ?
>
> > 2. Can I interface this board with GSM module so that i can have my call
> > working ?
>
> > 3. Is this released source code have working Bluetooth & WiFi ?? If yes then
> > what
>
> > changes  & where I need to do to make them work (this board doesn't have
> > bluetooth 7 WiFi support , I am asking for general steps )
>
> > Thanks & Regards
> > Nimit
>

> > On Thu, Nov 27, 2008 at 11:49 AM, Anil Sasidharan <anil...@gmail.com> wrote:
>
> >> Hi,
>
> >>            We have ported android-1.0 onto OMAP3EVM (from Mistral)
> >> with 2.6.26 kernel. If you are interested in getting some info/support
> >> on this, please let us know.
>
> >> Warm Regards,
> >> Anil
> >> Mistral
>
> >> Warm Regards,
> >> Anil
>

> >> On Thu, Nov 27, 2008 at 7:34 AM, kapare <kevyn.alexandre.p...@gmail.com>

[Nimit Manglick]

Hi Anil,

After adding the following settings in init.rc , my system doesn't even boots up :(

Is there any specific place in init.rc  where i should insert these settings ??

Or other than this shall I need to do anythng else..??

I am pasting the boot logs which i am getting :-

OHZ: local_softirq_pending 20
NOHZ: local_softirq_pending 20
NOHZ: local_softirq_pending 20
NOHZ: local_softirq_pending 20
NOHZ: local_softirq_pending 20
NOHZ: local_softirq_pending 20
NOHZ: local_softirq_pending 20
binder: release proc 1056, transaction 5204, not freed
NOHZ: local_softirq_pending 20
binder: release 1208:1217 transaction 7181 out, still active
binder: release 1208:1218 transaction 7191 out, still active
binder: 649:654 transaction failed 29189, size 20-4
binder: send failed reply for transaction 7191, target dead
binder: 649:649 transaction failed 29189, size 13124-0
binder: send failed reply for transaction 7181, target dead
binder: release proc 1223, transaction 7374, not freed
binder: release proc 1981, transaction 17745, not freed
binder: release proc 2127, transaction 19641, not freed
binder: release 3903:3911 transaction 43260 out, still active
binder: release 3903:3912 transaction 43288 out, still active
binder: 649:649 transaction failed 29189, size 8-0
binder: send failed reply for transaction 43288, target dead
binder: 649:655 transaction failed 29189, size 13124-0
binder: send failed reply for transaction 43260, target dead
binder: release proc 4373, transaction 49585, not freed
binder: release proc 4609, transaction 52803, not freed
binder: release proc 5667, transaction 66971, not freed
binder: release proc 6108, transaction 72815, not freed
binder: release 6658:6667 transaction 80064 out, still active
binder: release 6658:6668 transaction 80093 out, still active
binder: 649:655 transaction failed 29189, size 8-0
binder: send failed reply for transaction 80093, target dead
binder: 649:653 transaction failed 29189, size 13124-0
binder: send failed reply for transaction 80064, target dead
binder: release proc 6820, transaction 82313, not freed
binder: release proc 7729, transaction 94727, not freed
binder: release 7846:7854 transaction 96125 out, still active
binder: release 7846:7855 transaction 96135 out, still active
binder: 649:1222 transaction failed 29189, size 20-4
binder: send failed reply for transaction 96135, target dead
binder: 649:653 transaction failed 29189, size 13124-0
binder: send failed reply for transaction 96125, target dead
binder: release 8128:8137 transaction 99905 out, still active
binder: release 8128:8138 transaction 99919 out, still active
binder: 649:649 transaction failed 29189, size 48-0
binder: 649:649 transaction failed 29189, size 4-0
binder: send failed reply for transaction 99919, target dead
binder: 649:1222 transaction failed 29189, size 13124-0
binder: send failed reply for transaction 99905, target dead

Thanks & Regards
Nimit

[Anil Sasidharan]

Hello Nimit,

Yes, you got to add this at a specific place in the
init.rc as shown here:


on boot
# basic netwrok init
ifup lo
hostname localhost
domainname localdomain

setprop net.gprs.local-ip <board's-ip-address>
setprop net.dns1 <primary-dns-server-ip>
setprop net.dns2 <secondary-dns-server-ip>

Warm Regards,
Anil

[Anil Sasidharan]

Hi,

We have used linux kernel version 2.6.26 from omap GIT as
the base and applied the android patch generated out of linux kernel
2.6.25 from android GIT.

Warm Regards,
Anil

On Thu, Nov 27, 2008 at 7:47 PM, kapare <kevyn.alex...@gmail.com> wrote:
>

[Nimit Manglick]

Hi Anil,

Thanx for the info...

I got my google working now on board :)

But Is there any mechanism to type somethng in the URL ??

So that i can open other websites also.

Thanks & Regards
Nimit Manglick

[Anil Sasidharan]

Hi,

How abt using USB keyboard? Or another option is to add
bookmarks into the browser's sqlite based table. There are some
freeware tools that can be used to manipulate the entries in the table
that maintains bookmarks.

Warm Regards,
Anil

[janu0204]

Hi Anil,
This is janakiram ,i too an planning to port android on
OMAP ,but its on 2420.I required your guidance
Kindly let me know how to proceed

I am plannig to do it on Ubuntu Linux as host


but while i am trying to install the emulator i am geting error
regarding SDL.

I would also like to know from how did u proceed in porting on
anndroid if you can share me a document how you had done it will be
more helpful


regards
ram

> >> > > - Maxime- Hide quoted text -
>
> - Show quoted text -

[kapare]

Can someone gives me is .config for OMAP3 EVM

After merging the code I launch make and it ask:

Default panic timeout (PANIC_TIMEOUT) [0] (NEW)
Enable Android's Shared Memory Subsystem (ASHMEM) [N/y/?] (NEW) y
Memory device driver (DEVMEM) [Y/n/?] (NEW) y
Low Memory Killer (LOW_MEMORY_KILLER) [N/m/y/?] (NEW) y
Switch class support (SWITCH) [N/m/y/?] (NEW) y
GPIO Swith support (SWITCH_GPIO) [N/m/y/?] (NEW) y
RAM buffer console (ANDROID_RAM_CONSOLE) [N/y] (NEW) y
Enable verbose console messages (ANDROID_RAM_CONSOLE_ENABLE_VERBOSE)
[Y/n] (NEW) y
Enable error correction (ANDROID_RAM_CONSOLE_ERROR_CORRECTION) [N/y]
(NEW) y
Data data size (ANDROID_RAM_CONSOLE_ERROR_CORRECTION_DATA_SIZE) [128]
(NEW)
ECC size (ANDROID_RAM_CONSOLE_ERROR_CORRECTION_ECC_SIZE) [16] (NEW)
Symbol size (ANDROID_RAM_CONSOLE_ERROR_CORRECTION_SYMBOL_SIZE) [8]
(NEW)
Polynomial (ANDROID_RAM_CONSOLE_ERROR_CORRECTION_POLYNOMIAL)
[0x11d] (NEW)
Start ram console early (ANDROID_RAM_CONSOLE_EARLY_INIT) [N/y] (NEW)
Android log driver (ANDROID_LOGGER) [Y/n] (NEW) y
Android timed gpio driver (ANDROID_TIMED_GPIO) [Y/n] (NEW) y
Binder IPC Driver (ANDROID_BINDER_IPC) [Y/n/m] (NEW) y
Only allow certain groups to create sockets (ANDROID_PARANOID_NETWORK)
[Y/n/?] (NEW) y

I'm interested to know what are the kernel default config for Android
on OMAP3 EVM


Maybe
http://elinux.org/Android_on_OMAP#Kernel_configuration
are ok ?

Regards

kap

> > > I imagine that your demo with OMAP 3EVMand montavista src have been

> > > ship for Embedded Technology 2008 in Yokohama, Japan, November 19-21 ?
>
> > > I'm still wiondering why you used 2.6.24 and not minimally 2.6.25 or
> > > higher, since android is 2.6.25.
>
> > > I will try to go with 2.6.22.18 TI src and patch android on it!
>
> > > thx for infos
>
> > > kap
>
> > > On Nov 26, 1:45 pm, Maxime Petazzoni <maxime.petazz...@gmail.com>
> > > wrote:
> > >> Hi,
>
> > >> On 26 nov, 18:36, kapare <kevyn.alexandre.p...@gmail.com> wrote:
>
> > >> > > No, I've used MontaVista Linux 2.6.24 :http://mvista.com/press_release_detail.php?fid=news/2008/MontaVista-L...
> > >> > > , on top of which I added the Android drivers (that needed a bit of
> > >> > > work because of some differences between 2.6.25 and 2.6.24, especially
> > >> > > in sysfs).
>
> > >> > Did you get the src code from git our from support of monta vista?
>
> > >> > thx for helping a guy a bit lost!
>
> > >> I work at MontaVista, and the press release up there depicts our work
> > >> on Android. We used our kernel as the base for the Android port, so we
> > >> already have OMAP3EVM and OMAP3LDP board support. Except from small

> > >> keypad mapping changes betweenEVMand Zoom, I only had to rebuild the
> > >> kernel for the correct board to move from theEVMto Zoom. I haven't

[kapare]

Hi Anil,

I have done does steps (I'm new with git):
git clone http://source.mvista.com/gittrees/linux-omap-2.6.git

so by default the master branch is on
v2.6.28-rc6

Check arch/arm/configs
found omap3_evm_defconfig

To see other branch
git tag

So I create a branch for
git-checkout -b omap3evm-android v2.6.26

Check for omap3_evm_defconfig in arch/arm/configs
NOT THERE :((

Are these steps that you have done for v2.6.26?
If yes, how did you incorporate omap3_evm_defconfig support in
v2.6.26

Regards

kap

On Nov 28, 1:09 am, "Anil Sasidharan" <anil...@gmail.com> wrote:
> Hi,
>
>           We have used linux kernel version 2.6.26 from omap GIT as
> the base and applied the android patch generated out of linux kernel
> 2.6.25 from android GIT.
>
> Warm Regards,
> Anil
>

[Nishanth Menon]

Kapare,

On Mon, Dec 1, 2008 at 1:05 PM, kapare <kevyn.alex...@gmail.com> wrote:
> Check for omap3_evm_defconfig in arch/arm/configs
> NOT THERE :((
>
> Are these steps that you have done for v2.6.26?
> If yes, how did you incorporate omap3_evm_defconfig support in
> v2.6.26

See [1]. Essentially, you are branching off a tag where evm was not
yet supported. there is not way you'd get all the drivers even if you
pull in just the defconfig.

I dont know of any reasons why you'd want to do that.. if you are
interested in a linux kernel with OMAP support which works for
Android, see [2].

Regards,
Nishanth Menon
Ref:
[1] http://source.mvista.com/git/?p=linux-omap-2.6.git;a=history;f=arch/arm/configs/omap3_evm_defconfig;h=e42fe8cd95d5a8a1af203888c8034b826b2c5b76;hb=HEAD
[2] http://git.omapzoom.org/?p=omapkernel.git;a=summary

[kapare]

By searching on android-internals I set my .config settings to

# CONFIG_ANDROID_RAM_CONSOLE is not set
CONFIG_ANDROID_LOGGER=y
# CONFIG_ANDROID_TIMED_GPIO is not set
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_PARANOID_NETWORK=y
CONFIG_ASHMEM=y
CONFIG_DEVMEM=y
CONFIG_PANIC_TIMEOUT=0
CONFIG_LOW_MEMORY_KILLER=y
CONFIG_ANDROID_LOGGER=y
# CONFIG_SWITCH is not set

# CONFIG_ANDROID_POWER depends on PM & RTC_CLASS
#ENABLE RTC_CLASS
CONFIG_RTC_CLASS=y
#NEW QUESTION ARE DISPLAY AND SET:
CONFIG_ANDROID_POWER=y
CONFIG_ANDROID_POWER_ALARM=y
CONFIG_ANDROID_POWER_STAT=y


kap

> Maybehttp://elinux.org/Android_on_OMAP#Kernel_configuration

[kapare]

Nishanth,

Thx,

So I have multiple choice can you recommend the one that is the more
stable for omap3evm?:

android-2.6.26-1.0-2?

Regards
kap

On Dec 1, 2:17 pm, "Nishanth Menon" <menon.nisha...@gmail.com> wrote:

> Kapare,On Mon, Dec 1, 2008 at 1:05 PM, kapare <kevyn.alexandre.p...@gmail.com> wrote:
> > Check for omap3_evm_defconfig in arch/arm/configs
> > NOT THERE :((
>
> > Are these steps that you have done for v2.6.26?
> > If yes, how did you incorporate  omap3_evm_defconfig support in
> > v2.6.26
>
> See [1]. Essentially, you are branching off a tag where evm was not
> yet supported. there is not way you'd get all the drivers even if you
> pull in just the defconfig.
>
> I dont know of any reasons why you'd want to do that.. if you are
> interested in a linux kernel with OMAP support which works for
> Android, see [2].
>
> Regards,
> Nishanth Menon
> Ref:

> [1]http://source.mvista.com/git/?p=linux-omap-2.6.git;a=history;f=arch/a...
> [2]http://git.omapzoom.org/?p=omapkernel.git;a=summary

[Nishanth Menon]

On Mon, Dec 1, 2008 at 2:29 PM, kapare <kevyn.alex...@gmail.com> wrote:
> So I have multiple choice can you recommend the one that is the more
> stable for omap3evm?:
>
> android-2.6.26-1.0-2?

I would like to say [1], but I dont use EVM :(. You may want to
discuss on linux-omap mailing list[2] to get more details.
Regards,
Nishanth Menon

Ref:
[1] http://source.mvista.com/git/?p=linux-omap-2.6.git
[2] http://vger.kernel.org/vger-lists.html#linux-omap

[Nimit Manglick]

Hi Kapare,

Please find attached the .config for OMAP 35EVM.

Regards
Nimit

[Nimit Manglick]

Hi All,

Has anyone tried the Voice / data call on OMAP 3503EVM ??

It doesn't have any direct RF modem but we need to interface it with some additional RF modem hardware, Can anyone suggest which can be the best hardware modem to do so ??

What is the procedure to make a call out of it ??

Secondly I have put some media files on SD card (audio + video - mpeg + wmv format)
Media player is able to play the audio file but i am not able to hear any sound :(

So where i need to change in the hardware so that i will be able to listen music ?? But the media player is not even detecting any of the video files ..

So anyone please help me.

Thanks & Regards
Nimit Manglick

[Anil Sasidharan]

twebb,

Please see my answers in-lined.............

> Anil,
> Hope you don't mind me contacting you directly. We actually own a
> Mistral OMAP35x EVM board and I've gotten android running on it.
> However I'm running into an issue or two that maybe you can help with.
>
> 1. I've only run with a filesystem that was extracted from the
> android emulator, mounted via NFS or YAFFS2. No problems. However, I
> now have built the android source and want to run with the "built"
> filesystem, but I'm having problems. On startup, either init function
> says it can't find files on /data or /system, or (if I mess around
> alot with permissions/ownership) android will start but several apps
> don't run because of permissions/ownership issues. Is there any
> secret to "preparing" the source built filesystem (../out/target/
> product/generic/system and ../root and ../data) for use on an actual
> target? (I'd rather not have to "un-yaffs" the system.img and
> data.img files since I won't be using yaffs in the long run.)
>

The out/target/product/<board-name> directory contains /system, /data
and /root directories. You don't need to worry about un-yaffs the .img
files. However please make sure that the init.rc under /root directory
is modified according to your setup (especially comment out the
mounting of YAFFS2 partitions). The easy approach would be to make use
of the very same file system you already have on the NFS or SD card
and just replace the system directory alone with the one built out of
sources.

> 2. I'm also seeing an issue where I'm having an issue where D-pad key
> presses (i.e. left/right/up/down) don't seem to cause the
> screen to refresh such that the next icon is highlighted. Based on
> how the code reacts, the icon is actually active (i.e. ENTER causes it
> to launch) but just not highlighted. It seems as though every other
> key press results in the screen being refreshed (such that every other
> icon is highlighted as the directions keys are used to move around an
> array of icons on the screen). Is this a keyboard driver issue, a
> frame buffer driver issue, or something else? All other key related,
> touchscreen related, and frame buffer related functionality seems
> fine. I've modified omapfb_main.c per the "page flipping frame
> buffer" question on http://elinux.org/Android_on_OMAP. Are there
> other mods to frame buffer driver or keypad driver I need to make to
> eliminate this problem?
>

This is one of the notorious/infamous issues that I've faced while
bringing up Android on OMAP3EVM. This is an issue with the framebuffer
update. I presume you already have added support for double-buffering
in fb driver (fb_pan). The GO bit needs to be set for the shadowed
registers to take effect in hardware. Once the hardware is ready, the
GO bit will be reset. Per the hardware specifications, we should not
change any display controller registers until the GO bit is
reset.Android desktop icon-navigation problem got resolved after this
change is made in the display controller source.
For you reference the code is added here (extracted from the function
_setup_plane in drivers/video/omap/dispc.c. The source file to be
modified may change depending on the kernel version at you end :-) ):

MOD_REG_FLD(DISPC_CONTROL, 0x20, 0); /* clears and sets the GOLCD bit */
MOD_REG_FLD(DISPC_CONTROL, 0x20, 0x20);

> Thanks for your time.
> twebb
>
>
>

Warm Regards,
Anil

[Nimit Manglick]

Hi Anil,

Can you give me some pointers on my previous query on 35x EVM

I have put some media files on SD card (audio + video - mpeg + wmv format + 3gp)

Media player is able to play the audio file but i am not able to hear any sound :(

So where i need to change in the hardware so that i will be able to listen music ?? But the media player is not even detecting any of the video files ..

Thanks & Regards
Nimit

[Anil Sasidharan]

Hi Nimit,

Have you integrated the ALSA audio support into Android HAL?
Or is it another sound support being added there (OSS, ESD, custom)?
Do you see the media files listed (scanned and enumerated by media
scanner)?

Warm Regards,
Anil

[Nimit Manglick]

Hi Anil,

I am now trying to compile alsa using android tool chain but i am not getting success.

Secondly i also tried to compile it using another  arm-eabi toolchain but there also my alsa-utils are not getting compiled.

Regards
Nimit

[Anil Sasidharan]

Hi,

This has already been done by Windriver and TI. You will be
able to get the sources from http://android.git.kernel.org/ (ASLA lib
and HAL ported by Windriver) or from http://git.omapzoom.org.
Integration is pretty straightforward.

Warm Regards,
Anil

[Nimit Manglick]

Hi Anil,

Can you please tell me which all packages shall i need to check out.

1. external/alsa-lib.git

2. hardware/alsa_sound.git

Other than this shall I need to check out any other package ?

But i didn't found the alsa-utils package ? As i want aplay, amixer utilities as well.

What else is required to integrate ?

I am just doing the "make" in root directory so taht i wwill have my new file system with

alsa libs. Will mount this new filesystem.

[Nimit Manglick]

Hi Anil,

Can you please tell me which all packages shall i need to check out.

1. external/alsa-lib.git

2. hardware/alsa_sound.git

Other than this shall I need to check out any other package ?

But i didn't found the alsa-utils package ? As i want aplay, amixer utilities as well.

What else is required to integrate ?

I am just doing the "make" in root directory so taht i wwill have my new file system with

alsa libs. Will mount this new filesystem.

Thanks & Regards
Nimit

On Wed, Dec 17, 2008 at 6:54 PM, Anil Sasidharan <ani...@gmail.com> wrote:

[Rupesh Gujare]

Nimit,
  We have already successfully tested sound on beagle (OMAP3530) .
You can go through following how to for more details:-
http://labs.embinux.org/android-porting-on-beagle.html

Regards,
Rupesh Gujare
http://embinux.com

-- 
Rupesh Gujare
Engineer- Embedded Software
Embedded and Telecommunication
SQLStar International Limited
Phone: +91 40 2310 1669
email address : rupesh...@embinux.com,
rupesh...@sqlstar.com

[Nimit Manglick]

Hi Anil / Rupesh,

I am getting the following errors after doing a check out of alsa-lib & while doing "make"

in the top source directory.


out/target/product/generic/obj/STATIC_LIBRARIES/libasound_intermediates/libasound.a(input.o): In function `snd_input_buffer_scan':
external/alsa-lib/src/input.c:245: undefined reference to `vsscanf'
collect2: ld returned 1 exit status
make: *** [out/target/product/generic/obj/SHARED_LIBRARIES/libaudio_intermediates/LINKED/libaudio.so] Error 1

Thanks & Regards
Nimit

[Rupesh Gujare]

Nimit,
  Did you followed all steps given on :-
http://labs.embinux.org/android-porting-on-beagle.html

  You are required to apply patches to Android build, to make sound work.

Regards,

-- 
Rupesh Gujare
http://embinux.com

Regards,

[Nimit Manglick]

Hi Rupesh,

Ya now i am following all the steps. I have applied the patches .

But If you can see the new file added in libc/arch-arm/bionic/ffs.S, there is an empty

#include i.e there is no filename mentioned there.

Can you please verify it and let me know.

Thanks & Regards
Nimit

[Nimit Manglick]

Hi Rupesh,

Its compiling now. In your patch the filename is there.

Thanks

Nimit

[Nimit Manglick]

Hi Anil,

can you please share the keypad mapping of 3530 EVM

Regards
Nimit

[kapare]

1- Go to minicom console and run getevent&


2- Click on keypad buttons of OMAP35xx EVM and you will see something
like that:

/dev/input/event0: 0001 006a 00000001
/dev/input/event0: 0001 006a 00000000


3- This mean that the hexadecemal value for the key pressed is 6A.


4- Convert that value to decimal 106.


5- Edit /system/usr/keylayout/qwerty.kl and map with the current
OMAP35xx EVM keypad.


6- Here from OMAP35xx EVM keypad from left(next to SD slot) to right
(serial port) and from top(screen) to bottom(power connector) Map of
OMAP35xx EVM keypad "Hexa(Dec)":

19(25) 18(24) 31(49) 25(37) 24(36)

17(23) 1C(28) 21(33) 12(18) 67(103)

6C(108) 30(48) 1E(30) 6A(106) 69(105)


7- Edit /system/usr/keylayout/qwerty.kl like that:

key 25 HOME WAKE_DROPPED

key 24 DPAD_UP WAKE_DROPPED

key 49 BACK WAKE_DROPPED

key 37 MENU WAKE_DROPPED

key 36 A WAKE_DROPPED

key 23 DPAD_LEFT WAKE_DROPPED

key 28 DPAD_CENTER WAKE_DROPPED

key 33 DPAD_RIGHT WAKE_DROPPED

key 18 VOLUME_UP

key 103 B WAKE_DROPPED

key 108 CALL WAKE_DROPPED

key 48 DPAD_DOWN WAKE_DROPPED

key 30 ENDCALL WAKE_DROPPED

key 106 VOLUME_DOWN WAKE_DROPPED

key 105 C WAKE_DROPPED

Regards

kap

On Dec 19, 12:21 am, "Nimit Manglick" <nimitandr...@gmail.com> wrote:
> Hi Anil,
>
> can you please share the keypad mapping of 3530 EVM
>
> Regards
> Nimit
>

> On Thu, Dec 18, 2008 at 12:15 PM, Nimit Manglick <nimitandr...@gmail.com>wrote:
>
> > Hi Rupesh,
>
> > Its compiling now. In your patch the filename is there.
>
> > Thanks
>
> > Nimit
>

> > On Thu, Dec 18, 2008 at 12:10 PM, Nimit Manglick <nimitandr...@gmail.com>wrote:
>
> >> Hi Rupesh,
>
> >> Ya now i am following all the steps. I have applied the patches .
>
> >> But If you can see the new file added in libc/arch-arm/bionic/ffs.S, there
> >> is an empty
>
> >> #include i.e there is no filename mentioned there.
>
> >> Can you please verify it and let me know.
>
> >> Thanks & Regards
> >> Nimit
>
> >> On Thu, Dec 18, 2008 at 12:01 PM, Rupesh Gujare <
> >> rupesh.guj...@embinux.com> wrote:
>
> >>>  Nimit,
> >>>   Did you followed all steps given on :-
> >>>http://labs.embinux.org/android-porting-on-beagle.html
>
> >>>   You are required to apply patches to Android build, to make sound work.
>
> >>> Regards,
>
> >>> --

> >>> Rupesh Gujarehttp://embinux.com

> >>>> On Wed, Dec 17, 2008 at 6:54 PM, Anil Sasidharan <anil...@gmail.com>wrote:
>
> >>>>> Hi,
>
> >>>>>          This has already been done by Windriver and TI. You will be

> >>>>> able to get the sources fromhttp://android.git.kernel.org/(ASLA lib
> >>>>> and HAL ported by Windriver) or fromhttp://git.omapzoom.org.

> >>>>> Integration is pretty straightforward.
>
> >>>>> Warm Regards,
> >>>>> Anil
>
> >>>>> On Wed, Dec 17, 2008 at 4:35 PM, Nimit Manglick <
> >>>>> nimitandr...@gmail.com> wrote:
> >>>>> > Hi Anil,
>
> >>>>> > I am now trying to compile alsa using android tool chain but i am not
> >>>>> > getting success.
>
> >>>>> > Secondly i also tried to compile it using another  arm-eabi toolchain
> >>>>> but
> >>>>> > there also my alsa-utils are not getting compiled.
>
> >>>>> > Regards
> >>>>> > Nimit
>

> >>>>> > On Wed, Dec 17, 2008 at 11:54 AM, Anil Sasidharan <anil...@gmail.com>

> >>>>> wrote:
>
> >>>>> >> Hi Nimit,
>
> >>>>> >>          Have you integrated the ALSA audio support into Android
> >>>>> HAL?
> >>>>> >> Or is it another sound support being added there (OSS, ESD, custom)?
> >>>>> >> Do you see the media files listed (scanned and enumerated by media
> >>>>> >> scanner)?
>
> >>>>> >> Warm Regards,
> >>>>> >> Anil
>
> >>>>> >> On Wed, Dec 17, 2008 at 11:01 AM, Nimit Manglick <

> >>>>> nimitandr...@gmail.com>

> >>>>> >> wrote:
> >>>>> >> > Hi Anil,
>
> >>>>> >> > Can you give me some pointers on my previous query on 35x EVM
>
> >>>>> >> > I have put some media files on SD card (audio + video - mpeg + wmv
> >>>>> >> > format +
> >>>>> >> > 3gp)
> >>>>> >> > Media player is able to play the audio file but i am not able to
> >>>>> hear
> >>>>> >> > any
> >>>>> >> > sound :(
>
> >>>>> >> > So where i need to change in the hardware so that i will be able
> >>>>> to
> >>>>> >> > listen
> >>>>> >> > music ?? But the media player is not even detecting any of the
> >>>>> video
> >>>>> >> > files
> >>>>> >> > ..
>
> >>>>> >> > Thanks & Regards
> >>>>> >> > Nimit
>
> >>>>> >> > On Wed, Dec 17, 2008 at 10:46 AM, Anil Sasidharan <

> >>>>> anil...@gmail.com>

> >>>>> >> >> > buffer" question onhttp://elinux.org/Android_on_OMAP.  Are

> ...
>
> read more »

[vishal bhoj]

Kapare,


I have got Android running on omap3evm ,Keypad is working fine. I am having problem with the touchscreen. the touch are recognised ans the top bar (date and time) slides and goes back . how can i get touchscreen running on android ?

--
with regards vishal

[Nimit Manglick]

Hi Kapare,

Thanks for ur reply and sorry for late replying..

So my status is :- I tried with ur suggestions but still my MENU key is not getting

mapped :(

Thanks & Regards
Nimit

[vishal bhoj]

NIMIT,


remove WAKE_DROPPED from the keys and try, worked for me . with the default mapping are you getting some characters when you press key ?

--
with regards vishal

[vishal bhoj]

NIMIT,

how did you get the touch screen working ?

--
with regards vishal

[Nimit Manglick]

Hi Bhoj,

I didn't do anything specific with touchscreen. I was having my kernel ready with

touchscreen support and my things got up.

Regards
Nimit

[vishal bhoj]

Nimit ,

Is it ? CAn you please check and tell me if the driver is ads7846 ?
Did the keypad work for you ?

--
with regards vishal

[vishal bhoj]

Nimit,

Which karnel are you using ?

--
with regards vishal

[hzy.spe...@gmail.com]

Android is more popular now, how could I join with you?
Is there any how-to to follow?



Thanks

[Nimit Manglick]

Vishal,

I have my own customized kernel with android patch on top of it.

Yes keypad worked for me but only few keys as i told u earlier also.

Thanks
Nimit

[Nimit Manglick]

There are flood of documents available on internet to start off with.

Some links are :-

http://code.google.com/android/intro/index.html

http://elinux.org/Android_on_OMAP

https://omapzoom.org/gf/project/omapandroid/wiki/?pagename=Installing+the+System

Thanks
Nimit

On Fri, Jan 16, 2009 at 3:47 PM, hzy.spe...@gmail.com <hzy.spe...@gmail.com> wrote:

[divya]

Hi Nimit,

Have you tried adb with ur OMAP Board.If yes can you update me.
I am using a tcp ip connection using a windows host and OMAP 3430 SDP.

Waiting for ur reply...

Regards,
Divya

[Nimit Manglick]

Hi Divya,

No i haven't tried anything using adb..

Bye t way why r u looking for adb..?? After booting android

u will get the console itself na...

Anyways sorry no idea :(

Regards
Nimit

[vishal bhoj]

Hi Divya ,


Even I tried to connect through adb but I could not. When i do a adb devices it doesn't list anything. The adbd demon is running on the traget device . If you are able to connect on zoom please update me .

thanks in advance

--
with regards vishal

[Sean McNeil]

It is very simple:

First, make sure you have connectivity to the zoom. Ping the ip address.
Next, type the command as follows (with appropriate changes):

ADBHOST=ip_address adb kill-server
ADBHOST=ip_address adb shell

If using ethernet over usb, the zoom/OMAP USB gadget driver has an odd
requirement. When you use ifconfig to setup the ip address on the zoom,
you have to specify "up" on the ifconfig command. So in init.rc you'd
have something like:

## Configure the USB interface
##
service usb-ether /system/bin/ifconfig usb0 192.168.0.202 up
oneshot

If you are using the ethernet port, then you'll have to set it up
appropriately. Again, if you can ping you should be OK.

Cheers,
Sean

[vishal bhoj]

Thanks Sean,

It works now :)

--
with regards vishal

[divya]

Hi vishal,

I am still having some problem with this.I checked my init.rc but
the above line isnt present in it.And what is this ip "192.168.0.202
".

Can you share ur init.rc script file.

And this you are able to work on windows system....right?

Regards,
Divya

> > >     On Wed, Jan 21, 2009 at 8:33 PM, divya <pdiv...@gmail.com

> > >     <mailto:pdiv...@gmail.com>> wrote:
>
> > >         Hi Nimit,
>
> > >          Have you tried adb with ur OMAP Board.If yes can you update me.
> > >         I am using a tcp ip connection using a windows host and OMAP
> > >         3430 SDP.
>
> > >         Waiting for ur reply...
>
> > >         Regards,
> > >         Divya
>
> > > --
> > > with regards vishal
>
> --

> with regards vishal- Hide quoted text -
>
> - Show quoted text -

[vishal bhoj]

Divya,


I am using a linux host machine, That ip is for network over USB (not sure ).I din't modify my initrc file. I hope 3430sdp has a ethernet port . Can you ping to ur board ? I mean is your network up ? if not try this

setprop net.dns1 <primary-dns-server-ip> 
$netcfg eth0 up
$netcfg eth0 dhcp

After this try to ping and then follow Sean's procedure .

--
with regards vishal

[pavan savoy]

Does this help anymore than having telnetd running on board ? I mean what could a adb shell do, which cannot be done by say a normal shell ?

Just curious !!

[divya]

Vishal,

I am able to ping to my board ..But the lines with is suggested by
Sean and you is not present in my init.rc file.

Can you just share ur init.rc file.

Actually my requirement is to use both the linux and windows system.
Just trying with the windows system first.

Do you use minicom as hyperterminal in linux.. or something else?

Regards,
Divya

[vishal bhoj]

Divya,

The lines which i have typed should be typed thru ur hyperterminal when android kernel boots . you can add these lines in init.rc file.  what Sean suggested is for emulating ethernet over USB like RNDIS.  I have not tried on windows.


intrc scriptloglevel 3
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
    mount tmpfs tmpfs /sqlite_stmt_journals size=4m

#    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 mtd@system /system
#    mount yaffs2 mtd@system /system ro remount

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

    # Same reason as /data above
#    mount yaffs2 mtd@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

    # double check the perms, in case lost+found already exists, and set owner
    chown root root /data/lost+found
    chmod 0770 /data/lost+found
    chown root root /cache/lost+found
    chmod 0770 /cache/lost+found

on boot
# basic network init
    ifup lo
    hostname localhost
    domainname localdomain

# set RLIMIT_NICE to allow priorities from 19 to -20
    setrlimit 13 40 40

# Define the oom_adj values for the classes of processes that can be
# killed by the kernel.  These are used in ActivityManagerService.
    setprop ro.FOREGROUND_APP_ADJ 0
    setprop ro.VISIBLE_APP_ADJ 1
    setprop ro.SECONDARY_SERVER_ADJ 2
    setprop ro.HIDDEN_APP_MIN_ADJ 7
    setprop ro.CONTENT_PROVIDER_ADJ 14
    setprop ro.EMPTY_APP_ADJ 15

# Define the memory thresholds at which the above process classes will
# be killed.  These numbers are in pages (4k).
    setprop ro.FOREGROUND_APP_MEM 1536
    setprop ro.VISIBLE_APP_MEM 2048
    setprop ro.SECONDARY_SERVER_MEM 4096
    setprop ro.HIDDEN_APP_MEM 5120
    setprop ro.CONTENT_PROVIDER_MEM 5632
    setprop ro.EMPTY_APP_MEM 6144

# Write value must be consistent with the above properties.
    write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15

    write /proc/sys/vm/overcommit_memory 1
    write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144

    # Set init its forked children's oom_adj.
    write /proc/1/oom_adj -16

    # Permissions for System Server and daemons.
    chown radio system /sys/android_power/state
    chown radio system /sys/android_power/request_state
    chown radio system /sys/android_power/acquire_full_wake_lock
    chown radio system /sys/android_power/acquire_partial_wake_lock
    chown radio system /sys/android_power/release_wake_lock
    chown radio system /sys/power/state
    chown radio system /sys/power/wake_lock
    chown radio system /sys/power/wake_unlock
    chmod 0660 /sys/power/state
    chmod 0660 /sys/power/wake_lock
    chmod 0660 /sys/power/wake_unlock
    chown system system /sys/class/timed_output/vibrator/enable
    chown system system /sys/class/leds/keyboard-backlight/brightness
    chown system system /sys/class/leds/lcd-backlight/brightness
    chown system system /sys/class/leds/button-backlight/brightness
    chown system system /sys/class/leds/red/brightness
    chown system system /sys/class/leds/green/brightness
    chown system system /sys/class/leds/blue/brightness
    chown system system /sys/class/leds/red/device/grpfreq
    chown system system /sys/class/leds/red/device/grppwm
    chown system system /sys/class/leds/red/device/blink
    chown system system /sys/class/leds/red/brightness
    chown system system /sys/class/leds/green/brightness
    chown system system /sys/class/leds/blue/brightness
    chown system system /sys/class/leds/red/device/grpfreq
    chown system system /sys/class/leds/red/device/grppwm
    chown system system /sys/class/leds/red/device/blink
    chown system system /sys/class/timed_output/vibrator/enable
    chown system system /sys/module/sco/parameters/disable_esco
    chown system system /sys/kernel/ipv4/tcp_wmem_min
    chown system system /sys/kernel/ipv4/tcp_wmem_def
    chown system system /sys/kernel/ipv4/tcp_wmem_max
    chown system system /sys/kernel/ipv4/tcp_rmem_min
    chown system system /sys/kernel/ipv4/tcp_rmem_def
    chown system system /sys/kernel/ipv4/tcp_rmem_max
    chown root radio /proc/cmdline

# Define TCP buffer sizes for various networks
#   ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
    setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
    setprop net.tcp.buffersize.wifi    4095,87380,110208,4096,16384,110208
    setprop net.tcp.buffersize.umts    4094,87380,110208,4096,16384,110208
    setprop net.tcp.buffersize.edge    4093,26280,35040,4096,16384,35040
    setprop net.tcp.buffersize.gprs    4092,8760,11680,4096,8760,11680
    setprop net.dns1 192.168.1.1
    class_start default

## Daemon processes to be run by init.
##
service console /system/bin/sh
    console

# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
    disabled

# adbd on at boot in emulator
on property:ro.kernel.qemu=1
    start adbd

on property:persist.service.adb.enable=1
    start adbd

on property:persist.service.adb.enable=0
    stop adbd

service servicemanager /system/bin/servicemanager
    user system
    critical
    onrestart restart zygote
    onrestart restart media

service mountd /system/bin/mountd
    socket mountd stream 0660 root mount

service debuggerd /system/bin/debuggerd

service ril-daemon /system/bin/rild
    socket rild stream 660 root radio
    socket rild-debug stream 660 radio system
    user root
    group radio cache inet misc

service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
    socket zygote stream 666
    onrestart write /sys/android_power/request_state wake
    onrestart write /sys/power/state on

service media /system/bin/mediaserver
    user media
    group system audio camera graphics inet net_bt net_bt_admin

service bootsound /system/bin/playmp3
    user media
    group audio
    oneshot

service dbus /system/bin/dbus-daemon --system --nofork
    socket dbus stream 660 bluetooth bluetooth
    user bluetooth
    group bluetooth net_bt_admin

#STOPSHIP: disable the verbose logging
service hcid /system/bin/logwrapper /system/bin/hcid -d -s -n -f /etc/bluez/hcid.conf
    socket bluetooth stream 660 bluetooth bluetooth
    socket dbus_bluetooth stream 660 bluetooth bluetooth
    # init.rc does not yet support applying capabilities, so run as root and
    # let hcid drop uid to bluetooth with the right linux capabilities
    group bluetooth net_bt_admin misc
    disabled

service hfag /system/bin/sdptool add --channel=10 HFAG
    user bluetooth
    group bluetooth net_bt_admin
    disabled
    oneshot

service hsag /system/bin/sdptool add --channel=11 HSAG
    user bluetooth
    group bluetooth net_bt_admin
    disabled
    oneshot

service installd /system/bin/installd
    socket installd stream 600 system system

#service flash_recovery /system/bin/flash_image recovery /system/recovery.img
#    oneshot

--
with regards vishal

[vishal bhoj]

Divya ,

Did it help ? Why wre you trying it on windows?

--
with regards vishal

[divya]

Vishal,

I havent tried as yet.Will try and tell you.The reason for doing on
windows is becoz I have been asked to do on both linux and windows
host.

Just one thing.Is there any specific hyperterminal for linux host like
minicom?I had read it somewhere.What do you use?I am not sure thats y
I am asking.

Regards,
Divya

On Feb 6, 11:19 am, vishal bhoj <vishalb...@gmail.com> wrote:
> Divya ,
>
> Did it help ? Why wre you trying it on windows?
>

> On Thu, Feb 5, 2009 at 9:03 AM, vishal bhoj <vishalb...@gmail.com> wrote:
> > Divya,
>
> > The lines which i have typed should be typed thru ur hyperterminal when
> > android kernel boots . you can add these lines in init.rc file.  what Sean
> > suggested is for emulating ethernet over USB like RNDIS.  I have not tried
> > on windows.
>
> > intrc scriptloglevel 3
> > 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/fram­ework.jar:/system/framework/android.policy.jar:/system/framework/services.j­ar

[Nimit Manglick]

Hi Divya

On Linux you can use "minicom" as well as "kermit" package also which is also conterpart
of hyperterminal in windows.

Regards
Nimit

[divya]

Thanks Nimit,

Which one is better for use.

Regards,
Divya

On Feb 6, 1:46 pm, Nimit Manglick <nimitandr...@gmail.com> wrote:
> Hi Divya...
>
> read more »

> > /system/framework/core.jar:/system/framework/ext.jar:/system/framework/fram­­ework.jar:/system/framework/android.policy.jar:/system/framework/services.­j­ar

> > > > service media- Hide quoted text -

[divya]

Hi,

Can you tel me the site from which i can download it.

Regards,
Divya

> > > /system/framework/core.jar:/system/framework/ext.jar:/system/framework/fram­­­ework.jar:/system/framework/android.policy.jar:/system/framework/services­.­j­ar

> > > > >     user- Hide quoted text -
>
> - Show quoted text -...
>
> read more »

[vishal bhoj]

on ubuntu use apt-get install . on fedora use yum on cmd prompt

--
with regards vishal

[pavan savoy]

cutecom is the best !!!

[Nimit Manglick]

Divya,

Its upto you which one you want to use.

But minicom is most common and popular option.

For kermit refer the link :-

http://www.columbia.edu/kermit/ck80.html

Regards
Nimit

[Abhishek Srivastav]

Hello Everyone,

I am trying to boot android in our Custom board. This board is very
similar to that of OMAP3EVM from Mistral.

But when I attempt to boot I am getting a Kernel panic while executing
init ie init=/init. I am able to boot the Kernel when I change init
the bootargs ie init=/system/bin/sh, but after this when I attempt to
run init, I am getting a segmentation fault. On analyzing this through
strace command I have observed that it is not able to open the node /
dev/ashmem but the same has been enabled in the Kernel configuration.

# strace init
execve("/init", ["init"], [/* 4 vars */]) = 0
gettid() = 287
syscall_983045(0xbeaead84, 0, 0x40, 0, 0xbeacb000, 0xbeaeaec0,
0xbeaeae84, 0xf00
05, 0, 0, 0, 0, 0, 0xbeaead68, 0x12e07, 0x1926c, 0x60000010,
0xbeaead84, 0xb9f1,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
open("/dev/urandom", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file
or director
y)
sigaction(SIGCHLD, {0x88c1, [], SA_NOCLDSTOP}, NULL, 0) = 0
umask(0) = 022
mkdir("/dev", 0755) = -1 EEXIST (File exists)
mkdir("/proc", 0755) = -1 EEXIST (File exists)
mkdir("/sys", 0755) = -1 EEXIST (File exists)
mount("tmpfs", "/dev", "tmpfs", 0, 0x1c034) = 0
mkdir("/dev/pts", 0755) = 0
mkdir("/dev/socket", 0755) = 0
mount("devpts", "/dev/pts", "devpts", 0, 0) = 0
mount("proc", "/proc", "proc", 0, 0) = -1 EBUSY (Device or resource
busy)
mount("sysfs", "/sys", "sysfs", 0, 0) = -1 EBUSY (Device or resource
busy)
mknod("/dev/__null__", S_IFCHR|0600, makedev(1, 3)) = 0
open("/dev/__null__", O_RDWR|O_LARGEFILE) = 3
unlink("/dev/__null__") = 0
dup2(3, 0) = 0
dup2(3, 1) = 1
dup2(3, 2) = 2
close(3) = 0
mknod("/dev/__kmsg__", S_IFCHR|0600, makedev(1, 11)) = 0
open("/dev/__kmsg__", O_WRONLY|O_LARGEFILE) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
unlink("/dev/__kmsg__") = 0
open("/init.rc", O_RDONLY|O_LARGEFILE) = 4
lseek(4, 0, SEEK_END) = 8687
lseek(4, 0, SEEK_SET) = 0
brk(0) = 0x23000
brk(0x23000) = 0x23000
brk(0x26000) = 0x26000
read(4, "\non init\n\nsysclktz 0\n\nloglevel 3"..., 8687) = 8687
close(4) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x40
000000
mprotect(0x40000000, 4096, PROT_READ) = 0
fstat64(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(1, 3), ...}) = 0
brk(0x27000) = 0x27000
mprotect(0x40000000, 4096, PROT_READ|PROT_WRITE) = 0
mprotect(0x40000000, 4096, PROT_READ) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbeaea840) = -1 ENOTTY (Not a
typewrite
r)
brk(0x28000) = 0x28000
open("/proc/cmdline", O_RDONLY|O_LARGEFILE) = 4
read(4, "console=ttyS0,115200n8 noinitrd "..., 1023) = 112
close(4) = 0
chmod("/proc/cmdline", 0440) = 0
open("/proc/cpuinfo", O_RDONLY|O_LARGEFILE) = 4
read(4, "Processor\t: ARMv7 Processor rev "..., 1023) = 744
close(4) = 0
open("/init.omap3.rc", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file
or direct
ory)
getpid() = 287
mq_notify(0x10, 0x2) = -1 ENOSYS (Function not
implemented)
open("/dev/ashmem", O_RDWR|O_LARGEFILE) = -1 ENOENT (No such file or
directory)
open("/default.prop", O_RDONLY|O_LARGEFILE) = 4
lseek(4, 0, SEEK_END) = 93
lseek(4, 0, SEEK_SET) = 0
read(4, "#\n# ADDITIONAL_DEFAULT_PROPERTIE"..., 93) = 93
close(4) = 0
--- SIGSEGV (Segmentation fault) @ 0 (20) ---
+++ killed by SIGSEGV +++
# ls

Please help me regarding this

Thanks in advance!!!

Regards,
Abhishek Srivastav

[vishal bhoj]

have u checked with the permissions o f the filesystem ? R u booting over nfs or sdcard?

--
with regards vishal

[Abhishek Srivastav]

Hi Vishal,

Thanks a lot for your reply....
Now I am able to boot the android.
It was a Kernel configuration problem (Message queue support was not
enabled ).

But still I am not able to reach the android menuscreen(Currently the
screen displays the android images with android logo).

On analyzing this logcat command, I have found that it is continuously
trying to load the audio libraries.

Please help me in disabling this.

The tail log of logcat and strace commands are pasted below.

strace:
=======
timer_delete(0x1) = 0
futex(0x4000b220, FUTEX_WAKE, 2147483647) = 0
futex(0x40009004, FUTEX_WAKE, 2147483647) = 0
futex(0x4000b0a0, FUTEX_WAKE, 2147483647) = 0
futex(0x40009004, FUTEX_WAKE, 2147483647) = 0
wait4(-1, 0xbef27ac0, WNOHANG, NULL) = 0
timer_delete(0x1) = 0
timer_delete(0x1) = 0
timer_delete(0x1) = 0
timer_delete(0x1) = 0
poll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8,
events=POLLIN}], 3, 5
000) = ? ERESTART_RESTARTBLOCK (To be restarted)
--- SIGCHLD (Child exited) @ 0 (0) ---
write(7, "\21", 1) = 1
sigreturn() = ? (mask now [])
timer_delete(0x1) = 0
timer_delete(0x1) = 0
timer_delete(0x1) = 0
timer_delete(0x1) = 0
poll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8,
events=POLLIN, revent
s=POLLIN}], 3, 5000) = 1
read(8, "\21", 92) = 1
wait4(-1, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGTERM}], WNOHANG, NULL)
= 721
--- SIGILL (Illegal instruction) @ 0 (0) ---
+++ killed by SIGILL +++
# <3>init: untracked pid 726 exited
init: untracked pid 726 exited

logcat
======
>export DRM_CONTENT=/data/drm/content
00000000
I/DEBUG ( 481): bed75ad0 00000000
I/DEBUG ( 481): bed75ad4 bed75ae0 [stack]
I/DEBUG ( 481): bed75ad8 ab716388 /system/lib/libaudio.so
I/DEBUG ( 481): bed75adc ab715f34 /system/lib/libaudio.so
I/ServiceManager( 499): Waiting for sevice media.audio_flinger...
W/AudioSystem( 499): AudioFlinger not published, waiting...
I/ServiceManager( 499): Waiting for sevice media.audio_flinger...
I/ServiceManager( 499): Waiting for sevice media.audio_flinger...
Õ

Thanks and Regards,
Abhishek Srivastav

[Nimit Manglick]

How you are mounting the RFS ? via SD card or NFS ?

Are you using the already used filesystem via NFS means if you try to use

teh RFs which you have already mounted via NFS then you have to delete soem fiels from it

before using the same RFs via SD card.

[Abhishek Srivastav]

Hi Nimit,

I am using the filesystem mounted on SD card. This filesystem being
used is a fresh one ie it was never mounted on using NFS.
I got this filesystem from the beagle website ie http://www.embinux.com/download_beagle.php.

If possible can you please send me the final image on the LCD screen
once the android boots up.

Please help me in solving this issue.

Thanks and Regards,
Abhishek Srivastav

On Feb 24, 12:17 pm, Nimit Manglick <nimitandr...@gmail.com> wrote:
> How you are mounting the RFS ? via SD card or NFS ?
>
> Are you using the already used filesystem via NFS means if you try to use
>
> teh RFs which you have already mounted via NFS then you have to delete soem
> fiels from it
>
> before using the same RFs via SD card.
>
> On Tue, Feb 24, 2009 at 12:36 PM, Abhishek Srivastav <
>

[Nishanth Menon]

Abhishek,
I suggest you discuss this on beagleboard mailing list:
beagl...@googlegroups.com
Regards,
Nishanth Menon
Abhishek Srivastav said the following on 02/24/2009 10:10 AM:

[Nimit Manglick]

Thats a working RFS. I have tested it on EVM.

But that filesystem doesn't have audio support.

So you have to integrate alsa in ur android and make ur own filesystem.

[Nimit Manglick]

Ohh.. I think thats the latest RFS.

Follow the instructions from 

http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

[Abhishek Srivastav]

Thanks Nimit!!!!!

Can you please confirm whether the android menuscreen was coming or
not with the default file system .... and whether is it possible to
disable the audio support(i.e It seems that sevice manager is waiting
for some audio libraries.)

[vishal bhoj]

in ur case the alsa is failing , and hence audioflinger is not setup and it restarts  .
if u follow the discrpition given in
http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board

6- Add ALSA audio support to the board config file and comment out generic audio support.
$vim ~/android_build/build/target/board/generic/BoardConfig.mk
add BOARD_USES_ALSA_AUDIO := true 
#BOARD_USES_GENERIC_AUDIO := true

change it to

BOARD_USES_GENERIC_AUDIO := true

and build it . This should solve ur problem. but  try to add alsa support later

--
with regards vishal

[Abhishek Srivastav]

Thanks Vishal and Nimit !!!!

Now I am able to boot the android and get the android menu screen, but
now I am not able to test the TouchScreen.
I have ensured that Touchscreen controller driver is working fine.
We are getting the proper interrupts when we are accessing the screen
(confirmed this by viewing the interrupt count states from /proc/
interrupts).

Am I missing some TS specific configuration for android in Kernel???

Please help me out in this.

Thanks in advance !!!!

Regards,
Abhishek Srivastav

[Abhishek Srivastav]

Hello Everyone,

I have ported android on my custom board which is similar to OMAP3EVM.
There are a few issues which I am facing

1) I am successfully able to play the audio files(.mp3) in ANDROID but
once I pause and play again, I am not able to hear anything. On
viewing the log messages, it seems that there is some buffer overfolw.
On googling this, I find this is due to some bug in the ALSA driver.
Please help me out in fixing this.

2) I have been playing the audio files by copying it in SD card
playing it from there, but when I follow the similar steps for video
files. I am not able to play the same.

Please help me out in solving these issues.

Thanks & Regards,
Abhishek Srivastav

[anantvijayk]

hi,

I have OMAP3EVM with the kernel and root filesystem from the mistral's
site. the device is up and everything works fine.

The device is connected through ethernet port on board. The target
device has an ip assigned and is reachable by the other machines.

I'm trying to run adb over ethernet.

My pc ip: 192.168.102.130
My device ip: 192,168.101.56

Here are the steps i ran from my pc:
# ADBHOST=192.168.101.56 adb kill-server
# ADBHOST=192.168.101.56 adb shell

output:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

Also the netstat on the target device gave me this:
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp 0 0 127.0.0.1:5037
0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:619
0.0.0.0:* LISTEN

Am i missing something???

Googling on this found out that, apart from the above lines in the
netstat; people have one more line like the one below:
tcp 0 0 0.0.0.0:5555 0.0.0.0:*
LISTEN

how do i get this line in my netstat on device?
Any config i'm missing??

thanks in advance,
Anantvijay

> > with regards vishal- Hide quoted text -