Database Users

Honeycomb Hope

There is hope for Honeycomb on our tablets! The og moto droid recently can run Honeycomb. So hopefully when the sourcecode is released it will run swell on the Archos 101. http://forum.xda-developers.com/showthread.php?p=13573812#post13573812

Even the G1 can run honeycomb (it was the pretty-first android device in the world^^)
But the problems are the source, and i don't think that google will release the source code, no matter why...
But i've hope for ice cream sandwich (will released ~Q4 of 2011)
This will be Android 4.0 and it will comprise Honeycomb and Gingerbread

i'm not sold on the idea that it'll work on the our gen 8's

Porting Touchscreen Drivers
Hi,
AS I understand it, the major problem is the touch screen driver.
Reading the posts here, I don't understand how can u port a driver without the source code of the current driver from Archos.
As there is no current open source driver for this screen (and yes, I have read the "Porting Touchscreen Drivers for ROM's - Instructions") So the driver needs to be written from scrap or ported from the Archos source code.
So as I understand it, our best and might be the only chance for android 3.0 port is to ask for the driver source from Archos and port it, or wait for a port from Archos to android 3.0 .
Am I getting it wrong here ?

RaananM said:
Am I getting it wrong here ?
Click to expand...
Click to collapse
A little bit is wrong
I summarize the hole story now:
The touchscreen drivers aren't the only problems about porting honeycomb.
If we're able to compile the drivers (as i wrote in my thread) we could bring the honeycomb Mod to run.... BUT we have no sources! Thats the biggest problem we've
There are a few honeycomb roms, but these one has many bugs (wifi dont work for example)
And i think with a little bit of work, we could get this roms to work, but with these big bugs te tablet is ruined and if google dont release the source code these roms not getting better.
I've hope on Ice Cream Sandwich.

Ok.
but we still can't do a thing without the source to the driver. Or are there any ROMs which support our screen ?

RaananM said:
1) But we still can't do a thing without the source to the driver.
2) Or are there any ROMs which support our screen ?
Click to expand...
Click to collapse
1) Of course! We gonna compile our own drivers (kernel) please look here:http://forum.xda-developers.com/showthread.php?p=13944810#post13944810
2) Nope,unfortunality we've the only android device with this touchscreen

OK. been reading in your pointers and got to -
http://forum.xda-developers.com/showthread.php?t=891056
Do you know where does the code in
git://gitorious.org/archos/archos-gpl-gen8.git (from the howto Makefile)
comes from ? Archos ? or is it pure android ?
Thanks for your help.

RaananM said:
OK. been reading in your pointers and got to -
http://forum.xda-developers.com/showthread.php?t=891056
Do you know where does the code in
git://gitorious.org/archos/archos-gpl-gen8.git (from the howto Makefile)
comes from ? Archos ? or is it pure android?
Click to expand...
Click to collapse
Its from Archos why you ask?
Thanks for your help.
Click to expand...
Click to collapse
Then please klick thanks

Yes we need Touchscreen drivers, where as Vegancomb is already in development which is almost in B1 phase.

compyy said:
Yes we need Touchscreen drivers, where as Vegancomb is already in development which is almost in B1 phase.
Click to expand...
Click to collapse
Yes,but its not the only step we've to take...
Anyone who could do this (I've found an How to at the web )

what is Vegancomb

I'm pretty sure Google said they are not releasing HC source at all, period. The way I understand it is they have basically turned HC into a holdover for tablets they endorse till they compile everything together for phones and tablets with ice cream sandwich at which point the ice cream source will be released. It seems to be to keep just anybody from throwing HC on a device and selling it and possibly causing a bad user experience and making google look bad. Also most likely to help with fragmentation issues.
None of this of course helps us any....just what I've read and how I understood everything.
Sent from my ADR6400L using XDA App

sorry i meant VegaComb BETA 1.3

[CRAZYTHEORY] Joint HC Developement?

Hello there,
I have this theory... I want to hear your opinions to see if I'm just crazy or I'm correct in thinking this.
After seeing how the unmodified Acer Iconia Galaxy ROM + modified ASUS Transformer kernel (Clemsyn's) worked on a Transformer I started to think that this could be because of all the Honeycomb tablets are running a pretty similar OS configuration ("stock-like" Honeycomb).
Am I right in thinking this (I haven't actually used any other HC tablet except the Iconia)?
If this is right, it kind of explains why an unmodified ROM developed for the Iconia works with our device, as they are using pretty similar systems. The main difference, of course, is the hardware. This explains the wifi, battery and other issues in this example. This was partly corrected from the use of an ASUS TF kernel (Clemsyns) with the same ROM since the kernel provides the needed interfaces, modules, whatever for the respective hardware.
Of course, the kernels between the devices, I'm assuming as I haven't actually compared the source, are pretty similar aside from certain hardware modules that have been left out during compilation, as they are both just modified Linux kernel. This explains why the Iconia ROM worked (mostly) even when using an Iconia kernel.
So am I right with all the above, or am I missing something obvious, or am I just crazy (2am and my PC's made my room very hot afterall)?
Okay, so if the above is correct, couldn't/shouldn't we be doing some cooperative developement with other Honeycomb device developers? Or at least the Iconia developers, as I'm not sure about other devices. I mean, if the ROMs are pretty much compatible, all that would need to be done is have a respective kernel for the respective device flashed on-top of the ROM, right?
Anyway, laugh at me, flame me, tell me to go to bed, whatever, but I'd like to know what your thoughts are.
And on a related note:
Has anyone actually tried flashing any other "other-device ROMs" onto a TF with a TF kernel and got it working?
I'd love to try, but my internet is terrible... I swear someone else on the network constantly has their BT speeds uncapped 24/7 (share-house's are ****ty).

I think that's pretty much the goal of the CyanogenMod project. Only reason they haven't begun on a Honeycomb version is because Google never released the AOSP. Hopefully this will change with ICS.

Yes, the OEMs are working together with google behind the scenes.
More than likely Google has "forced" them to contribute code in order to participate and enjoy early code.
Unified code at the OS level would be a godsend and allow for Windows - style updates.

poltak11 said:
After seeing how the unmodified Acer Iconia Galaxy ROM + modified ASUS Transformer kernel (Clemsyn's) worked on a Transformer I started to think that this could be because of all the Honeycomb tablets are running a pretty similar OS configuration ("stock-like" Honeycomb).
Click to expand...
Click to collapse
As far as I'm aware, pretty much all the current crop of Honeycomb tablets are all based on the Nvidia Ventana reference platform, so it's not too surprising that they are all very, very, similar software-wise.
Regards,
Dave

JCopernicus said:
Yes, the OEMs are working together with google behind the scenes.
More than likely Google has "forced" them to contribute code in order to participate and enjoy early code.
Unified code at the OS level would be a godsend and allow for Windows - style updates.
Click to expand...
Click to collapse
But as the OEMs are working together, why aren't independant developers here on xda? I mean, I'm just thinking that a lot more nice work would get done if there was unified developement going on between the HC devices instead of seperate forums, and seperate ROMs that seem to be very similar.
And yes, I do agree about the closed source problem. But Google said this is just a temporary thing, right?

It's hard to write too much code when you don't have the original to start with.
No one really wants to write Honeycomb from scratch.
sassafras

sassafras_ said:
It's hard to write too much code when you don't have the original to start with.
No one really wants to write Honeycomb from scratch.
sassafras
Click to expand...
Click to collapse
I understand this, of course, but excuse my ignorance when it comes to Android Developement, but what are the developers of PRIME and Clemsyn's ROM and all the other HC ROMs working with at the moment, as there is no source other than the GPL'd kernel?

poltak11 said:
I understand this, of course, but excuse my ignorance when it comes to Android Developement, but what are the developers of PRIME and Clemsyn's ROM and all the other HC ROMs working with at the moment, as there is no source other than the GPL'd kernel?
Click to expand...
Click to collapse
They are working with the OTA. It is all compiled things. They can add things on top of it, but they can't do modifications to it because its already compiled (source code not provided).

zephiK said:
They are working with the OTA. It is all compiled things. They can add things on top of it, but they can't do modifications to it because its already compiled (source code not provided).
Click to expand...
Click to collapse
Ah, fair enough. Well assuming that Google actually does release the source-code sometime, will this sort of thing be happening? As in co-developement between devices?
It just seems like the sensible thing to be happening, as opposed to a greatly splintered "fork" style of developement.

poltak11 said:
Ah, fair enough. Well assuming that Google actually does release the source-code sometime, will this sort of thing be happening? As in co-developement between devices?
It just seems like the sensible thing to be happening, as opposed to a greatly splintered "fork" style of developement.
Click to expand...
Click to collapse
Chances are there will be a CyanogenMod type project once Android tablet sources are released.
However, there will always be developers who are primarily interested in doing their own thing, which is perfectly acceptable too.
Regards,
Dave

poltak11 said:
Ah, fair enough. Well assuming that Google actually does release the source-code sometime, will this sort of thing be happening? As in co-developement between devices?
It just seems like the sensible thing to be happening, as opposed to a greatly splintered "fork" style of developement.
Click to expand...
Click to collapse
There's a reason CM hasn't officially touched any Honeycomb tablet. There's no source. Once they open up the source with ICS then everyone will be working on it through github.

[Gen8] ICS on Gen8 (A70S) preview

Hi All,
Here is a quick preview of my first ICS build running on my A70S:
It's smoother than my initial run, I figured that 3D drivers were not kicked in when I made the comment on my other thread.
It's quite smooth even though there is some slowness from time to time. As it is, it's not usable, there are some crashes because network and sound are not working, but it's quite encouraging.
I may focus on Gen8 more than Gen9 finally as Gen9 will have Archos upgrade. Currently, only 3D and touchscreen are working... Don't expect much, I don't have enough time to work on this to make significant progress quickly.

Great...finally is something!!!
I you want some help, tell me....ok?

Looks great, that launcher is really smooth and it looks like a completely new OS.
Is there any chance that other talented developers working on the Archos will also jump on this with you? $aur0n, divx118, chulri?

God i cant wait for this give me wifi and i will be happy whats ram usage like?

for the buzz
http://www.jbmm.fr/?p=24894

Well, as expected, ram usage is sky high but it's almost untuned... I don't know yet if we can make progress regarding this.
I want first to have wifi and audio working, it should give enough stability to start playing with it. Then, todo list is huge...
Things that are going to be difficult is hdmi, ics doesn't like much the current clone model, and supporting other tablets as kernel changes are required for touch screen.
We'll see... Too bad that I have a job

Awesome!
Great work man! Looking forward to a full release_
-------------------------------
Sent from my HTC Desire S

YES!
This... Is amazing.. I never thought I'd see the day where even Honeycomb was running on the tablet. I really hope the main devs here see this and maybe combine. It's awesome having such a fine-tuned and packed UrukDroid, and it's pretty great finally seeing Gingerbread on our devices, but I think this is the true goal now!.. But that's just me

Hey letama,
now i know what you meant with good news coming...
letama said:
It's smoother than my initial run, I figured that 3D drivers were not kicked in when I made the comment on my other thread.
Click to expand...
Click to collapse
Could you tell, which driver set you integrated?
I also searched for ICS distributions for OMAP3630 base devices.
Couldn't find any 3D libraries yet...
letama said:
It's quite smooth even though there is some slowness from time to time. As it is, it's not usable, there are some crashes because network and sound are not working, but it's quite encouraging.
Click to expand...
Click to collapse
Am i right by assuming you used the 2.6.35 kernel sources?
I guess we'll need some efforts in the drivers, especially the tiwlan stuff, which should be build externally.
letama said:
I may focus on Gen8 more than Gen9 finally as Gen9 will have Archos upgrade. Currently, only 3D and touchscreen are working... Don't expect much, I don't have enough time to work on this to make significant progress quickly.
Click to expand...
Click to collapse
This is a start... and a pretty amazing one!!!
Hopefully i'll find some time the next weeks to look into the kernel sources more intensely.
Anyway, it will be no easy task to add the missing parts.
For the HDMI i guess there is a dead end, because there's still one proprietary module which might not work with newer kernel.
Maybe it could work on top of the GPL'ed parts which where published and might get compiled for newer kernel.
But who cares now...
Really impressive work!!!
Congratulations and best regards,
scholbert

Can you upload the rom just for testing features of ics ? It looks very good, great job !

Hi Scholbert!
scholbert said:
now i know what you meant with good news coming...
Click to expand...
Click to collapse
scholbert said:
Could you tell, which driver set you integrated?
I also searched for ICS distributions for OMAP3630 base devices.
Couldn't find any 3D libraries yet...
Am i right by assuming you used the 2.6.35 kernel sources?
I guess we'll need some efforts in the drivers, especially the tiwlan stuff, which should be build externally.
Click to expand...
Click to collapse
No, in fact, this is 2.6.29 with Archos 3D binaries. ICS is patched to support old drivers, partly the same way it has been done in cm9 for other devices. I didn't test the .35 yet, I suspended my work on it in the middle, I'm not even sure touchscreen was working.
.35 would be good, I'm having few crashes in 3D drivers currently. I'm not sure yet if they're related to memory or bad interaction somewhere, still trying to get audio and wifi first.
Wifi should be relatively easy, i'm not very far. Audio is more complex, I tried simple solutions and it won't cut it, but with TI and Nexus S sources, we should be able to do something. Could take time though.
For the HDMI i guess there is a dead end, because there's still one proprietary module which might not work with newer kernel.
Click to expand...
Click to collapse
Well, with the new A70s coming with Honeycomb, we may be able to steal some binaries for 2.6.35 (or even 3.0 if Archos upgrade them to ICS). They're also 3630, and we should get the kernel source code someday.
scholbert said:
Congratulations and best regards,
Click to expand...
Click to collapse
Thanks!

arkade91 said:
Can you upload the rom just for testing features of ics ? It looks very good, great job !
Click to expand...
Click to collapse
Well, as it is, it's not usable. It crashes a lot and you can't do much without network.
I'd like to have at least wifi and if I can sound. Wifi to be able to do something with the tablet, sound because lots of crashes and slowness are coming from missing sound.
If it takes too much time, I'll release it but be warned that it's worthless currently.

letama said:
Well, as it is, it's not usable. It crashes a lot and you can't do much without network.
I'd like to have at least wifi and if I can sound. Wifi to be able to do something with the tablet, sound because lots of crashes and slowness are coming from missing sound.
If it takes too much time, I'll release it but be warned that it's worthless currently.
Click to expand...
Click to collapse
Yes you're right, i hoped never get honeycomb or ICS on our tablet... take your time, it's already a very good news that ics running on our old archos gen8 ... THANKS !
Sent from my A101IT using xda premium

Where can I donate?!?
Very good work, I never thought that this would happen.
Honeycomb was not realistic but now I have hope for something better

Thanks GPhenom for thinking about donation, but I can't accept for now, I'm not even sure I'll be able to release something.
We'll see, but there is lots of work before having something usable.

Promising start man! Kudos for getting it running at all
Sent from my openAOS Build of Android 2.3 (cyanogenmod edition) using xda premium

This look cool
Can you make source repo (git) for this please
I would like to build it and test to get wifi and so working
and good work

Cool! Hope to see a first alpha

Sweet, buying a Archos 70 (hopefully Gen8, got to look that up first) today. Just awesome work dude!

AlphaTime said:
Can you make source repo (git) for this please
I would like to build it and test to get wifi and so working
Click to expand...
Click to collapse
Take a look here, I'm not having structured git yet...

The ways to get full ICS on Atrix

There is a great description of the ways to get ICS on Atrix from crnkoj:
crnkoj said:
So lets try to get some light into it, the issue about hw acceleration for the atrix is that, even now that nvidia released proper ICS binaries, those are made for recent kernel versions (post 2.6.39 and 3.x versions), those libs are floating around and are accessible to most people who would want to build stuff with hw acceleration, the problem on the atrix however is we only have 2.6.32 kernel sources from motorola, which in term means all the libs floating around are incompatible and useless. Now there would be two general ways of fixing this: 1. get libs that work with 2.6.32 kernels but are ics compatible (most improbable, except if moto leaks them and is still to lazy to move on from the 2.6.32 kernel) 2. get or make post 2.6.39 kernel sources that have the atrix's proprietary drivers including or rewritten (actually more probable, but still quite low chances, except if moto releases and ICS build for the photon/atrix or someone knows, has the time and will to write these code from scratch for the newer kernel versions). So as you can see this is quite a grim outlook, its still being worked on by community devs as far as my information are up-to-date, but i dont know which aproach they are choosing. There is however a minor glimpse of hope, since the move to integrate android drivers in the mainline/mainstream linux kernel is happening in the 3.3 kernel version (there are 3.2.x versions as of now), so this might be actually the best bet, hoping that most of the atrix proprietary drivers will be supported in it, one could just use the "nvidia libs floating around", another thing is nvidia is maintaining their own tegra2/3 kernel sources, so combined with the 3.3 move to android drivers and nvidia implementing support for tegra into their sources, it might not look so grim for us anymore, but this is all a developing story.
Click to expand...
Click to collapse
Also, there is another comment from one of the CM developers:
OK, since so many people are asking: The reason I'm doing the OMAP devices first is because the fine folks at Texas Instruments have, as before, published their reference code. (and Google's current reference device, the SGN, is an OMAP4, which also helps considerably).
The Optimus 2X (and its TMoUS brother, the G2x) is a Tegra2, and nVidia has, as always, published a total amount of zero useful lines of code; at this point, my time is better employed at getting CM9 off the ground with devices in which I can write code than it would be at figuring out how the hell to support old tegra binaries. It'll happen, but not in the near future.
Click to expand...
Click to collapse
According to this, there are some plans of CM-developers to make some kind of wrapper to use GB tegra binaries for ICS on GB kernel. Great!
Also, a question from me. LG has announced ICS on O2X. Will this release help us? I saw that some developers used O2X GB binaries for Atrix, and it worked even better Can we do the same trick with ICS binaries and get fully working ICS on ICS kernel?

v.k said:
Also, a question from me. LG has announced ICS on O2X. Will this release help us? I saw that some developers used O2X GB binaries for Atrix, and it worked even better Can we do the same trick with ICS binaries and get fully working ICS on ICS kernel?
Click to expand...
Click to collapse
You can never be sure on the software world, but I hope so. A Motorola ICS release would definitely be better though.

Interesting information, thank you!

Easier said than done...
But thanks for sharing the info.
Sent from my Atrix 4G using Tapatalk

Hopefully something will get worked out. I have no plans on leaving this phone as I love the FP scanner too much

if i'm correct, samsung's galaxy r and captivate glide are both tegra 2 phones and they run on the 2.6.36 kernel, which supports hw acceleration to a certain degree, does this help us?

[Q] Is it as simple as compiling cyanogenmod?

Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.

evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?

s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.

I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.

Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.

@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers

What about devices that have CM10 only?

lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.

JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.

As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.

mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.

Please, support for RAZR i (x86)

lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)