Open GoogleCodeExporter opened 9 years ago
I'm disappointed but the team has made great job !!
No problem...if i have to wait a solution to resolve this black screen problem
;-).
Bye
Original comment by kudo...@aol.com
on 21 Jan 2012 at 3:56
I have the same problem with black web browser using android-x86-4.0 on both
Asus EeePC 900a and on HPmini 210. This did not happen with
Android-x86-2.3-rc2 using my EeePC 900 but never tried 2.3 on EeePC900a nor on
HPmini 210. Everything else on 4.0 seems to work well and more smoothly than
2.3 so I was both surprised and a bit disappointed.
Original comment by mhmon...@gmail.com
on 22 Jan 2012 at 1:43
Hello !
tested android-x86-3.2-RC2-tegav2 on my Samsung N150 and now web surfing is
ok...but i've found some other bugs : no usb detected (perhaps it's "normal" ?)
; Open Manager crash ; soft reset sometimes when i install apps (like firefox
-> don't run too).
Bye.
Original comment by kudo...@aol.com
on 22 Jan 2012 at 9:43
Same here on a Asus EEPC 900a
Original comment by mike.pre...@gmail.com
on 7 Feb 2012 at 9:34
I did build a TegaV2 (ICS) image on codebase 06.02. problem exists.
Original comment by hurr1k...@gmail.com
on 8 Feb 2012 at 11:05
Found the Problem. Rendering with openGL ins the Problem.
For non developers:
-open Browser
-type about:debug in url-field
(Nothing happens!)
- go to settings
-debugging
-deselect "enable opengl rendering"
Now builtin Browser works.
Devs please leave comment if you have seen this reason and workaround
Original comment by hurr1k...@gmail.com
on 8 Feb 2012 at 6:47
I can confirm that disabling OpenGL rendering does seem to resolve the black
screen in the browser (at least on my machine). I assume that updated display
drivers could resolve this issue, though if the default setting could be
changed, disabling OpenGL would work well as a temporary fix. I am typing this
comment from the Android browser, ICS test build 20120101 (Asus laptop image).
Original comment by TechnoMonkey76
on 10 Feb 2012 at 5:30
[deleted comment]
No more problem with "nightly build"
Original comment by labo.b1...@gmail.com
on 10 Feb 2012 at 9:06
Where can we download "nightly build" for ICS build?
Black screen problem is on many apps (gmail, email, pulse, etc) is this
resolved for these apps too?
Original comment by yym.v...@gmail.com
on 10 Feb 2012 at 5:57
I guess you can build it from the sources
Original comment by sport-l...@dzhigurda.com
on 10 Feb 2012 at 7:19
can someone upload a more recent iso build? I tried all day to create one from
the source without any luck :(
Original comment by david.av...@gmail.com
on 19 Feb 2012 at 8:08
You can install "Droid Surfing" from App Store and that it, you can navigate
web.
Original comment by abelrequ...@gmail.com
on 19 Feb 2012 at 11:34
[deleted comment]
I can surf the web (even with about:debug workaround), but the same problem
happens with gmail and other apps, like youtube, and sometimes even crashes
them down..
I really want an updated build of ICS...
or even a way to fix it without a whole new build.
also, there are nightly iso builds at http://android-x86.moonman.dk/ but they
are all version 2.2, not ics.. :(
thanks a lot for your help
Original comment by david.av...@gmail.com
on 20 Feb 2012 at 7:09
[deleted comment]
I had a graphic artefacts in browsers and it's help me, thanks!
Original comment by zarif...@gmail.com
on 25 Feb 2012 at 7:54
All html content is black. Default email application works without problem,
html gmail doesn't work, default YouTube app crashes on playback, google search
also black content. Also tried other browsers (doplhin hd, opera), result are
same - black page. Maybe it's rendering issues plz help me
Original comment by crazy123...@gmail.com
on 5 Mar 2012 at 11:59
Same for me in my new samsung galaxy s3, the default browser has a grey
background and I can't disable it.. I've tried to disable all the poer save
mode but still the same. Kernel number 3.0.15-611327 android 4.0.4
Original comment by superluglor
on 14 Jun 2012 at 6:47
same problem full of bugs you can't use it.
Original comment by ultragam...@gmail.com
on 3 Feb 2013 at 3:11
Original issue reported on code.google.com by
kudo...@aol.com
on 21 Jan 2012 at 3:54