4.0 ICS.on Tegav2

[Daniel Lodge]

Hi guys, fantastic work on the 4.0 ICS build!

I have installed it on my Tegav2, and it works and runs great.
Only a few issues I have found.....

1. The app switcher button doesnt work at all. (it did work in the
3.2 version)
2. Camera doesnt work.
3. After running for a random period of time (up to 30mins constant
use sometimes), the screen will all of a sudden just go blank.....then
if you click a key, it will show you the terminal (as if you'd pressed
Alt-F1). Then you cant get back into Android?

[Daniel Lodge]

also just found out that auido doesnt work

[Chih-Wei Huang]

You are using an deprecated version.

2011-12-31 上午7:08 於 "Daniel Lodge" <nzda...@gmail.com> 寫道：

also just found out that auido doesnt work

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
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.

[Alvin Ong]

Audio doesnt work, only works when docked for the dell inspiron duo

[Daniel Lodge]

I am using the 20111209 version of tegav2 which is the latest version
available on the downloads page

On Dec 31, 5:30 pm, Alvin Ong <al...@alvinandcheri.com> wrote:
> Audio doesnt work, only works when docked for the dell inspiron duo
>

> On Dec 30, 2011, at 7:50 PM, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
>
> You are using an deprecated version.

[WizardTom]

https://code.google.com/p/android-x86/downloads/list Has the updated
version, not on Android-X86 website though. You'll get your sound,
way smoother scroll and graphics, and a brick... that is No Browser
Function! It's a one line fix that was discovered but I am just
waiting for a patch or rebuild.

[Avery Lewis]

So is the sound now working on the Tegra version that was put out 5
days ago? And what about the Camera and has anyone managed to get
Angry Birds to run on their tablet and if so a link to the app?

[Al Sutton]

I've put a browser-fixed build up at http://code.google.com/p/android-x86/downloads/detail?name=android-x86-4.0-tegav2-20111231.iso.zip

It has an issue with screen time-outs, so you should maximise it's time out period, but apart from that issue I've been able to fire it up, connect to my WiFi network and browse the web :).

Happy new year :).

Al.

-- 
T: @alsutton W: www.funkyandroid.com 

The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. 

[bnavigator]

Excellent!

Thanks for the new build. Browser is working now. Any chance to have a
build witth GApps and Market included?

Ben

[Al Sutton]

Inclusion of the GApps or Market would breach Googles copyright.

-- 
T: @alsutton W: www.funkyandroid.com 

The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. 

[bnavigator]

So how come it is in the 20111225 build? How do I merge those images
to get the benefits from both of them?

[Joshua Akonom]

here is the link to all the gapps minus the market. There are ways to
get it but I am not going to violate the policies that google sets
forth. These apps however are fully available free from Google:

http://www.google.com/mobile/android/

[Alvin Ong]

Does the sound work on this build?

On Jan 1, 2012, at 5:25 AM, tabletsx86 <rbg.tab...@gmail.com> wrote:

> Google Apps contain the proprietary Google applications that come pre-
> installed with most android devices.
> Due to licensing restrictions, these apps cannot come pre-installed
> and must be installed separately.
>
> Available from Cyanogenmod:
>
> http://wiki.cyanogenmod.com/wiki/Main_Page
>
>
> HERE:
>
> http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip

[Daniel Lodge]

Agreed...how come market was included in the last build?

[bnavigator]

It's also included in the brand new build by cwh.

[Daniel Lodge]

haha settle down there buddy.
We are grateful for any fixes that anyone does.

On Jan 2, 4:27 pm, tabletsx86 <rbg.tablets...@gmail.com> wrote:
> pay attention....
>
> 12-25 build was by CHW and had the market/gapps
> so he obviously works for a company the doesn't have the
> licensing restrictions and/or he has them himself...
>
> 1-1 released by Al Sutton was evidently as a favor to the group
> to correct some issues and he doesn't have the rights to include the
> gapps...
>
> then later on 1-1 CHW released an updated version, with gapps and
> fixes....
>
> it's really not difficult if you read...instead of saying "how come
> the others
> had them and this one doesn't"...just be thankful your getting fixes
> as
> some have been waithing a while just to get the browser fixes in
> tegav2 so
> it was useful...want market...get it on your own...install it and be
> good to go...
>
> google is your friend...and someone, somewhere has usually already
> solved your issue...!!!

[Chih-Wei Huang]

Guys,
Stop talking about that issue.
If Google complains, I must remove them totally,
or even stop this project completely.
Unless that's what you want...

[Chih-Wei Huang]

2012/1/1 Chih-Wei Huang <cwh...@android-x86.org>:
> BTW, I'm still curios what the root cause of the browser issue is.
> I've tested the 4.0.3 emulator and some arm phones
> without this fix. The browser works fine.
> So it seems to be an android-x86 specified issue?
> I stuck...

OK, I think I found the fundamental reason.
The http_stack used by android-x86 is 'android',
while armv7a uses 'chrome'.
(see frameworks/base/media/libstagefright/Android.mk
about line 100-120)

However, we are unable to enable chrome stack,
since it requres v8 engine, which is arm only now.
shxt!!

This is also the root cause of Youtube crashing --
the stagefright http streaming requires chrome stack.
(see frameworks/base/media/libstagefright/HTTPBase.cpp,
line 52)

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

[Dave Hunt]

Is there an easy fix or is this a serious show stopper for streaming.
This also blows my mind as this implies that Google has locked into
the arm architecture. I seriously think they are missing a golden
opportunity to snag the portable pc market. Unless they are still
banking on ChromeOS.

On Jan 2, 10:35 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> 2012/1/1 Chih-Wei Huang <cwhu...@android-x86.org>:

>
> > BTW, I'm still curios what the root cause of the browser issue is.

> > I've tested the4.0.3 emulator and some arm phones