Gingerbread-x86 updated

[Chih-Wei Huang]

Hi,
The gingerbread-x86 branch is updated to latest
AOSP 2.3.5 release. A good news is,
the restriction of 64-bit build host is removed.

Other major changes include:
* kernel is updated to 2.6.39.
* hardware acceleration implements by the
latest Mesa 7.11 release.
Note the build rules is redesigned to support more
drivers. See external/mesa/Android.mk for details.
See eeepc or asus_laptop as examples.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Neeld]

Hi Chei-Wei,

I did repo sync and tried tu build again. But it fails in power module in

[Yi Sun]

Please post your build error messages

From: Neeld <nj.desh-gM/Ye1E23mwN+***@public.gmane.org>
Reply-To: <android-x86-/***@public.gmane.org>
Date: Mon, 8 Aug 2011 11:56:52 -0700 (PDT)
To: <android-x86-/***@public.gmane.org>
Subject: Re: Gingerbread-x86 updated

Hi Chei-Wei,

I did repo sync and tried tu build again. But it fails in power module in
kernel

--
You received this message because you are subscribed to the Google Groups
"Android-x86" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/android-x86/-/xzPq-4za4iUJ.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to
android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/android-x86?hl=en.


--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[fgdn17]

Ubuntu 10.04 64 bit build environment builds fine...will get a chance
to test tomorrow...

***@ubuntu-10-4:~$ cd latestginger
***@ubuntu-10-4:~/latestginger$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.3 LTS
Release: 10.04
Codename: lucid

***@ubuntu-10-4:~/latestginger$ date
Mon Aug 8 19:30:38 EDT 2011

***@ubuntu-10-4:~/latestginger$ repo sync
Fetching projects: 1% (2/171) remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
From git://android.git.kernel.org/platform/bootable/bootloader/legacy
* [new tag] android-cts-2.2_r7 -> android-cts-2.2_r7
Fetching projects: 2% (4/171) remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
.
.
.
Fetching projects: 99% (170/171) remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
From git://android.git.kernel.org/platform/system/netd
* [new tag] android-cts-2.2_r7 -> android-cts-2.2_r7
Fetching projects: 100% (171/171), done.
Syncing work tree: 100% (170/170), done.

kernel/: discarding 43 commits
prebuilt/: discarding 3 commits
***@ubuntu-10-4:~/latestginger$

***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
TARGET_PRODUCT=tegav2>
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.5
TARGET_PRODUCT=tegav2
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86-atom
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GRJ90
============================================
Checking build tools versions...
.
.
.
61.84% done, estimate finish Mon Aug 8 21:30:39 2011
68.69% done, estimate finish Mon Aug 8 21:30:39 2011
75.57% done, estimate finish Mon Aug 8 21:30:40 2011
82.43% done, estimate finish Mon Aug 8 21:30:40 2011
89.31% done, estimate finish Mon Aug 8 21:30:41 2011
96.17% done, estimate finish Mon Aug 8 21:30:42 2011
Total translation table size: 4495
Total rockridge attributes bytes: 1372
Total directory bytes: 2048
Path table size(bytes): 26
Done with: The File(s) Block(s) 72602
Writing: Ending Padblock Start Block 72636
Done with: Ending Padblock Block(s) 150
Max brk space used 0
72786 extents written (142 MB)
***@ubuntu-10-4:~/latestginger$




On Aug 8, 10:48 am, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> Hi,
> The gingerbread-x86 branch is updated to latest
> AOSP 2.3.5 release. A good news is,
> the restriction of 64-bit build host is removed.
>
> Other major changes include:
> * kernel is updated to 2.6.39.
> * hardware acceleration implements by the
>   latest Mesa 7.11 release.
>   Note the build rules is redesigned to support more
>   drivers. See external/mesa/Android.mk for details.
>   See eeepc or asus_laptop as examples.
>
> --
> Chih-Wei
> Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[fgdn17]

ok got to test my build today...BACK TO DRAWING BOARD PLEASE...DOESN'T
WORK...


am testing today....VIDEO is BROKEN...FYI

ran without hardware install as first try...ok comes up, homepage
ok...

anything done when touching menu from keyboard simple gives a blank
white screen....

cannot do anything...select file manger...blank white screen....

brought up again, removed keyboard after starting...

anything select from launcher simple brings up a blank white
screen........

am going to try building WITHOUT new changes that were done to isolate
issue...

trying to get logcat/dmesg fro system but not sure how as I usually
use ADB over
wireless BUT without being able to setup anything...including wireless
am presently
between a rock and a hard place...



On Aug 8, 9:48 pm, fgdn17 <dick.gor...-***@public.gmane.org> wrote:
> Ubuntu 10.04 64 bit build environment builds fine...will get a chance
> to test tomorrow...
>
> ***@ubuntu-10-4:~$ cd latestginger
> ***@ubuntu-10-4:~/latestginger$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:    Ubuntu 10.04.3 LTS
> Release:        10.04
> Codename:       lucid
>
> ***@ubuntu-10-4:~/latestginger$ date
> Mon Aug  8 19:30:38 EDT 2011
>
> ***@ubuntu-10-4:~/latestginger$ repo sync
> Fetching projects:   1% (2/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> From git://android.git.kernel.org/platform/bootable/bootloader/legacy
>  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> Fetching projects:   2% (4/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> .
> .
> .
> Fetching projects:  99% (170/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> From git://android.git.kernel.org/platform/system/netd
>  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> Fetching projects: 100% (171/171), done.
> Syncing work tree: 100% (170/170), done.
>
> kernel/: discarding 43 commits
> prebuilt/: discarding 3 commits
> ***@ubuntu-10-4:~/latestginger$
>
> ***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
> TARGET_PRODUCT=tegav2>
> ============================================
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=2.3.5
> TARGET_PRODUCT=tegav2
> TARGET_BUILD_VARIANT=eng
> TARGET_SIMULATOR=
> TARGET_BUILD_TYPE=release
> TARGET_BUILD_APPS=
> TARGET_ARCH=x86
> TARGET_ARCH_VARIANT=x86-atom
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=GRJ90
> ============================================
> Checking build tools versions...
> .
> .
> .
>  61.84% done, estimate finish Mon Aug  8 21:30:39 2011
>  68.69% done, estimate finish Mon Aug  8 21:30:39 2011
>  75.57% done, estimate finish Mon Aug  8 21:30:40 2011
>  82.43% done, estimate finish Mon Aug  8 21:30:40 2011
>  89.31% done, estimate finish Mon Aug  8 21:30:41 2011
>  96.17% done, estimate finish Mon Aug  8 21:30:42 2011
> Total translation table size: 4495
> Total rockridge attributes bytes: 1372
> Total directory bytes: 2048
> Path table size(bytes): 26
> Done with: The File(s)                             Block(s)    72602
> Writing:   Ending Padblock                         Start Block 72636
> Done with: Ending Padblock                         Block(s)    150
> Max brk space used 0
> 72786 extents written (142 MB)
> ***@ubuntu-10-4:~/latestginger$
>
> On Aug 8, 10:48 am, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>
>
>
>
>
>
>
> > Hi,
> > The gingerbread-x86 branch is updated to latest
> > AOSP 2.3.5 release. A good news is,
> > the restriction of 64-bit build host is removed.
>
> > Other major changes include:
> > * kernel is updated to 2.6.39.
> > * hardware acceleration implements by the
> >   latest Mesa 7.11 release.
> >   Note the build rules is redesigned to support more
> >   drivers. See external/mesa/Android.mk for details.
> >   See eeepc or asus_laptop as examples.
>
> > --
> > Chih-Wei
> > Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[fgdn17]

ok...have got it working...changed Boardconfig.mk using the string
from asus laptop

for BOARD_GPU_DRIVERS.....

it appears all they are doing is selecting everyone...so which ever is
correct
for tevgav2 is where I'll end up....hopefully that'll still work...

we'll see...

On Aug 9, 2:36 pm, fgdn17 <dick.gor...-***@public.gmane.org> wrote:
> ok got to test my build today...BACK TO DRAWING BOARD PLEASE...DOESN'T
> WORK...
>
> am testing today....VIDEO is BROKEN...FYI
>
> ran without hardware install as first try...ok comes up, homepage
> ok...
>
> anything done when touching menu from keyboard simple gives a blank
> white screen....
>
> cannot do anything...select file manger...blank white screen....
>
> brought up again, removed keyboard after starting...
>
> anything select from launcher simple brings up a blank white
> screen........
>
> am going to try building WITHOUT new changes that were done to isolate
> issue...
>
> trying to get logcat/dmesg fro system but not sure how as I usually
> use ADB over
> wireless BUT without being able to setup anything...including wireless
> am presently
> between a rock and a hard place...
>
> On Aug 8, 9:48 pm, fgdn17 <dick.gor...-***@public.gmane.org> wrote:
>
>
>
>
>
>
>
> > Ubuntu 10.04 64 bit build environment builds fine...will get a chance
> > to test tomorrow...
>
> > ***@ubuntu-10-4:~$ cd latestginger
> > ***@ubuntu-10-4:~/latestginger$ lsb_release -a
> > No LSB modules are available.
> > Distributor ID: Ubuntu
> > Description:    Ubuntu 10.04.3 LTS
> > Release:        10.04
> > Codename:       lucid
>
> > ***@ubuntu-10-4:~/latestginger$ date
> > Mon Aug  8 19:30:38 EDT 2011
>
> > ***@ubuntu-10-4:~/latestginger$ repo sync
> > Fetching projects:   1% (2/171)  remote: Counting objects: 1, done.
> > remote: Total 1 (delta 0), reused 0 (delta 0)
> > Unpacking objects: 100% (1/1), done.
> > From git://android.git.kernel.org/platform/bootable/bootloader/legacy
> >  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> > Fetching projects:   2% (4/171)  remote: Counting objects: 1, done.
> > remote: Total 1 (delta 0), reused 0 (delta 0)
> > Unpacking objects: 100% (1/1), done.
> > .
> > .
> > .
> > Fetching projects:  99% (170/171)  remote: Counting objects: 1, done.
> > remote: Total 1 (delta 0), reused 0 (delta 0)
> > Unpacking objects: 100% (1/1), done.
> > From git://android.git.kernel.org/platform/system/netd
> >  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> > Fetching projects: 100% (171/171), done.
> > Syncing work tree: 100% (170/170), done.
>
> > kernel/: discarding 43 commits
> > prebuilt/: discarding 3 commits
> > ***@ubuntu-10-4:~/latestginger$
>
> > ***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
> > TARGET_PRODUCT=tegav2>
> > ============================================
> > PLATFORM_VERSION_CODENAME=REL
> > PLATFORM_VERSION=2.3.5
> > TARGET_PRODUCT=tegav2
> > TARGET_BUILD_VARIANT=eng
> > TARGET_SIMULATOR=
> > TARGET_BUILD_TYPE=release
> > TARGET_BUILD_APPS=
> > TARGET_ARCH=x86
> > TARGET_ARCH_VARIANT=x86-atom
> > HOST_ARCH=x86
> > HOST_OS=linux
> > HOST_BUILD_TYPE=release
> > BUILD_ID=GRJ90
> > ============================================
> > Checking build tools versions...
> > .
> > .
> > .
> >  61.84% done, estimate finish Mon Aug  8 21:30:39 2011
> >  68.69% done, estimate finish Mon Aug  8 21:30:39 2011
> >  75.57% done, estimate finish Mon Aug  8 21:30:40 2011
> >  82.43% done, estimate finish Mon Aug  8 21:30:40 2011
> >  89.31% done, estimate finish Mon Aug  8 21:30:41 2011
> >  96.17% done, estimate finish Mon Aug  8 21:30:42 2011
> > Total translation table size: 4495
> > Total rockridge attributes bytes: 1372
> > Total directory bytes: 2048
> > Path table size(bytes): 26
> > Done with: The File(s)                             Block(s)    72602
> > Writing:   Ending Padblock                         Start Block 72636
> > Done with: Ending Padblock                         Block(s)    150
> > Max brk space used 0
> > 72786 extents written (142 MB)
> > ***@ubuntu-10-4:~/latestginger$
>
> > On Aug 8, 10:48 am, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>
> > > Hi,
> > > The gingerbread-x86 branch is updated to latest
> > > AOSP 2.3.5 release. A good news is,
> > > the restriction of 64-bit build host is removed.
>
> > > Other major changes include:
> > > * kernel is updated to 2.6.39.
> > > * hardware acceleration implements by the
> > >   latest Mesa 7.11 release.
> > >   Note the build rules is redesigned to support more
> > >   drivers. See external/mesa/Android.mk for details.
> > >   See eeepc or asus_laptop as examples.
>
> > > --
> > > Chih-Wei
> > > Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

Sorry, don't understand what you did exactly?
The tegav2 has already updated to match
the latest gingerbread-x86.

Make sure you have sync each project correctly.
Note if you have changed something without committing it,
repo sync may fail.

2011/8/10 fgdn17 <dick.gordon-***@public.gmane.org>:
> ok...have got it working...changed Boardconfig.mk using the string
> from asus laptop
>
> for BOARD_GPU_DRIVERS.....
>
> it appears all they are doing is selecting everyone...so which ever is
> correct
> for tevgav2 is where I'll end up....hopefully that'll still work...

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[fgdn17]

READ ALL MY POST..it builds..DOESN'T WORK...

VIDEO IS SCREWED UP...

On Aug 9, 9:11 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> Sorry, don't understand what you did exactly?
> The tegav2 has already updated to match
> the latest gingerbread-x86.
>
> Make sure you have sync each project correctly.
> Note if you have changed something without committing it,
> repo sync may fail.
>
> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
> > ok...have got it working...changed Boardconfig.mk using the string
> > from asus laptop
>
> > for BOARD_GPU_DRIVERS.....
>
> > it appears all they are doing is selecting everyone...so which ever is
> > correct
> > for tevgav2 is where I'll end up....hopefully that'll still work...
>
> --
> Chih-Wei
> Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

First, if you want report something,
please use clear and precise words in English
to describe how to reproduce the problem.

"VIDEO IS SCREWED UP" is not a very clear
statement. Did you mean the video playback
of Gallery3D is broken? or something else?

What I can tell you is tegav2 is the standard
test platform we use everyday.
It works very fine in this gingerbread-x86 update.
We don't see any problem you said.

I asked you ensure you have synced correctly
to get the right code. If you have changed something,
try to revert back it and make a clean build.
( you may need to rm -rf out/ )

Besides, tell us what device you tested exactly.
Did you use the exact tegav2 tablet shipped
by Tegatech? Or did you use some clones?


2011/8/10 fgdn17 <dick.gordon-***@public.gmane.org>:
> READ ALL MY POST..it builds..DOESN'T WORK...
>
> VIDEO IS SCREWED UP...
>
> On Aug 9, 9:11 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>> Sorry, don't understand what you did exactly?
>> The tegav2 has already updated to match
>> the latest gingerbread-x86.
>>
>> Make sure you have sync each project correctly.
>> Note if you have changed something without committing it,
>> repo sync may fail.
>>
>> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>>
>> > ok...have got it working...changed Boardconfig.mk using the string
>> > from asus laptop
>>
>> > for BOARD_GPU_DRIVERS.....
>>
>> > it appears all they are doing is selecting everyone...so which ever is
>> > correct
>> > for tevgav2 is where I'll end up....hopefully that'll still work...

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[fgdn17]

I'll repeat it all for you again...
see if you can follow along.....and note the date/time...
aug. 8th, 9:48pm
Ubuntu 10.04 64 bit build environment builds fine...will get a chance
to test tomorrow...

***@ubuntu-10-4:~$ cd latestginger
***@ubuntu-10-4:~/latestginger$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.3 LTS
Release: 10.04
Codename: lucid

***@ubuntu-10-4:~/latestginger$ date
Mon Aug 8 19:30:38 EDT 2011

***@ubuntu-10-4:~/latestginger$ repo sync
Fetching projects: 1% (2/171) remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
From git://android.git.kernel.org/platform/bootable/bootloader/legacy
* [new tag] android-cts-2.2_r7 -> android-cts-2.2_r7
Fetching projects: 2% (4/171) remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
.
.
.
Fetching projects: 99% (170/171) remote: Counting objects: 1, done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
From git://android.git.kernel.org/platform/system/netd
* [new tag] android-cts-2.2_r7 -> android-cts-2.2_r7
Fetching projects: 100% (171/171), done.
Syncing work tree: 100% (170/170), done.

kernel/: discarding 43 commits
prebuilt/: discarding 3 commits
***@ubuntu-10-4:~/latestginger$

***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
TARGET_PRODUCT=tegav2>
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.5
TARGET_PRODUCT=tegav2
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=x86
TARGET_ARCH_VARIANT=x86-atom
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GRJ90
============================================
Checking build tools versions...
.
.
.
61.84% done, estimate finish Mon Aug 8 21:30:39 2011
68.69% done, estimate finish Mon Aug 8 21:30:39 2011
75.57% done, estimate finish Mon Aug 8 21:30:40 2011
82.43% done, estimate finish Mon Aug 8 21:30:40 2011
89.31% done, estimate finish Mon Aug 8 21:30:41 2011
96.17% done, estimate finish Mon Aug 8 21:30:42 2011
Total translation table size: 4495
Total rockridge attributes bytes: 1372
Total directory bytes: 2048
Path table size(bytes): 26
Done with: The File(s) Block(s) 72602
Writing: Ending Padblock Start Block 72636
Done with: Ending Padblock Block(s) 150
Max brk space used 0
72786 extents written (142 MB)
***@ubuntu-10-4:~/latestginger$

aug. 9th, 2:36pm
ok got to test my build today...BACK TO DRAWING BOARD PLEASE...DOESN'T
WORK...

am testing today....VIDEO is BROKEN...FYI

ran without hardware install as first try...ok comes up, homepage
ok...

anything done when touching menu from keyboard simple gives a blank
white screen....

cannot do anything...select file manger...blank white screen....

brought up again, removed keyboard after starting...

anything select from launcher simple brings up a blank white
screen........

am going to try building WITHOUT new changes that were done to isolate
issue...

trying to get logcat/dmesg fro system but not sure how as I usually
use ADB over
wireless BUT without being able to setup anything...including wireless
am presently
between a rock and a hard place...
aug. 9th, 7:17pm
ok...have got it working...changed Boardconfig.mk using the string
from asus laptop

for BOARD_GPU_DRIVERS.....

it appears all they are doing is selecting everyone...so which ever is
correct
for tevgav2 is where I'll end up....hopefully that'll still work...

we'll see...


On Aug 9, 10:41 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> First, if you want report something,
> please use clear and precise words in English
> to describe how to reproduce the problem.
>
> "VIDEO IS SCREWED UP" is not a very clear
> statement. Did you mean the video playback
> of Gallery3D is broken? or something else?
>
> What I can tell you is tegav2 is the standard
> test platform we use everyday.
> It works very fine in this gingerbread-x86 update.
> We don't see any problem you said.
>
> I asked you ensure you have synced correctly
> to get the right code. If you have changed something,
> try to revert back it and make a clean build.
> ( you may need to rm -rf out/ )
>
> Besides, tell us what device you tested exactly.
> Did you use the exact tegav2 tablet shipped
> by Tegatech? Or did you use some clones?
>
> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
>
>
>
>
>
>
>
>
> > READ ALL MY POST..it builds..DOESN'T WORK...
>
> > VIDEO IS SCREWED UP...
>
> > On Aug 9, 9:11 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> >> Sorry, don't understand what you did exactly?
> >> The tegav2 has already updated to match
> >> the latest gingerbread-x86.
>
> >> Make sure you have sync each project correctly.
> >> Note if you have changed something without committing it,
> >> repo sync may fail.
>
> >> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
> >> > ok...have got it working...changed Boardconfig.mk using the string
> >> > from asus laptop
>
> >> > for BOARD_GPU_DRIVERS.....
>
> >> > it appears all they are doing is selecting everyone...so which ever is
> >> > correct
> >> > for tevgav2 is where I'll end up....hopefully that'll still work...
>
> --
> Chih-Wei
> Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

Sigh... Another Arobase...

2011/8/10 fgdn17 <dick.gordon-***@public.gmane.org>:
> I'll repeat it all for you again...
> see if you can follow along.....and note the date/time...
> aug. 8th, 9:48pm
> Ubuntu 10.04 64 bit build environment builds fine...will get a chance
> to test tomorrow...
>
> ***@ubuntu-10-4:~$ cd latestginger
> ***@ubuntu-10-4:~/latestginger$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:    Ubuntu 10.04.3 LTS
> Release:        10.04
> Codename:       lucid
>
> ***@ubuntu-10-4:~/latestginger$ date
> Mon Aug  8 19:30:38 EDT 2011
>
> ***@ubuntu-10-4:~/latestginger$ repo sync
> Fetching projects:   1% (2/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> From git://android.git.kernel.org/platform/bootable/bootloader/legacy
>  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> Fetching projects:   2% (4/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> .
> .
> .
> Fetching projects:  99% (170/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> From git://android.git.kernel.org/platform/system/netd
>  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> Fetching projects: 100% (171/171), done.
> Syncing work tree: 100% (170/170), done.
>
> kernel/: discarding 43 commits
> prebuilt/: discarding 3 commits
> ***@ubuntu-10-4:~/latestginger$
>
> ***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
> TARGET_PRODUCT=tegav2>
> ============================================
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=2.3.5
> TARGET_PRODUCT=tegav2
> TARGET_BUILD_VARIANT=eng
> TARGET_SIMULATOR=
> TARGET_BUILD_TYPE=release
> TARGET_BUILD_APPS=
> TARGET_ARCH=x86
> TARGET_ARCH_VARIANT=x86-atom
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=GRJ90
> ============================================
> Checking build tools versions...
> .
> .
> .
>  61.84% done, estimate finish Mon Aug  8 21:30:39 2011
>  68.69% done, estimate finish Mon Aug  8 21:30:39 2011
>  75.57% done, estimate finish Mon Aug  8 21:30:40 2011
>  82.43% done, estimate finish Mon Aug  8 21:30:40 2011
>  89.31% done, estimate finish Mon Aug  8 21:30:41 2011
>  96.17% done, estimate finish Mon Aug  8 21:30:42 2011
> Total translation table size: 4495
> Total rockridge attributes bytes: 1372
> Total directory bytes: 2048
> Path table size(bytes): 26
> Done with: The File(s)                             Block(s)    72602
> Writing:   Ending Padblock                         Start Block 72636
> Done with: Ending Padblock                         Block(s)    150
> Max brk space used 0
> 72786 extents written (142 MB)
> ***@ubuntu-10-4:~/latestginger$
>
> aug. 9th, 2:36pm
> ok got to test my build today...BACK TO DRAWING BOARD PLEASE...DOESN'T
> WORK...
>
> am testing today....VIDEO is BROKEN...FYI
>
> ran without hardware install as first try...ok comes up, homepage
> ok...
>
> anything done when touching menu from keyboard simple gives a blank
> white screen....
>
> cannot do anything...select file manger...blank white screen....
>
> brought up again, removed keyboard after starting...
>
> anything select from launcher simple brings up a blank white
> screen........
>
> am going to try building WITHOUT new changes that were done to isolate
> issue...
>
> trying to get logcat/dmesg fro system but not sure how as I usually
> use ADB over
> wireless BUT without being able to setup anything...including wireless
> am presently
> between a rock and a hard place...
> aug. 9th, 7:17pm
> ok...have got it working...changed Boardconfig.mk using the string
> from asus laptop
>
> for BOARD_GPU_DRIVERS.....
>
> it appears all they are doing is selecting everyone...so which ever is
> correct
> for tevgav2 is where I'll end up....hopefully that'll still work...
>
> we'll see...
>
>
> On Aug 9, 10:41 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>> First, if you want report something,
>> please use clear and precise words in English
>> to describe how to reproduce the problem.
>>
>> "VIDEO IS SCREWED UP" is not a very clear
>> statement. Did you mean the video playback
>> of Gallery3D is broken? or something else?
>>
>> What I can tell you is tegav2 is the standard
>> test platform we use everyday.
>> It works very fine in this gingerbread-x86 update.
>> We don't see any problem you said.
>>
>> I asked you ensure you have synced correctly
>> to get the right code. If you have changed something,
>> try to revert back it and make a clean build.
>> ( you may need to rm -rf out/ )
>>
>> Besides, tell us what device you tested exactly.
>> Did you use the exact tegav2 tablet shipped
>> by Tegatech? Or did you use some clones?
>>
>> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> > READ ALL MY POST..it builds..DOESN'T WORK...
>>
>> > VIDEO IS SCREWED UP...
>>
>> > On Aug 9, 9:11 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>> >> Sorry, don't understand what you did exactly?
>> >> The tegav2 has already updated to match
>> >> the latest gingerbread-x86.
>>
>> >> Make sure you have sync each project correctly.
>> >> Note if you have changed something without committing it,
>> >> repo sync may fail.
>>
>> >> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>>
>> >> > ok...have got it working...changed Boardconfig.mk using the string
>> >> > from asus laptop
>>
>> >> > for BOARD_GPU_DRIVERS.....
>>
>> >> > it appears all they are doing is selecting everyone...so which ever is
>> >> > correct
>> >> > for tevgav2 is where I'll end up....hopefully that'll still work...
>>
>> --
>> Chih-Wei
>> Android-x86 projecthttp://www.android-x86.org
>
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>
>



--
Chih-Wei
Android-x86 project
http://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[fgdn17]

Arobase?? Is that something wrong on my build system???

On Aug 9, 11:47 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> Sigh... Another Arobase...
>
> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
>
>
>
>
>
>
>
>
> > I'll repeat it all for you again...
> > see if you can follow along.....and note the date/time...
> > aug. 8th, 9:48pm
> > Ubuntu 10.04 64 bit build environment builds fine...will get a chance
> > to test tomorrow...
>
> > ***@ubuntu-10-4:~$ cd latestginger
> > ***@ubuntu-10-4:~/latestginger$ lsb_release -a
> > No LSB modules are available.
> > Distributor ID: Ubuntu
> > Description:    Ubuntu 10.04.3 LTS
> > Release:        10.04
> > Codename:       lucid
>
> > ***@ubuntu-10-4:~/latestginger$ date
> > Mon Aug  8 19:30:38 EDT 2011
>
> > ***@ubuntu-10-4:~/latestginger$ repo sync
> > Fetching projects:   1% (2/171)  remote: Counting objects: 1, done.
> > remote: Total 1 (delta 0), reused 0 (delta 0)
> > Unpacking objects: 100% (1/1), done.
> > From git://android.git.kernel.org/platform/bootable/bootloader/legacy
> >  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> > Fetching projects:   2% (4/171)  remote: Counting objects: 1, done.
> > remote: Total 1 (delta 0), reused 0 (delta 0)
> > Unpacking objects: 100% (1/1), done.
> > .
> > .
> > .
> > Fetching projects:  99% (170/171)  remote: Counting objects: 1, done.
> > remote: Total 1 (delta 0), reused 0 (delta 0)
> > Unpacking objects: 100% (1/1), done.
> > From git://android.git.kernel.org/platform/system/netd
> >  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> > Fetching projects: 100% (171/171), done.
> > Syncing work tree: 100% (170/170), done.
>
> > kernel/: discarding 43 commits
> > prebuilt/: discarding 3 commits
> > ***@ubuntu-10-4:~/latestginger$
>
> > ***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
> > TARGET_PRODUCT=tegav2>
> > ============================================
> > PLATFORM_VERSION_CODENAME=REL
> > PLATFORM_VERSION=2.3.5
> > TARGET_PRODUCT=tegav2
> > TARGET_BUILD_VARIANT=eng
> > TARGET_SIMULATOR=
> > TARGET_BUILD_TYPE=release
> > TARGET_BUILD_APPS=
> > TARGET_ARCH=x86
> > TARGET_ARCH_VARIANT=x86-atom
> > HOST_ARCH=x86
> > HOST_OS=linux
> > HOST_BUILD_TYPE=release
> > BUILD_ID=GRJ90
> > ============================================
> > Checking build tools versions...
> > .
> > .
> > .
> >  61.84% done, estimate finish Mon Aug  8 21:30:39 2011
> >  68.69% done, estimate finish Mon Aug  8 21:30:39 2011
> >  75.57% done, estimate finish Mon Aug  8 21:30:40 2011
> >  82.43% done, estimate finish Mon Aug  8 21:30:40 2011
> >  89.31% done, estimate finish Mon Aug  8 21:30:41 2011
> >  96.17% done, estimate finish Mon Aug  8 21:30:42 2011
> > Total translation table size: 4495
> > Total rockridge attributes bytes: 1372
> > Total directory bytes: 2048
> > Path table size(bytes): 26
> > Done with: The File(s)                             Block(s)    72602
> > Writing:   Ending Padblock                         Start Block 72636
> > Done with: Ending Padblock                         Block(s)    150
> > Max brk space used 0
> > 72786 extents written (142 MB)
> > ***@ubuntu-10-4:~/latestginger$
>
> > aug. 9th, 2:36pm
> > ok got to test my build today...BACK TO DRAWING BOARD PLEASE...DOESN'T
> > WORK...
>
> > am testing today....VIDEO is BROKEN...FYI
>
> > ran without hardware install as first try...ok comes up, homepage
> > ok...
>
> > anything done when touching menu from keyboard simple gives a blank
> > white screen....
>
> > cannot do anything...select file manger...blank white screen....
>
> > brought up again, removed keyboard after starting...
>
> > anything select from launcher simple brings up a blank white
> > screen........
>
> > am going to try building WITHOUT new changes that were done to isolate
> > issue...
>
> > trying to get logcat/dmesg fro system but not sure how as I usually
> > use ADB over
> > wireless BUT without being able to setup anything...including wireless
> > am presently
> > between a rock and a hard place...
> > aug. 9th, 7:17pm
> > ok...have got it working...changed Boardconfig.mk using the string
> > from asus laptop
>
> > for BOARD_GPU_DRIVERS.....
>
> > it appears all they are doing is selecting everyone...so which ever is
> > correct
> > for tevgav2 is where I'll end up....hopefully that'll still work...
>
> > we'll see...
>
> > On Aug 9, 10:41 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> >> First, if you want report something,
> >> please use clear and precise words in English
> >> to describe how to reproduce the problem.
>
> >> "VIDEO IS SCREWED UP" is not a very clear
> >> statement. Did you mean the video playback
> >> of Gallery3D is broken? or something else?
>
> >> What I can tell you is tegav2 is the standard
> >> test platform we use everyday.
> >> It works very fine in this gingerbread-x86 update.
> >> We don't see any problem you said.
>
> >> I asked you ensure you have synced correctly
> >> to get the right code. If you have changed something,
> >> try to revert back it and make a clean build.
> >> ( you may need to rm -rf out/ )
>
> >> Besides, tell us what device you tested exactly.
> >> Did you use the exact tegav2 tablet shipped
> >> by Tegatech? Or did you use some clones?
>
> >> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
> >> > READ ALL MY POST..it builds..DOESN'T WORK...
>
> >> > VIDEO IS SCREWED UP...
>
> >> > On Aug 9, 9:11 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> >> >> Sorry, don't understand what you did exactly?
> >> >> The tegav2 has already updated to match
> >> >> the latest gingerbread-x86.
>
> >> >> Make sure you have sync each project correctly.
> >> >> Note if you have changed something without committing it,
> >> >> repo sync may fail.
>
> >> >> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
> >> >> > ok...have got it working...changed Boardconfig.mk using the string
> >> >> > from asus laptop
>
> >> >> > for BOARD_GPU_DRIVERS.....
>
> >> >> > it appears all they are doing is selecting everyone...so which ever is
> >> >> > correct
> >> >> > for tevgav2 is where I'll end up....hopefully that'll still work...
>
> >> --
> >> Chih-Wei
> >> Android-x86 projecthttp://www.android-x86.org
>
> > --
> > You received this message because you are subscribed to the Google Groups "Android-x86" group.
> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> > To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/android-x86?hl=en.
>
> --
> Chih-Wei
> Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Yi Sun]

Dude,
What is your target device?
Yi


On Aug 9, 2011, at 8:53 PM, fgdn17 <dick.gordon-***@public.gmane.org> wrote:

> Arobase?? Is that something wrong on my build system???
>
> On Aug 9, 11:47 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>> Sigh... Another Arobase...
>>
>> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>> I'll repeat it all for you again...
>>> see if you can follow along.....and note the date/time...
>>> aug. 8th, 9:48pm
>>> Ubuntu 10.04 64 bit build environment builds fine...will get a chance
>>> to test tomorrow...
>>
>>> ***@ubuntu-10-4:~$ cd latestginger
>>> ***@ubuntu-10-4:~/latestginger$ lsb_release -a
>>> No LSB modules are available.
>>> Distributor ID: Ubuntu
>>> Description: Ubuntu 10.04.3 LTS
>>> Release: 10.04
>>> Codename: lucid
>>
>>> ***@ubuntu-10-4:~/latestginger$ date
>>> Mon Aug 8 19:30:38 EDT 2011
>>
>>> ***@ubuntu-10-4:~/latestginger$ repo sync
>>> Fetching projects: 1% (2/171) remote: Counting objects: 1, done.
>>> remote: Total 1 (delta 0), reused 0 (delta 0)
>>> Unpacking objects: 100% (1/1), done.
>>> From git://android.git.kernel.org/platform/bootable/bootloader/legacy
>>> * [new tag] android-cts-2.2_r7 -> android-cts-2.2_r7
>>> Fetching projects: 2% (4/171) remote: Counting objects: 1, done.
>>> remote: Total 1 (delta 0), reused 0 (delta 0)
>>> Unpacking objects: 100% (1/1), done.
>>> .
>>> .
>>> .
>>> Fetching projects: 99% (170/171) remote: Counting objects: 1, done.
>>> remote: Total 1 (delta 0), reused 0 (delta 0)
>>> Unpacking objects: 100% (1/1), done.
>>> From git://android.git.kernel.org/platform/system/netd
>>> * [new tag] android-cts-2.2_r7 -> android-cts-2.2_r7
>>> Fetching projects: 100% (171/171), done.
>>> Syncing work tree: 100% (170/170), done.
>>
>>> kernel/: discarding 43 commits
>>> prebuilt/: discarding 3 commits
>>> ***@ubuntu-10-4:~/latestginger$
>>
>>> ***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
>>> TARGET_PRODUCT=tegav2>
>>> ============================================
>>> PLATFORM_VERSION_CODENAME=REL
>>> PLATFORM_VERSION=2.3.5
>>> TARGET_PRODUCT=tegav2
>>> TARGET_BUILD_VARIANT=eng
>>> TARGET_SIMULATOR=
>>> TARGET_BUILD_TYPE=release
>>> TARGET_BUILD_APPS=
>>> TARGET_ARCH=x86
>>> TARGET_ARCH_VARIANT=x86-atom
>>> HOST_ARCH=x86
>>> HOST_OS=linux
>>> HOST_BUILD_TYPE=release
>>> BUILD_ID=GRJ90
>>> ============================================
>>> Checking build tools versions...
>>> .
>>> .
>>> .
>>> 61.84% done, estimate finish Mon Aug 8 21:30:39 2011
>>> 68.69% done, estimate finish Mon Aug 8 21:30:39 2011
>>> 75.57% done, estimate finish Mon Aug 8 21:30:40 2011
>>> 82.43% done, estimate finish Mon Aug 8 21:30:40 2011
>>> 89.31% done, estimate finish Mon Aug 8 21:30:41 2011
>>> 96.17% done, estimate finish Mon Aug 8 21:30:42 2011
>>> Total translation table size: 4495
>>> Total rockridge attributes bytes: 1372
>>> Total directory bytes: 2048
>>> Path table size(bytes): 26
>>> Done with: The File(s) Block(s) 72602
>>> Writing: Ending Padblock Start Block 72636
>>> Done with: Ending Padblock Block(s) 150
>>> Max brk space used 0
>>> 72786 extents written (142 MB)
>>> ***@ubuntu-10-4:~/latestginger$
>>
>>> aug. 9th, 2:36pm
>>> ok got to test my build today...BACK TO DRAWING BOARD PLEASE...DOESN'T
>>> WORK...
>>
>>> am testing today....VIDEO is BROKEN...FYI
>>
>>> ran without hardware install as first try...ok comes up, homepage
>>> ok...
>>
>>> anything done when touching menu from keyboard simple gives a blank
>>> white screen....
>>
>>> cannot do anything...select file manger...blank white screen....
>>
>>> brought up again, removed keyboard after starting...
>>
>>> anything select from launcher simple brings up a blank white
>>> screen........
>>
>>> am going to try building WITHOUT new changes that were done to isolate
>>> issue...
>>
>>> trying to get logcat/dmesg fro system but not sure how as I usually
>>> use ADB over
>>> wireless BUT without being able to setup anything...including wireless
>>> am presently
>>> between a rock and a hard place...
>>> aug. 9th, 7:17pm
>>> ok...have got it working...changed Boardconfig.mk using the string
>>> from asus laptop
>>
>>> for BOARD_GPU_DRIVERS.....
>>
>>> it appears all they are doing is selecting everyone...so which ever is
>>> correct
>>> for tevgav2 is where I'll end up....hopefully that'll still work...
>>
>>> we'll see...
>>
>>> On Aug 9, 10:41 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>>>> First, if you want report something,
>>>> please use clear and precise words in English
>>>> to describe how to reproduce the problem.
>>
>>>> "VIDEO IS SCREWED UP" is not a very clear
>>>> statement. Did you mean the video playback
>>>> of Gallery3D is broken? or something else?
>>
>>>> What I can tell you is tegav2 is the standard
>>>> test platform we use everyday.
>>>> It works very fine in this gingerbread-x86 update.
>>>> We don't see any problem you said.
>>
>>>> I asked you ensure you have synced correctly
>>>> to get the right code. If you have changed something,
>>>> try to revert back it and make a clean build.
>>>> ( you may need to rm -rf out/ )
>>
>>>> Besides, tell us what device you tested exactly.
>>>> Did you use the exact tegav2 tablet shipped
>>>> by Tegatech? Or did you use some clones?
>>
>>>> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>>
>>>>> READ ALL MY POST..it builds..DOESN'T WORK...
>>
>>>>> VIDEO IS SCREWED UP...
>>
>>>>> On Aug 9, 9:11 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>>>>>> Sorry, don't understand what you did exactly?
>>>>>> The tegav2 has already updated to match
>>>>>> the latest gingerbread-x86.
>>
>>>>>> Make sure you have sync each project correctly.
>>>>>> Note if you have changed something without committing it,
>>>>>> repo sync may fail.
>>
>>>>>> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>>
>>>>>>> ok...have got it working...changed Boardconfig.mk using the string
>>>>>>> from asus laptop
>>
>>>>>>> for BOARD_GPU_DRIVERS.....
>>
>>>>>>> it appears all they are doing is selecting everyone...so which ever is
>>>>>>> correct
>>>>>>> for tevgav2 is where I'll end up....hopefully that'll still work...
>>
>>>> --
>>>> Chih-Wei
>>>> Android-x86 projecthttp://www.android-x86.org
>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "Android-x86" group.
>>> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>>> To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>>> For more options, visit this group athttp://groups.google.com/group/android-x86?hl=en.
>>
>> --
>> Chih-Wei
>> Android-x86 projecthttp://www.android-x86.org
>
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>

[Shady]

Hello All,

Built 2.3.5 for my Lenovo S10e and noticed considerable improvements in the
graphics. However somethings still don't work. Details below:

On 2.3.4 I used to use the S103t target from froyo ( a simple copy paste of
the target folder, and that got me good results bar HW acceleration).
Now with 2.3.5, that same target was not usable, even with updating the
variables (maybe there are more changes that I'm not aware about). So
instead, I used the asus laptop target. However, I modified the laptop_info
file to use the laptop_info() function regardless of the board name. This
way I can benefit from the auto detect. Compiles and boots.

Results: The UI and animations are amazingly fast and smooth, I didn't think
it could be better than what I had on 2.3.4, but it was. The gallery works
amazingly well, just like on my phone.

Things that still don't work:
*Camera*: When ever I start the camera app, I get a white screen. On
froyo-x86, my last attempt with the FB0DEV (with / without debate) I managed
to get the camera to work. However, now it still shows a white screen.
*Video Play Back: *The video playback is slightly better than before.
Quality is better but frame rate is still very low.
*Microphone:* Any app that tries to record or use the mic causes a force
close. Logcat states errors setting buffer to 2048, invalid arguments,
unable to set sample rate, among others
*Mouse: * The mouse works great. But in portrait mode it only goes down to
half of the screen.

Thank you for the updates. Things are looking good. I hope there are
solutions for the above.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/ZXI0Ifn6tPkJ.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

2011/8/10 Shady <rasheedshady-***@public.gmane.org>:
> Camera: When ever I start the camera app, I get a white screen. On
> froyo-x86, my last attempt with the FB0DEV (with / without debate) I managed
> to get the camera to work. However, now it still shows a white screen.

Camera support is not added to gingerbread-x86 yet.

> Video Play Back: The video playback is slightly better than before. Quality
> is better but frame rate is still very low.

The AOSP (and Android-x86) implements the video playback
by software codec. It's not very optimized for x86,
especially it didn't take advantage of multi threads.

To improve the performance, there are two possible approaches:
* use hardware decoders, but that's very hardware dependent.
* port libraries like ffmpeg or gstreamer to Android-x86.
Theoretically they are better optimized for x86.

Either way are hard work and needs contributors.

> Microphone: Any app that tries to record or use the mic causes a force
> close. Logcat states errors setting buffer to 2048, invalid arguments,
> unable to set sample rate, among others

I'll check the issue later.

> Mouse:  The mouse works great. But in portrait mode it only goes down to
> half of the screen.

I just fixed that. Please sync again.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Shady Rasheed]

Thanks!! Mouse works like a charm. Although it could be handy to reverse the
axis just like the cursor keys.

Again, thanks a lot.

On Wed, Aug 10, 2011 at 10:27 AM, Chih-Wei Huang <cwhuang-/***@public.gmane.org>wrote:

> 2011/8/10 Shady <rasheedshady-***@public.gmane.org>:
> > Camera: When ever I start the camera app, I get a white screen. On
> > froyo-x86, my last attempt with the FB0DEV (with / without debate) I
> managed
> > to get the camera to work. However, now it still shows a white screen.
>
> Camera support is not added to gingerbread-x86 yet.
>
> > Video Play Back: The video playback is slightly better than before.
> Quality
> > is better but frame rate is still very low.
>
> The AOSP (and Android-x86) implements the video playback
> by software codec. It's not very optimized for x86,
> especially it didn't take advantage of multi threads.
>
> To improve the performance, there are two possible approaches:
> * use hardware decoders, but that's very hardware dependent.
> * port libraries like ffmpeg or gstreamer to Android-x86.
> Theoretically they are better optimized for x86.
>
> Either way are hard work and needs contributors.
>
> > Microphone: Any app that tries to record or use the mic causes a force
> > close. Logcat states errors setting buffer to 2048, invalid arguments,
> > unable to set sample rate, among others
>
> I'll check the issue later.
>
> > Mouse: The mouse works great. But in portrait mode it only goes down to
> > half of the screen.
>
> I just fixed that. Please sync again.
>
> --
> Chih-Wei
> Android-x86 project
> http://www.android-x86.org
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
>
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Kuan Po Huang]

Hi Chih-Wei,

For camera issue, is there any direction i can do to make camera preview
shown on screen?

Thanks.

Kurt.

On Wed, Aug 10, 2011 at 8:11 PM, Shady Rasheed <rasheedshady-***@public.gmane.org>wrote:

> Thanks!! Mouse works like a charm. Although it could be handy to reverse
> the axis just like the cursor keys.
>
> Again, thanks a lot.
>
>
> On Wed, Aug 10, 2011 at 10:27 AM, Chih-Wei Huang <cwhuang-/***@public.gmane.org>wrote:
>
>> 2011/8/10 Shady <rasheedshady-***@public.gmane.org>:
>> > Camera: When ever I start the camera app, I get a white screen. On
>> > froyo-x86, my last attempt with the FB0DEV (with / without debate) I
>> managed
>> > to get the camera to work. However, now it still shows a white screen.
>>
>> Camera support is not added to gingerbread-x86 yet.
>>
>> > Video Play Back: The video playback is slightly better than before.
>> Quality
>> > is better but frame rate is still very low.
>>
>> The AOSP (and Android-x86) implements the video playback
>> by software codec. It's not very optimized for x86,
>> especially it didn't take advantage of multi threads.
>>
>> To improve the performance, there are two possible approaches:
>> * use hardware decoders, but that's very hardware dependent.
>> * port libraries like ffmpeg or gstreamer to Android-x86.
>> Theoretically they are better optimized for x86.
>>
>> Either way are hard work and needs contributors.
>>
>> > Microphone: Any app that tries to record or use the mic causes a force
>> > close. Logcat states errors setting buffer to 2048, invalid arguments,
>> > unable to set sample rate, among others
>>
>> I'll check the issue later.
>>
>> > Mouse: The mouse works great. But in portrait mode it only goes down to
>> > half of the screen.
>>
>> I just fixed that. Please sync again.
>>
>> --
>> Chih-Wei
>> Android-x86 project
>> http://www.android-x86.org
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Android-x86" group.
>> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> To unsubscribe from this group, send email to
>> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> For more options, visit this group at
>> http://groups.google.com/group/android-x86?hl=en.
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Dustin Knight]

Im using acer aspire one ao110. Mesa is perfect on gingerbread now. Im
having a strange issue with wifi. AO110 uses ath5k driver btw and using a
slightly modifed eepc device tree. Only changed board names and auto detect
script for acer to do a full auto detect. Wifi works perfect on a usb live
drive. When installed to hdd as ext3 wifi scans only the first time and
never associates. After reboots it never lists ap's anymore. This has
happened on install to hdd on everything after donut. Logcat reports a
ioctrl sigsev on wpa_supplicant as the error. After wifi works on persistant
install Im ready to use x86 as primary os. Any suggestions and yes ethernet
is turned off.
On Aug 10, 2011 8:33 AM, "Kuan Po Huang" <kphuang-***@public.gmane.org> wrote:
> Hi Chih-Wei,
>
> For camera issue, is there any direction i can do to make camera preview
> shown on screen?
>
> Thanks.
>
> Kurt.
>
> On Wed, Aug 10, 2011 at 8:11 PM, Shady Rasheed <rasheedshady-***@public.gmane.org
>wrote:
>
>> Thanks!! Mouse works like a charm. Although it could be handy to reverse
>> the axis just like the cursor keys.
>>
>> Again, thanks a lot.
>>
>>
>> On Wed, Aug 10, 2011 at 10:27 AM, Chih-Wei Huang <cwhuang-/***@public.gmane.org
>wrote:
>>
>>> 2011/8/10 Shady <rasheedshady-***@public.gmane.org>:
>>> > Camera: When ever I start the camera app, I get a white screen. On
>>> > froyo-x86, my last attempt with the FB0DEV (with / without debate) I
>>> managed
>>> > to get the camera to work. However, now it still shows a white screen.
>>>
>>> Camera support is not added to gingerbread-x86 yet.
>>>
>>> > Video Play Back: The video playback is slightly better than before.
>>> Quality
>>> > is better but frame rate is still very low.
>>>
>>> The AOSP (and Android-x86) implements the video playback
>>> by software codec. It's not very optimized for x86,
>>> especially it didn't take advantage of multi threads.
>>>
>>> To improve the performance, there are two possible approaches:
>>> * use hardware decoders, but that's very hardware dependent.
>>> * port libraries like ffmpeg or gstreamer to Android-x86.
>>> Theoretically they are better optimized for x86.
>>>
>>> Either way are hard work and needs contributors.
>>>
>>> > Microphone: Any app that tries to record or use the mic causes a force
>>> > close. Logcat states errors setting buffer to 2048, invalid arguments,
>>> > unable to set sample rate, among others
>>>
>>> I'll check the issue later.
>>>
>>> > Mouse: The mouse works great. But in portrait mode it only goes down
to
>>> > half of the screen.
>>>
>>> I just fixed that. Please sync again.
>>>
>>> --
>>> Chih-Wei
>>> Android-x86 project
>>> http://www.android-x86.org
>>>
>>> --
>>> You received this message because you are subscribed to the Google
Groups
>>> "Android-x86" group.
>>> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>>> To unsubscribe from this group, send email to
>>> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-x86?hl=en.
>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Android-x86" group.
>> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> To unsubscribe from this group, send email to
>> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> For more options, visit this group at
>> http://groups.google.com/group/android-x86?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
"Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
http://groups.google.com/group/android-x86?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Shady Rasheed]

Hello Chih-Wei


> port libraries like ffmpeg or gstreamer to Android-x86.
> Theoretically they are better optimized for x86.


Does compiling ffmpeg against NDK r6 targeting x86 do the job? I've managed
to get ffmpeg to start compiling, facing some minor issues which should be
sorted out soon.

If it does the job, can it be used instead of the built in decoder of
Android?

Unless this is not how things are done...

Looking for feedback!

On Wed, Aug 10, 2011 at 10:27 AM, Chih-Wei Huang <cwhuang-/***@public.gmane.org>wrote:

> To improve the performance, there are two possible approaches:
> * use hardware decoders, but that's very hardware dependent.
> * port libraries like ffmpeg or gstreamer to Android-x86.
> Theoretically they are better optimized for x86.
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

Not that easy. Compiling ffmpeg for android is easy.
The difficult part is to write some glue code so that
the android media framework can use it.

2011/8/11 Shady Rasheed <rasheedshady-***@public.gmane.org>:
> Hello Chih-Wei
>>  port libraries like ffmpeg or gstreamer to Android-x86.
>>  Theoretically they are better optimized for x86.
>
> Does compiling ffmpeg against  NDK r6 targeting x86 do the job? I've managed
> to get ffmpeg to start compiling, facing some minor issues which should be
> sorted out soon.
> If it does the job, can it be used instead of the built in decoder of
> Android?

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[tabletsx86]

after repo sync today build is broke again???

issue seems to be in kernel folder somewhere???



On Aug 11, 5:36 am, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> Not that easy. Compiling ffmpeg for android is easy.
> The difficult part is to write some glue code so that
> the android media framework can use it.
>
> 2011/8/11 Shady Rasheed <rasheedsh...-***@public.gmane.org>:
>
> > Hello Chih-Wei
> >>  port libraries like ffmpeg or gstreamer to Android-x86.
> >>  Theoretically they are better optimized for x86.
>
> > Does compiling ffmpeg against  NDK r6 targeting x86 do the job? I've managed
> > to get ffmpeg to start compiling, facing some minor issues which should be
> > sorted out soon.
> > If it does the job, can it be used instead of the built in decoder of
> > Android?
>
> --
> Chih-Wei
> Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

Thanks for report.
I fixed it by cherry-pick from android-3.0.
Not sure if it's the correct fix,
but at least it is build-able now.

2011/8/17 tabletsx86 <rbg.tabletsx86-***@public.gmane.org>:
> after repo sync today build is broke again???
> issue seems to be in kernel folder somewhere???

[tabletsx86]

repo'ed sync and it built fine...thanks

will be able to test later!!!!!!!!!!

On Aug 17, 3:57 am, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> Thanks for report.
> I fixed it by cherry-pick from android-3.0.
> Not sure if it's the correct fix,
> but at least it is build-able now.
>
> 2011/8/17 tabletsx86 <rbg.tablets...-***@public.gmane.org>:
>
>
>
>
>
>
>
> > after repo sync today build is broke again???
> > issue seems to be in kernel folder somewhere???

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Shady]

Hello Chih Wei
Any ideas on what might be the problem with capturing sound with the
microphone. I'm running gingerbread-x86 and get the following error when
using any application that tries to capture sound:

ALSALib( 2080): external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
Unknown PCM AndroidCapture
ALSAModule( 2080): Unable to set buffer size to 2048: Invalid argument
ALSAModule( 2080): Initialized ALSA CAPTURE device default
ALSAModule( 2080): open called for devices 00040000 in mode 0...
ALSALib( 2080): external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
Unknown PCM AndroidCapture
ALSAModule( 2080): Unable to set buffer size to 2048: Invalid argument
ALSAModule( 2080): Initialized ALSA CAPTURE device default
AudioRecord( 2116): Could not get audio input for record source 6


Thanks in advance

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/q52PR4yk5YcJ.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Douglas Santillan]

Sorry to bud in, but I think I can help with that.

I used to get ALSA logcat messages like that until I grafted an
asound.conf in /etc, that may be your ticket.

Please find attached a copy of the file. It may be modified depending
on your needs. This one should work fine for Froyo 2.2

On Wed, Sep 7, 2011 at 5:56 AM, Shady <rasheedshady-***@public.gmane.org> wrote:
> Hello Chih Wei
> Any ideas on what might be the problem with capturing sound with the
> microphone. I'm running gingerbread-x86 and get the following error when
> using any application that tries to capture sound:
> ALSALib( 2080): external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
> Unknown PCM AndroidCapture
> ALSAModule( 2080): Unable to set buffer size to 2048:  Invalid argument
> ALSAModule( 2080): Initialized ALSA CAPTURE device default
> ALSAModule( 2080): open called for devices 00040000 in mode 0...
> ALSALib( 2080): external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
> Unknown PCM AndroidCapture
> ALSAModule( 2080): Unable to set buffer size to 2048:  Invalid argument
> ALSAModule( 2080): Initialized ALSA CAPTURE device default
> AudioRecord( 2116): Could not get audio input for record source 6
>
> Thanks in advance
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-x86/-/q52PR4yk5YcJ.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Shady Rasheed]

Thanks for your input. The file did solve that problem, however another one
is showing now.
It is stating that Alsa Module : Unable to set channel count to 1: Invalid
argument.

I read somewhere, about code for earlier versions of android that Android
supports 1 channel recording only, while ALSA only supports 2 channel
recording.
I don't know if that is true or not, or if changes have been made to fix
this issue. But the bottom line is Alsa module is unable to set channel
count to 1

I hope someone has more info about this and how to fix it. I tried to follow
the patches on this site
http://code.google.com/p/0xdroid/issues/detail?id=10 but it didn't help.

Thanks in advance.

On Wed, Sep 7, 2011 at 10:17 PM, Douglas Santillan <capricorpsa-***@public.gmane.org>wrote:

> Sorry to bud in, but I think I can help with that.
>
> I used to get ALSA logcat messages like that until I grafted an
> asound.conf in /etc, that may be your ticket.
>
> Please find attached a copy of the file. It may be modified depending
> on your needs. This one should work fine for Froyo 2.2
>
> On Wed, Sep 7, 2011 at 5:56 AM, Shady <rasheedshady-***@public.gmane.org> wrote:
> > Hello Chih Wei
> > Any ideas on what might be the problem with capturing sound with the
> > microphone. I'm running gingerbread-x86 and get the following error when
> > using any application that tries to capture sound:
> > ALSALib( 2080):
> external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
> > Unknown PCM AndroidCapture
> > ALSAModule( 2080): Unable to set buffer size to 2048: Invalid argument
> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
> > ALSAModule( 2080): open called for devices 00040000 in mode 0...
> > ALSALib( 2080):
> external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
> > Unknown PCM AndroidCapture
> > ALSAModule( 2080): Unable to set buffer size to 2048: Invalid argument
> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
> > AudioRecord( 2116): Could not get audio input for record source 6
> >
> > Thanks in advance
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Android-x86" group.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msg/android-x86/-/q52PR4yk5YcJ.
> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> > To unsubscribe from this group, send email to
> > android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> > For more options, visit this group at
> > http://groups.google.com/group/android-x86?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
>
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Douglas Santillan]

Now you seem to have a chance to continue.

It seems that the key for your next step is in alsa_default.cpp in
/hardware/alsa_sound

defaults in definition account for 1 channel DEVICE_IN, however I do
not see DEVICE_IN tables. I hope that helps

I have seen that logcat message but I have not yet tinkered with voice
recording. I suspect this is the path to follow, and see what comes up
next.

On Wed, Sep 7, 2011 at 11:48 PM, Shady Rasheed <rasheedshady-***@public.gmane.org> wrote:
> Thanks for your input. The file did solve that problem, however another one
> is showing now.
> It is stating that Alsa Module : Unable to set channel count to 1: Invalid
> argument.
> I read somewhere, about code for earlier versions of android that Android
> supports 1 channel recording only, while ALSA only supports 2 channel
> recording.
> I don't know if that is true or not, or if changes have been made to fix
> this issue. But the bottom line is Alsa module is unable to set channel
> count to 1
> I hope someone has more info about this and how to fix it. I tried to follow
> the patches on this
> site http://code.google.com/p/0xdroid/issues/detail?id=10 but it didn't
> help.
> Thanks in advance.
>
> On Wed, Sep 7, 2011 at 10:17 PM, Douglas Santillan <capricorpsa-***@public.gmane.org>
> wrote:
>>
>> Sorry to bud in, but I think I can help with that.
>>
>> I used to get ALSA logcat messages like that until I grafted an
>> asound.conf in /etc, that may be your ticket.
>>
>> Please find attached a copy of the file. It may be modified depending
>> on your needs. This one should work fine for Froyo 2.2
>>
>> On Wed, Sep 7, 2011 at 5:56 AM, Shady <rasheedshady-***@public.gmane.org> wrote:
>> > Hello Chih Wei
>> > Any ideas on what might be the problem with capturing sound with the
>> > microphone. I'm running gingerbread-x86 and get the following error when
>> > using any application that tries to capture sound:
>> > ALSALib( 2080):
>> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
>> > Unknown PCM AndroidCapture
>> > ALSAModule( 2080): Unable to set buffer size to 2048:  Invalid argument
>> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
>> > ALSAModule( 2080): open called for devices 00040000 in mode 0...
>> > ALSALib( 2080):
>> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
>> > Unknown PCM AndroidCapture
>> > ALSAModule( 2080): Unable to set buffer size to 2048:  Invalid argument
>> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
>> > AudioRecord( 2116): Could not get audio input for record source 6
>> >
>> > Thanks in advance
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Android-x86" group.
>> > To view this discussion on the web visit
>> > https://groups.google.com/d/msg/android-x86/-/q52PR4yk5YcJ.
>> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> > To unsubscribe from this group, send email to
>> > android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-x86?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Android-x86" group.
>> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> To unsubscribe from this group, send email to
>> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> For more options, visit this group at
>> http://groups.google.com/group/android-x86?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Douglas Santillan]

Quick follow up.

The asound.conf file I sent needed changes.

While in Android, launch the FileManager and browse to

proc / asound
there check contents of
cards
devices

change the asound.conf for the devices that ALSA is detecting. Channel
does set to 1, however there are other logcat messages after that.
Using Speech recorder, 8K sampling works, 11K complaints.

I hope this helps


On Wed, Sep 7, 2011 at 11:48 PM, Shady Rasheed <rasheedshady-***@public.gmane.org> wrote:
> Thanks for your input. The file did solve that problem, however another one
> is showing now.
> It is stating that Alsa Module : Unable to set channel count to 1: Invalid
> argument.
> I read somewhere, about code for earlier versions of android that Android
> supports 1 channel recording only, while ALSA only supports 2 channel
> recording.
> I don't know if that is true or not, or if changes have been made to fix
> this issue. But the bottom line is Alsa module is unable to set channel
> count to 1
> I hope someone has more info about this and how to fix it. I tried to follow
> the patches on this
> site http://code.google.com/p/0xdroid/issues/detail?id=10 but it didn't
> help.
> Thanks in advance.
>
> On Wed, Sep 7, 2011 at 10:17 PM, Douglas Santillan <capricorpsa-***@public.gmane.org>
> wrote:
>>
>> Sorry to bud in, but I think I can help with that.
>>
>> I used to get ALSA logcat messages like that until I grafted an
>> asound.conf in /etc, that may be your ticket.
>>
>> Please find attached a copy of the file. It may be modified depending
>> on your needs. This one should work fine for Froyo 2.2
>>
>> On Wed, Sep 7, 2011 at 5:56 AM, Shady <rasheedshady-***@public.gmane.org> wrote:
>> > Hello Chih Wei
>> > Any ideas on what might be the problem with capturing sound with the
>> > microphone. I'm running gingerbread-x86 and get the following error when
>> > using any application that tries to capture sound:
>> > ALSALib( 2080):
>> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
>> > Unknown PCM AndroidCapture
>> > ALSAModule( 2080): Unable to set buffer size to 2048:  Invalid argument
>> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
>> > ALSAModule( 2080): open called for devices 00040000 in mode 0...
>> > ALSALib( 2080):
>> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
>> > Unknown PCM AndroidCapture
>> > ALSAModule( 2080): Unable to set buffer size to 2048:  Invalid argument
>> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
>> > AudioRecord( 2116): Could not get audio input for record source 6
>> >
>> > Thanks in advance
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Android-x86" group.
>> > To view this discussion on the web visit
>> > https://groups.google.com/d/msg/android-x86/-/q52PR4yk5YcJ.
>> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> > To unsubscribe from this group, send email to
>> > android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-x86?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Android-x86" group.
>> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> To unsubscribe from this group, send email to
>> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> For more options, visit this group at
>> http://groups.google.com/group/android-x86?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Shady Rasheed]

Douglas,

Thanks for the follow up. I will fiddle around with it later tonight, will
post back with updates.

Regards,

On Fri, Sep 9, 2011 at 1:40 AM, Douglas Santillan <capricorpsa-***@public.gmane.org>wrote:

> Quick follow up.
>
> The asound.conf file I sent needed changes.
>
> While in Android, launch the FileManager and browse to
>
> proc / asound
> there check contents of
> cards
> devices
>
> change the asound.conf for the devices that ALSA is detecting. Channel
> does set to 1, however there are other logcat messages after that.
> Using Speech recorder, 8K sampling works, 11K complaints.
>
> I hope this helps
>
>
> On Wed, Sep 7, 2011 at 11:48 PM, Shady Rasheed <rasheedshady-***@public.gmane.org>
> wrote:
> > Thanks for your input. The file did solve that problem, however another
> one
> > is showing now.
> > It is stating that Alsa Module : Unable to set channel count to 1:
> Invalid
> > argument.
> > I read somewhere, about code for earlier versions of android that Android
> > supports 1 channel recording only, while ALSA only supports 2 channel
> > recording.
> > I don't know if that is true or not, or if changes have been made to fix
> > this issue. But the bottom line is Alsa module is unable to set channel
> > count to 1
> > I hope someone has more info about this and how to fix it. I tried to
> follow
> > the patches on this
> > site http://code.google.com/p/0xdroid/issues/detail?id=10 but it didn't
> > help.
> > Thanks in advance.
> >
> > On Wed, Sep 7, 2011 at 10:17 PM, Douglas Santillan <
> capricorpsa-***@public.gmane.org>
> > wrote:
> >>
> >> Sorry to bud in, but I think I can help with that.
> >>
> >> I used to get ALSA logcat messages like that until I grafted an
> >> asound.conf in /etc, that may be your ticket.
> >>
> >> Please find attached a copy of the file. It may be modified depending
> >> on your needs. This one should work fine for Froyo 2.2
> >>
> >> On Wed, Sep 7, 2011 at 5:56 AM, Shady <rasheedshady-***@public.gmane.org> wrote:
> >> > Hello Chih Wei
> >> > Any ideas on what might be the problem with capturing sound with the
> >> > microphone. I'm running gingerbread-x86 and get the following error
> when
> >> > using any application that tries to capture sound:
> >> > ALSALib( 2080):
> >> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
> >> > Unknown PCM AndroidCapture
> >> > ALSAModule( 2080): Unable to set buffer size to 2048: Invalid
> argument
> >> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
> >> > ALSAModule( 2080): open called for devices 00040000 in mode 0...
> >> > ALSALib( 2080):
> >> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
> >> > Unknown PCM AndroidCapture
> >> > ALSAModule( 2080): Unable to set buffer size to 2048: Invalid
> argument
> >> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
> >> > AudioRecord( 2116): Could not get audio input for record source 6
> >> >
> >> > Thanks in advance
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups
> >> > "Android-x86" group.
> >> > To view this discussion on the web visit
> >> > https://groups.google.com/d/msg/android-x86/-/q52PR4yk5YcJ.
> >> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> >> > To unsubscribe from this group, send email to
> >> > android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/android-x86?hl=en.
> >> >
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Android-x86" group.
> >> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> >> To unsubscribe from this group, send email to
> >> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> >> For more options, visit this group at
> >> http://groups.google.com/group/android-x86?hl=en.
> >>
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Android-x86" group.
> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> > To unsubscribe from this group, send email to
> > android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> > For more options, visit this group at
> > http://groups.google.com/group/android-x86?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> To unsubscribe from this group, send email to
> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.
>
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Shady Rasheed]

Douglas,

Here's what I have in cards and devices

cards shows:
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf0640000 irq 43
devices shows:
2: [ 0- 0]: digital audio playback
3: [ 0- 0]: digital audio capture
4: [ 0- 0]: hardware dependent
5: [ 0] : control
33: : timer


so i changed the following in asound.conf
pcm.AndroidRecord {
type hw
card 0
device 3 <---- was 0 before

}

pcm.AndroidCapture {
type hw
card 0
device 3 <---was 0 before
}

As you said it records in 8K mode but states the following when recording in
11k mode

D/SpeechRecorderActivity( 1825): mRecord.OnClickListener.onClick
D/SpeechRecorderActivity( 1825): setupRecording
D/SpeechRecorderActivity( 1825): going to record
/data/data/com.android.speechrecorder/app_recordings/call_alex_lloyd.wav
D/dalvikvm( 1825): GC_FOR_MALLOC freed 323K, 52% free 2723K/5575K, external
722K/1038K, paused 11ms
I/dalvikvm-heap( 1825): Grow heap (frag case) to 6.201MB for 441012-byte
allocation
D/dalvikvm( 1825): GC_FOR_MALLOC freed 0K, 48% free 3153K/6023K, external
722K/1038K, paused 11ms
D/ALSAModule( 1626): open called for devices 00040000 in mode 0...
I/ALSAModule( 1626): Initialized ALSA CAPTURE device default
D/AcousticsModule( 1626): Acoustics set_params stub called with 0.
W/AudioHardwareInterface( 1626): getInputBufferSize bad sampling rate: 11025
E/AudioRecord( 1825): Unsupported configuration: sampleRate 11025, format 1,
channelCount 1
E/srec_jni( 1825): initCheck error -22
D/SpeechRecorderActivity( 1825): run audio capture thread
W/dalvikvm( 1825): threadid=8: thread exiting with uncaught exception
(group=0xb57454f0)
E/AndroidRuntime( 1825): FATAL EXCEPTION: Thread-9
E/AndroidRuntime( 1825): java.lang.NullPointerException
E/AndroidRuntime( 1825): at
com.android.speechrecorder.SpeechRecorderActivity$4.run(SpeechRecorderActivity.java:192)
W/ActivityManager( 1462): Force finishing activity
com.android.speechrecorder/.SpeechRecorderActivity


But this only works with the modified image based on the patch i mentioned a
previous post.


On Fri, Sep 9, 2011 at 5:49 PM, Shady Rasheed <rasheedshady-***@public.gmane.org>wrote:

> Douglas,
>
> Thanks for the follow up. I will fiddle around with it later tonight, will
> post back with updates.
>
> Regards,
>
>
> On Fri, Sep 9, 2011 at 1:40 AM, Douglas Santillan <capricorpsa-***@public.gmane.org>wrote:
>
>> Quick follow up.
>>
>> The asound.conf file I sent needed changes.
>>
>> While in Android, launch the FileManager and browse to
>>
>> proc / asound
>> there check contents of
>> cards
>> devices
>>
>> change the asound.conf for the devices that ALSA is detecting. Channel
>> does set to 1, however there are other logcat messages after that.
>> Using Speech recorder, 8K sampling works, 11K complaints.
>>
>> I hope this helps
>>
>>
>> On Wed, Sep 7, 2011 at 11:48 PM, Shady Rasheed <rasheedshady-***@public.gmane.org>
>> wrote:
>> > Thanks for your input. The file did solve that problem, however another
>> one
>> > is showing now.
>> > It is stating that Alsa Module : Unable to set channel count to 1:
>> Invalid
>> > argument.
>> > I read somewhere, about code for earlier versions of android that
>> Android
>> > supports 1 channel recording only, while ALSA only supports 2 channel
>> > recording.
>> > I don't know if that is true or not, or if changes have been made to fix
>> > this issue. But the bottom line is Alsa module is unable to set channel
>> > count to 1
>> > I hope someone has more info about this and how to fix it. I tried to
>> follow
>> > the patches on this
>> > site http://code.google.com/p/0xdroid/issues/detail?id=10 but it didn't
>> > help.
>> > Thanks in advance.
>> >
>> > On Wed, Sep 7, 2011 at 10:17 PM, Douglas Santillan <
>> capricorpsa-***@public.gmane.org>
>> > wrote:
>> >>
>> >> Sorry to bud in, but I think I can help with that.
>> >>
>> >> I used to get ALSA logcat messages like that until I grafted an
>> >> asound.conf in /etc, that may be your ticket.
>> >>
>> >> Please find attached a copy of the file. It may be modified depending
>> >> on your needs. This one should work fine for Froyo 2.2
>> >>
>> >> On Wed, Sep 7, 2011 at 5:56 AM, Shady <rasheedshady-***@public.gmane.org> wrote:
>> >> > Hello Chih Wei
>> >> > Any ideas on what might be the problem with capturing sound with the
>> >> > microphone. I'm running gingerbread-x86 and get the following error
>> when
>> >> > using any application that tries to capture sound:
>> >> > ALSALib( 2080):
>> >> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
>> >> > Unknown PCM AndroidCapture
>> >> > ALSAModule( 2080): Unable to set buffer size to 2048: Invalid
>> argument
>> >> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
>> >> > ALSAModule( 2080): open called for devices 00040000 in mode 0...
>> >> > ALSALib( 2080):
>> >> > external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)
>> >> > Unknown PCM AndroidCapture
>> >> > ALSAModule( 2080): Unable to set buffer size to 2048: Invalid
>> argument
>> >> > ALSAModule( 2080): Initialized ALSA CAPTURE device default
>> >> > AudioRecord( 2116): Could not get audio input for record source 6
>> >> >
>> >> > Thanks in advance
>> >> >
>> >> > --
>> >> > You received this message because you are subscribed to the Google
>> >> > Groups
>> >> > "Android-x86" group.
>> >> > To view this discussion on the web visit
>> >> > https://groups.google.com/d/msg/android-x86/-/q52PR4yk5YcJ.
>> >> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> >> > To unsubscribe from this group, send email to
>> >> > android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/android-x86?hl=en.
>> >> >
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> Groups
>> >> "Android-x86" group.
>> >> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> >> To unsubscribe from this group, send email to
>> >> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> >> For more options, visit this group at
>> >> http://groups.google.com/group/android-x86?hl=en.
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "Android-x86" group.
>> > To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> > To unsubscribe from this group, send email to
>> > android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> > For more options, visit this group at
>> > http://groups.google.com/group/android-x86?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Android-x86" group.
>> To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> To unsubscribe from this group, send email to
>> android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
>> For more options, visit this group at
>> http://groups.google.com/group/android-x86?hl=en.
>>
>>
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[fuzzy7k]

Nowhere in any of that did you mention what device you are trying to
install on, or even what video chip it uses. How can you expect anyone
to help you if you treat them like idiots and don't provided any
usefull information?

On Aug 9, 11:27 pm, fgdn17 <dick.gor...-***@public.gmane.org> wrote:
> I'll repeat it all for you again...
> see if you can follow along.....and note the date/time...
> aug. 8th, 9:48pm
> Ubuntu 10.04 64 bit build environment builds fine...will get a chance
> to test tomorrow...
>
> ***@ubuntu-10-4:~$ cd latestginger
> ***@ubuntu-10-4:~/latestginger$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:    Ubuntu 10.04.3 LTS
> Release:        10.04
> Codename:       lucid
>
> ***@ubuntu-10-4:~/latestginger$ date
> Mon Aug  8 19:30:38 EDT 2011
>
> ***@ubuntu-10-4:~/latestginger$ repo sync
> Fetching projects:   1% (2/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> From git://android.git.kernel.org/platform/bootable/bootloader/legacy
>  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> Fetching projects:   2% (4/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> .
> .
> .
> Fetching projects:  99% (170/171)  remote: Counting objects: 1, done.
> remote: Total 1 (delta 0), reused 0 (delta 0)
> Unpacking objects: 100% (1/1), done.
> From git://android.git.kernel.org/platform/system/netd
>  * [new tag]         android-cts-2.2_r7 -> android-cts-2.2_r7
> Fetching projects: 100% (171/171), done.
> Syncing work tree: 100% (170/170), done.
>
> kernel/: discarding 43 commits
> prebuilt/: discarding 3 commits
> ***@ubuntu-10-4:~/latestginger$
>
> ***@ubuntu-10-4:~/latestginger$ make -j4 iso_img
> TARGET_PRODUCT=tegav2>
> ============================================
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=2.3.5
> TARGET_PRODUCT=tegav2
> TARGET_BUILD_VARIANT=eng
> TARGET_SIMULATOR=
> TARGET_BUILD_TYPE=release
> TARGET_BUILD_APPS=
> TARGET_ARCH=x86
> TARGET_ARCH_VARIANT=x86-atom
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=GRJ90
> ============================================
> Checking build tools versions...
> .
> .
> .
>  61.84% done, estimate finish Mon Aug  8 21:30:39 2011
>  68.69% done, estimate finish Mon Aug  8 21:30:39 2011
>  75.57% done, estimate finish Mon Aug  8 21:30:40 2011
>  82.43% done, estimate finish Mon Aug  8 21:30:40 2011
>  89.31% done, estimate finish Mon Aug  8 21:30:41 2011
>  96.17% done, estimate finish Mon Aug  8 21:30:42 2011
> Total translation table size: 4495
> Total rockridge attributes bytes: 1372
> Total directory bytes: 2048
> Path table size(bytes): 26
> Done with: The File(s)                             Block(s)    72602
> Writing:   Ending Padblock                         Start Block 72636
> Done with: Ending Padblock                         Block(s)    150
> Max brk space used 0
> 72786 extents written (142 MB)
> ***@ubuntu-10-4:~/latestginger$
>
> aug. 9th, 2:36pm
> ok got to test my build today...BACK TO DRAWING BOARD PLEASE...DOESN'T
> WORK...
>
> am testing today....VIDEO is BROKEN...FYI
>
> ran without hardware install as first try...ok comes up, homepage
> ok...
>
> anything done when touching menu from keyboard simple gives a blank
> white screen....
>
> cannot do anything...select file manger...blank white screen....
>
> brought up again, removed keyboard after starting...
>
> anything select from launcher simple brings up a blank white
> screen........
>
> am going to try building WITHOUT new changes that were done to isolate
> issue...
>
> trying to get logcat/dmesg fro system but not sure how as I usually
> use ADB over
> wireless BUT without being able to setup anything...including wireless
> am presently
> between a rock and a hard place...
> aug. 9th, 7:17pm
> ok...have got it working...changed Boardconfig.mk using the string
> from asus laptop
>
> for BOARD_GPU_DRIVERS.....
>
> it appears all they are doing is selecting everyone...so which ever is
> correct
> for tevgav2 is where I'll end up....hopefully that'll still work...
>
> we'll see...
>
> On Aug 9, 10:41 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
>
> > First, if you want report something,
> > please use clear and precise words in English
> > to describe how to reproduce the problem.
>
> > "VIDEO IS SCREWED UP" is not a very clear
> > statement. Did you mean the video playback
> > of Gallery3D is broken? or something else?
>
> > What I can tell you is tegav2 is the standard
> > test platform we use everyday.
> > It works very fine in this gingerbread-x86 update.
> > We don't see any problem you said.
>
> > I asked you ensure you have synced correctly
> > to get the right code. If you have changed something,
> > try to revert back it and make a clean build.
> > ( you may need to rm -rf out/ )
>
> > Besides, tell us what device you tested exactly.
> > Did you use the exact tegav2 tablet shipped
> > by Tegatech? Or did you use some clones?
>
> > 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
> > > READ ALL MY POST..it builds..DOESN'T WORK...
>
> > > VIDEO IS SCREWED UP...
>
> > > On Aug 9, 9:11 pm, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> > >> Sorry, don't understand what you did exactly?
> > >> The tegav2 has already updated to match
> > >> the latest gingerbread-x86.
>
> > >> Make sure you have sync each project correctly.
> > >> Note if you have changed something without committing it,
> > >> repo sync may fail.
>
> > >> 2011/8/10 fgdn17 <dick.gor...-***@public.gmane.org>:
>
> > >> > ok...have got it working...changed Boardconfig.mk using the string
> > >> > from asus laptop
>
> > >> > for BOARD_GPU_DRIVERS.....
>
> > >> > it appears all they are doing is selecting everyone...so which ever is
> > >> > correct
> > >> > for tevgav2 is where I'll end up....hopefully that'll still work...
>
> > --
> > Chih-Wei
> > Android-x86 projecthttp://www.android-x86.org

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[albe]

Hp Mini 1000 1030nr WiFi Working!
Thank you I have been waiting!
BCM4315 (chip 4312) WiFi works "Out of the BOx"
woo hoo!
ISO from mariuz's site Daily x86 ginger builds generic_x86.iso.7z
8/9/2011
gingerbread-x86 2.3.5 release kernel 2.6.39.

On Aug 8, 10:48 am, Chih-Wei Huang <cwhu...-/***@public.gmane.org> wrote:
> Hi,
> The gingerbread-x86 branch is updated to latest
> AOSP 2.3.5 release. A good news is,
> the restriction of 64-bit build host is removed.
>
> Other major changes include:
> * kernel is updated to 2.6.39.
> * hardware acceleration implements by the
>   latest Mesa 7.11 release.
>   Note the build rules is redesigned to support more
>   drivers. See external/mesa/Android.mk for details.
>   See eeepc or asus_laptop as examples.
>
> --
> Chih-Wei
> Android-x86 projecthttp://www.android-x86.org
>
>

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to android-x86-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To unsubscribe from this group, send email to android-x86+***@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Chih-Wei Huang]

Hi,
The gingerbread-x86 branch has been updated to
AOSP 2.3.7 release.
Besides, a new target amd_persimmon is added.
Thanks to AMD that contributed it.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org