Sådär nu har en kille på modacos forum, ''PlaguedByPenguins'' portat över konstas 10.1 rom (zte blade rom) till våran platta Tråden finner ni här: http://www.modaco.com/topic/361573-devrom-cyanogenmod-101-android-422-for-v9/ Verkar även som han eventuellt kommer fortsätta uppdatera denna För tillfället ska det mesta fungera, men blutooth kan vara lite krångligt. Håller på att installera denna nu, återkommer senare med mina intryck Saxxat från tråden på modaco: this is a CyanogenMod 10.1 based ROM for ZTE V9 - the resistive screen model. it is based on KonstaT's http://www.modaco.co...01-android-422/ for ZTE Blade and all the same caveats apply here. please read all of KonstaT's first 3 posts before trying the below. In particular please note that this is not an official CyanogenMod rom and expect it to eat all your data and brick your v9. you have been warned. having said that, it works fine for me cm-10.1-20130324-PenguinKANG-v9.zip md5sum 8f51747035e798878299d4d894095a13 NOTE: - you will need >190MB in /system to flash this rom (my .au Optus v9 has 220MB), and initial boot will take ~5mins - this ROM is for the resistive screen V9's. there are a couple of files in this rom that know about capacitive models, but they are completely untested Working everything seems to work. specifically all those listed on KonstaT's page. AFAICT the only thing that's regressed from cm7 on V9 is - multi-touch (pinch to zoom) emulation from cm7 makes the browser go crazy on cm10.1, so it's disabled Issues known issues specific to this ROM - pre-surfaceflinger boot animation is wrong aspect and off centre - ElectronBeam power-on animation doesn't work (power-off does) known issues from upstream (AOSP or KonstaT or ZTE or ...) - AOSP keyboard gesture typing doesn't (won't ever?) work on arm6 devices - FM volume control works only after using Apollo first - no movie preview images - bluetooth scanning works but is unreliable suggestions and patches are welcome for all the above issues!! Bluetooth ah, bluetooth. sigh. there goes a week of my life. so the best way to scan to find a new bt device is to turn on bt from the main Settings screen and wait until bt is on for a few seconds before going to the Bluetooth devices screen. if scanning doesn't start immediately on that screen then it has failed, so go back to Settings and turn off bt and try again. be patient. scanning works about 30%-50% of the time using this method. once paired, bluetooth devices are ok - it's only this initial scanning stuff that's dodgy. Building - all sources are on my github - to build follow all KonstaT's instructions in his 3rd post, but except instead of getting the blade manifest, get my v9 manifest like this: curl -L -o .repo/local_manifests/manifest_zte_v9.xml -O -L https://raw.github.com/plaguedbypenguins/android_local_manifest/cm-10.1/manifest_zte_v9.xml ChangeLog 2013-03-24 fix for the StatusBar / SystemUI hang - turned out to be an AOSP bug with events that report identical times 2013-03-22 initial release changed governor to smartassV2 backported uhid driver from 3.8 kernel so that BT keyboard etc. work ... Many thanks to all those working on CyanogenMod and armv6.