View Single Post
  #516 (permalink)  
Old 11-24-2010, 04:06 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - Auto-brightness Testing: 10-28. Automatic Keyboard Detection!

Quote:
Originally Posted by [ACL] View Post
Did you test with 3d enabled ? the tearing and missing frames are probaby due to copybits. This is a userland lib that may need adjusting to play nice with the new framebuffer. I tried cyanogen again and the startupscreen there is actually really smooth but i get the same copybit error there as well. For 3d to work well we need copybit and gralloc to be flawless. right now they are failing.
Yeah, 3D is always enabled for me. I still have the force command in tinboot, but I thought for sure you had hard coded it to always be enabled since it was working properly.
Reply With Quote
This post has been thanked 1 times.