View Single Post
  #460 (permalink)  
Old 11-09-2010, 12:19 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
Alex and I are experimenting more and more with different framebuffers. We did notice that the new framebuffers seem to wake up the phone better. I dont know if you notice now sometimes it takes the screen a while to come back up.

Issue is that Google and CodeAurora have completely different framebuffers. The one im specifically working on is from Google (HTC uses google FB). But other devices like samsung use CA. Now we haven't had success yet in getting the CA FB to work. There is a big possibility this may be a faster FB which will make the tp2 fly... but thats all in the works.

This is a big change (prob bigger than the USB), so it will take a while to iron everything out.
You've got a bunch of testers ready to rock whenever you've got something for us to give feedback on

And thanks for keeping us up-to-date. I still haven't had a chance to look at any commits that were made to linux-msm that weren't applied to nand. Got kind of sick over the weekend, and I still haven't quite recovered.
Reply With Quote