View Single Post
  #126 (permalink)  
Old 10-08-2010, 01:36 AM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - Keyboard Mapping Fixed, HW3D, and Battery Algo Update

Quote:
Originally Posted by hceuterpe View Post
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
not really.. i know android does have some minimum requirements and i think for froyo it was .29.. but we later found out that was not the case. But then again our kernel has so much crap backported from higher kernels its hard to even say where we are at anymore. For example in nand we are running the usb gadget framework which is from .32 .. yet we run it happily.

jump to .32 is not worth it. If we are gonna move up might as well go all the way. Also the biggest reason why its so hard to jump is because we support so many devices. So we can move rhod, but the other devices would be left behind. Getting all the devs to agree on stuff isnt alwys easy. You should read some of the logs ..lol

wanna contribute ? joint us on #htc-linux
__________________
Reply With Quote