I'm curious does AMD sponsor or take part in the active development of android x86. I remembered they gave some hardware for development but is their role bigger?
On Nov 30, 7:52 pm, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> please make iso for viewpad. And include the driver for the broadcom.
> -- > 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@googlegroups.com. > To unsubscribe from this group, send email to > android-x86+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/android-x86?hl=en.
Hi, I ran ICS in live mode on my Acer W500 and it works great. There are some driver issues that I summarized in issue 505. Please take a look. Thank you
On Nov 30, 9:53 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Is the TEGA V2/Viewpad 10 support ready yet? I've never compiled > android-x86 before so it's all new to me other than downloading the > pre-built images.
> I'm curious does AMD sponsor or take part in the active development of > android x86. I remembered they gave some hardware for development but > is their role bigger?
Just finished trying this on an Iconia W500. Wireless worked but it took several attempts to successfully connect to my router. No touch screen or audio. But everything else worked quite well. Google Market also worked just fine.
On Nov 30, 11:53 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
On the Acer AO521 AMD Athlon Neo netbook is it not possible to boot into ICS 4.0. I get on the boot up screen "loading android".. but noting is happend.
Thnaks for the hard work... developers..
On 1 dec, 03:45, Stephen Ferrell <stephen.ferr...@gmail.com> wrote:
> Just finished trying this on an Iconia W500. Wireless worked but it > took several attempts to successfully connect to my router. No touch > screen or audio. But everything else worked quite well. Google > Market also worked just fine.
> On Nov 30, 11:53 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> > Hi all,
> > The ics-x86 branch based on Android 4.0.1 is ready. > > You may download the source as usual:
I just installed this on my W500, and had no problems with wireless. I did have some issues with video corruption, but they were manageable. The lack of touchscreen was sad, and I also had no sound. All other features appeared to work well.
You guys do great work, thanks for everything!
I have the north American model 8Z467 if that makes a difference.
I'm having a hell of a time getting it to boot without a kernel panic. The most dummy proof thing I've tried is creating an amd_brazos build with one small tweak, device/amd/brazos/ BoardConfig.mk:#TARGET_ARCH_VARIANT := x86-atom. I'm using a Turion X2, which doesn't support atom optimizations. The next most dummy proof thing I've tried is doing the same with the asus_laptop build in addition to changing the kernel target arch from core2 to k8 and adding support for amd cpus.
The results I get under normal boot are: -"Detecting Android-x86... found at /dev/sda8" with flashing caps lock.
The results I get under Debug mode are: -no early debug shell, I see the message to type exit and the message that it's running the shell, but it just blows through without skipping a beat -no late debug shell, again I get the type exit message, and the running shell message with a blinking cursor on the line below, but no prompt. I can type, but there is no prompt so nothing happens when I hit enter. -I can switch to ps2,3, and run dmesg which looks ok, but logcat gives me "Illegal instruction".
On Dec 1, 7:12 am, smarte <raf...@gmail.com> wrote:
> On the Acer AO521 AMD Athlon Neo netbook is it not possible to boot > intoICS4.0. > I get on the boot up screen "loading android".. but noting is > happend.
> Thnaks for the hard work... developers..
> On 1 dec, 03:45, Stephen Ferrell <stephen.ferr...@gmail.com> wrote:
> > Just finished trying this on an Iconia W500. Wireless worked but it > > took several attempts to successfully connect to my router. No touch > > screen or audio. But everything else worked quite well. Google > > Market also worked just fine.
> > On Nov 30, 11:53 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> > > Hi all,
> > > Theics-x86 branch based on Android 4.0.1 is ready. > > > You may download the source as usual:
Hi, I've got a reply from an Intel engineer (privately). He said "Intel platform does not yet supportICS, but Intel developers are working on it. i965 support will arrive in several weeks."
However, I still have some unclear questions that are not answered:
* Whether Intell will support i915 chip? That is, the video chip used in most atom based tablet or netbook. * Whether Intel will release the solution to public so all the community can benefit from it.
> Hi, > I've got a reply from an Intel engineer (privately). > He said "Intel platform does not yet supportICS, but Intel developers > are working on it. > i965 support will arrive in several weeks."
> However, I still have some unclear questions > that are not answered:
> * Whether Intell will support i915 chip? > That is, the video chip used in most atom based > tablet or netbook. > * Whether Intel will release the solution to public > so all the community can benefit from it.
I've said that in another thread. We still have troubles to bring OpenGL ES hardware acceleration (by GPU) to Intel video chipsets, including i915 and i965.
More technically, when start surfaceflinger, the screen becomes whole black, and the errors last in logcat:
Surfaceflinger: GL error 0x500
Are you interesting in resolving it? Welcome on board.
In my case - I can see the UI, but I get "Unfortunately, System UI has stopped." massage box will popup every few seconds. I cant use the console, but still I will try to see if its the same "GL error 0x500" issue.
On Dec 5, 11:04 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> I've said that in another thread. > We still have troubles to bring OpenGL ES > hardware acceleration (by GPU) to > Intel video chipsets, including i915 and i965.
> More technically, when start surfaceflinger, > the screen becomes whole black, and > the errors last in logcat:
> Surfaceflinger: GL error 0x500
> Are you interesting in resolving it? > Welcome on board.
> In my case - I can see the UI, but I get "Unfortunately, System UI has > stopped." massage box will popup every few seconds. I cant use the > console, but still I will try to see if its the same "GL error 0x500" > issue.
> > In my case - I can see the UI, but I get "Unfortunately, System UI has > > stopped." massage box will popup every few seconds. I cant use the > > console, but still I will try to see if its the same "GL error 0x500" > > issue.
> I'm having a hell of a time getting it to boot without a kernel panic. > The most dummy proof thing I've tried is creating an amd_brazos build > with one small tweak, device/amd/brazos/ > BoardConfig.mk:#TARGET_ARCH_VARIANT := x86-atom. I'm using a Turion > X2, which doesn't support atom optimizations. The next most dummy > proof thing I've tried is doing the same with the asus_laptop build in > addition to changing the kernel target arch from core2 to k8 and > adding support for amd cpus.
> The results I get under normal boot are: > -"Detecting Android-x86... found at /dev/sda8" with flashing caps > lock.
> The results I get under Debug mode are: > -no early debug shell, I see the message to type exit and the message > that it's running the shell, but it just blows through without > skipping a beat > -no late debug shell, again I get the type exit message, and the > running shell message with a blinking cursor on the line below, but no > prompt. I can type, but there is no prompt so nothing happens when I > hit enter. > -I can switch to ps2,3, and run dmesg which looks ok, but logcat > gives me "Illegal instruction".
> On Dec 1, 7:12 am, smarte <raf...@gmail.com> wrote:
> > On the Acer AO521 AMD Athlon Neo netbook is it not possible to boot > > intoICS4.0. > > I get on the boot up screen "loading android".. but noting is > > happend.
> > Thnaks for the hard work... developers..
> > On 1 dec, 03:45, Stephen Ferrell <stephen.ferr...@gmail.com> wrote:
> > > Just finished trying this on an Iconia W500. Wireless worked but it > > > took several attempts to successfully connect to my router. No touch > > > screen or audio. But everything else worked quite well. Google > > > Market also worked just fine.
> > > On Nov 30, 11:53 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> > > > Hi all,
> > > > Theics-x86 branch based on Android 4.0.1 is ready. > > > > You may download the source as usual:
> when typing logcat in the console I get - "Unable to open log device '/ > dev/log/main':No such file or directory", why is that? > Thx
Bzbit, after building without -DUSE_SSSE3, I now get the same error. What processor & video chip are you trying to run on? Mine is k8 w/ RS780.
> You have posted tx2500 builds in the past that worked great for me. > Any chance of a one for the 3.2 or 4.0 builds?
Sure. CW is the one who posts the iso's. Due to google not releasing the honeycomb source until ics, I didn't have the code until after he posted the other RC1's. But I have made the necessary modifications and have been testing honeycomb and it is worthy of an RC release. I'll let him know.
