View Single Post
  #125 (permalink)  
Old 10-07-2010, 11:54 PM
hceuterpe's Avatar
hceuterpe
PPCGeeks Regular
Offline
Location: Illinois
 
Join Date: Mar 2008
Posts: 50
Reputation: 55
hceuterpe is becoming a great contributor
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update

Quote:
Originally Posted by [ACL] View Post
How is Nesoid actually scaling? i want the actual gpu to do the scaling for us not it be handled by a library or android. Android itself will think its running a completely different resolution.

.35? haha.. new kernel. We are running .27 while everyone else is probably running .32. We would run on cleaner code and about 2.5 years worth of improvements. Not to mention bragging rights. You can actually tell someone "your kernel is dog shit.. .35 bitch !!!"

turns our blackstone has headset working, so im going to see if we can use the same code for rhod. Lets cross our fingers.
Hate to rain on anyone's parade, but I always thought it was weird to say the TP2 was running Froyo, yet had only a .27 kernel. Correct me if I'm wrong, but isn't every Android version built from a particular kernel version? So Cupcake (v1.5) is .27, Donut (v1.6) .29, Eclair (v2.0/2.1) on .29 still, and of course Froyo .32?

I personally would feel irked jumping ahead with .35 just yet, but Gingerbread is based on .35 so it wouldn't hurt to think of at least. It might be the software developer mentality in me to want to stick to official versions at least somewhat in ports. I've been reading some of the specific details of the differences between the different versions--I would think at least some of those changes have to be kernel related, and it would definitely help the TP2?

For instance, our phones have Bluetooth 2.1 EDR, and the Android bluetooth stack is based on both BlueZ which in turn is built into the kernel and that doesn't support BT 2.1 until BlueZ v4.x which starts at Android v2.0 and at least kernel .29 (we have 3.3x something). I wonder if Bluetooth would be easier to get working if we simply moved to .32? I've heard all sorts of problems related to Bluetooth in Android versions below 2.0, and that's only with phones that only have Bluetooth 2.0 (not BT 2.1 like do).

So I don't sound like a total bitch, I can try to contribute by merging the kernel code from .27 to .32? Man, that's such a huge jump!! :O
Reply With Quote