And if you would rather not be patient, ask Google, practice using ADB, and read up on how to build Android. The information is all out there, but the very small number of people who follow this thread who can give you the quick-ish (and hack-ish) answers are busy trying to figure out better ways to make AOKP stable and functional on our phones (i.e., without having to resort to hacks like deleting system files that disable the use of Market). Let them do their business and have their fun playing in the Android sandboxes, and in the meantime Quattrimus CM9 is pretty dang stable.

that really doesn't answer the question lol did the devs figure out how to make a wrapper for the gb drivers? just curious as to how they hardware acceleration is working on the beta build

Sent from my LS670 using Android Central Forums

No, they have not, and likely never will.

Hardware acceleration DOES NOT WORK.

It means hardware acceleration has a snow ball chance in hell of working on this phone, since qualcomm will not write the omx drivers and will not release the closed source programing necessary to get them to work. You have a better chance of winning $100 million in the lottery.

It means hardware acceleration has a snow ball chance in hell of working on this phone, since qualcomm will not write the omx drivers and will not release the closed source programing necessary to get them to work. You have a better chance of winning $100 million in the lottery.

are you saying i'm NEVER going to be able to watch netflix or play TINYzoo on my ice cream sammich phone?

are you saying i'm NEVER going to be able to watch netflix or play TINYzoo on my ice cream sammich phone?

Probably never, yes. We're using a phone that is, for all practical purposes, no longer being sold in stores, and the developers in charge of writing drivers for our hardware are not interested in porting drivers to newer operating systems (e.g., ICS). Community developers may take up the slack, but that could take awhile; if too many community developers move on to newer phones before they get around to porting the graphics drivers to ICS, we may never get the fancy graphics support on our OVs.

Probably never, yes. We're using a phone that is, for all practical purposes, no longer being sold in stores, and the developers in charge of writing drivers for our hardware are not interested in porting drivers to newer operating systems (e.g., ICS). Community developers may take up the slack, but that could take awhile; if too many community developers move on to newer phones before they get around to porting the graphics drivers to ICS, we may never get the fancy graphics support on our OVs.

Hi everyone, thanks to tdm's libaudio patch I was able to compile my updated version of wpa_supplicant to enable adhoc support. This will let your phone connect to other adhoc wireless networks.

Example: your 3g has bad reception and theres no wifi around, have your friend turn on his adhoc wifi hotspot on his phone, and you can connect to it. Adhoc networks will say (adhoc) next to their name. works for cm9.

Note it is the default cm9 wpa_supplicant v6 that tdm used in his build, so it should work with any cm9 rom that uses the default wpa_supplicant v6

Instructions:
1. make a backup of /system/bin/wpa_supplicant
2. Turn wifi connection off
3. copy the new version into /system/bin
4. turn wifi connection on

As above. Froyo and Gingerbread have been available for these phones for a long time now and Qualcomm released the drivers. ICS is new, our phones are not current, out of stock in many places, and Qualcomm is not going to write drivers for deprecated hardware.

I'm aware that AOKP is broken, however, it is functional(just with market, media, and a few other things aren't functioning). I still use it, cause i can live without the market, and PowerAmp is the only media player that works more so than others. (WinAmp is the only other one that partially works on AOKPb1p1)

I think it has something to do with Power Amp not using the built in media client that is in the ROM. (and broken in AOKPb1p1).