NexusHD2 Android Forum

Osprey00 wrote:tytung, is this anything useful?

0001-Forward-port-surface-dithering-from-CM10.2.patch


As I mentioned the other day, my theory is that it's related to Android's HTML rendering components. The screen goes black in Google Now/Search only when you do a search that requires web results. My guess is that the Currents and Facebook apps are querying the same HTML rendering component of Android. It makes it easier on the app developers, after all, to use web data whenever possible (especially when all of Facebook is on the web already, anyways), instead of needlessly duplicating everything in the app. If we can determine what that HTML rendering component is and either fix it or replace it, we'll likely fix all those apps that depend on it. That's my theory, at least. I believe that I read something about Google replacing the old WebView renderer with a Chromium-based one in KitKat (or something like that), so that could be the underlying change. Beyond that, I don't really know enough to pursue the problem solving much further, though. Hopefully, tytung can use this info to find the solution.

EDIT: To add to this, through some searching, I found that this is/was a problem on KitKat ROMs for other old phones, like the Desire HD (similar to the HD2) and the Nexus S. In a Nexus S thread, I found this guy's post:

http://forum.xda-developers.com/showpos ... tcount=366

That's what I was thinking, too, that the web renderer is making a call to graphics libraries that's failing. That would be why you get only a black square, yet you can click around on it to access the links that you can't see (meaning that the actual data is there).

Also, he followed up with this large post that suggests that he made some progress:

http://forum.xda-developers.com/showpos ... tcount=382

...then this one that suggests that the CM team fixed the bug:

http://forum.xda-developers.com/showpos ... tcount=393

I wonder why we're still seeing it, then. Perhaps the changes aren't in the particular versions used in our ROMs or they're enough to fix the issue for that chipset, but not for ours. I don't know, but I'm throwing everything out there in hopes that tytung knows what (if anything) to do with it.

Paxy wrote:An issue I have face off,
When I try to get AnTuTu Benchmark results, on 3d OpenGL test HD2 reboots.
When I start test without 2d,3d test, it is completed successful.
Same issue is presented with your CM10.2 V3.3.

draganbre wrote:I have a problem with opening package
"E:Can;t open/sdcard/NexusHD2-KitKat-CM11.0_V4.2.zip
(bad)
Installation aborted."
As for example NexusHD2-KitKat-CM11.0_V4.1 works.
Any ideas?

draganbre wrote:I have a problem with opening package
"E:Can;t open/sdcard/NexusHD2-KitKat-CM11.0_V4.2.zip
(bad)
Installation aborted."
As for example NexusHD2-KitKat-CM11.0_V4.1 works.
Any ideas?

Paxy wrote:An issue I have face off,
When I try to get AnTuTu Benchmark results, on 3d OpenGL test HD2 reboots.
When I start test without 2d,3d test, it is completed successful.
Same issue is presented with your CM10.2 V3.3.

PoJD001 wrote:Thanks. But the improved battery life was just a nice side effect of the performance optimizations. If I was after battery life, I wouldn't have chosen ondemand, but probably conservative or smartassv2 governors... I took a brief look at the app you mention and found varying results on xda. I honestly don't trust some magic apps that suddenly improve everything. I understand how it roughly works, but these beasts are not for me It is a background running app after all anyway, right. So it will eventually consume system resources anyway, which I am trying to minimize. It is like say using superfetch in Windows 7 for me. Am naturally skeptical to these smart apps... Android was designed certain way and I just use it that way (keep closed apps in memory too to speed up next invocation, etc). Thanks for your suggestion anyway.