Ok, I was finally able to reproduce / notice it....
......
Any one else up for random file switching?
Sure, just give me a few files to try and I'll step through one at a time tonight.
Ok, I was finally able to reproduce / notice it....
......
Any one else up for random file switching?
Sure, just give me a few files to try and I'll step through one at a time tonight.
Well, I its the surfaceflinger file so I would start with downloading other ROMS that are based on our chipset, like the Sprint version for example and try there build.
But in all honesty, its almost identical to our build so it may also have the problem. It seems like an error that Samsung needs to fix thats why flashing those other files is just a shot in the dard.
Not 100% sure, someone else will have to chime in.
Well, I its the surfaceflinger file so I would start with downloading other ROMS that are based on our chipset, like the Sprint version for example and try there build.
But in all honesty, its almost identical to our build so it may also have the problem. It seems like an error that Samsung needs to fix thats why flashing those other files is just a shot in the dard.
Not 100% sure, someone else will have to chime in.
Other carrier versions produce the same problem. I've tried them.
((all hail the African Canadian sock monkey))
Unless someone has explicitly patched the libs for the other variants, I highly doubt any of them will work. It looks like Samsung has quit bothering to maintain the CRT methods in their libs going forward.
Ok well, Thats what I figured but it was worth a shot.
Looks like we are going to have to go deep on this... Or scrap it....
Anythoughts on how we can port the fix into this lib without building it from scratch and importing CM9 Code? And even then?
Also, has anyone tried the CM9 lib.
IM just brainstorming.
AFAIK we can't build the lib from scratch. There's no source available and it's likely more complicated that it's worth write yourself (akin to trying to write your own driver). I don't know if libs are included in source releases or whether they fall under the 'proprietary drivers' category. So if/when Samsung releases ICS/JB source, I don't know if it will remedy this situation or not.
That said, it appears to be a rather simple fix. The process looks to be:
- Open the lib file (I think this is done with a hex editor. The file is compiled and signed in some way such that pulling it apart isn't really viable. It also has a fixed size that can't change.)
- Find the correct spots to add the CM9 code referenced in one of the earlier links
- Remove a few unimportant lines to make room for the added code
And that's it. It's not really any different than opening up an apk and adding a few lines. The only problem/question is how to edit lib files. I ended up opening it with a random hex editor and I can see a portion that is readable and consistent with the source that goes into it. I even found one of the function calls that need to be tweak. The problem was that it was just garbled enough to have trouble distinguishing where the code went. So either it's going to take a little deduction and trial and error, or I'm wrong about the hex editor and there's an easier way to do it.
In any case, learn how to edit lib files, and it's trivial to accomplish, since someone else has done the real legwork.
This has been reported on the sprint model as well as the verizon one. Look at Bean's rom's changlelog. He removed it at build 6 I believe. When i asked about it he said too many ppl were experiencing the flickering problem.
Bummer. Thanks for the info though. Here's a post on how to accomplish it, if anyone is feeling frisky. Looks like you have to make room for some bytecode additions. I'd do it myself if I were familiar with the process or had the time to learn.
http://xdaforums.com/showthread.php?p=26608114#post26608114
http://xdaforums.com/showthread.php?t=1676378
Ok well, Thats what I figured but it was worth a shot.
Looks like we are going to have to go deep on this... Or scrap it....
Anythoughts on how we can port the fix into this lib without building it from scratch and importing CM9 Code? And even then?
Also, has anyone tried the CM9 lib.
IM just brainstorming.