[G2 and Desire Z Android Development] HTCDreamOn:
Feedback time! yay, I've attached logs! :) but not for Swag paper props., I think that was me not having WiFi on and an anomaly... Works fine now :confused:

First of all... thank you so much for this, adamz667, Iv'e been waiting for this ever since I started using Flinny's CM10.1 builds. Unfortunately the timing of my buying my Vision meant JB had already come into existence, so I never tried your ICS AOKP (sorry :crying: ) but man I love this.

I can tell you've put a lot of effort into this, I'm glad we've got a source compiling AOKP dev for the Vision. Anyway....

When tablet mode for the status bar is selected (combined nav buttons and status bar), the status bar transparency is made redundant... that is, the status bar transparency setting doesn't work (nor if I set navbar transparency as well) but I don't know if this is meant to happen :confused:

When in status bar tablet mode, when the brightness tile is selected from the notif. toggles menu, the slider appears behind the notifications, meaning they have to be closed in order to change it

If custom carrier label is set, it prints it twice for wifi and network (usually it would say "EE" for my network and my SSID for wifi next to the corresponding signals, instead it says "AOKP" (what I set) next to both... I doubt this is your fault though.

Either navbar widgets don't work or I don't now how to set / use them

If tablet mode for status bar is set, if the navbar height is dropped lower than 48dp default, then notifications do not comply to this rule and appear larger than the status bar when broadcast

Storage settings FCs... This may be because I've installed the swap enabler (only apps to Sd-Ext, I don't use swapfiles ever.

I use OC Daemon, I've noticed if screen off is set to 245MHz main 368MHz Max conservative governor, I cannot awake from deep sleep (sometimes)... Setting 368MHz main powersave is OK though. OK turns out I lied... if the screen turns off after booting, that is if you don't unlock it and instead allow the screen to turn off straight after booting, when you try to turn the screen on again, only the buttons illuminate and the screen half turns on (it goes grey). Can someone confirm this, or is it OC Daemon / too low a clock speed (although this does not happen after the first screen off, as long as you unlock it first, you can then safely allow the phone to sleep)

Themes don't work: when you apply a theme, literally as soon as it applies the phone reboots (from bootanim., not splash screen) with lights on, and bootloops. Only fix is to battery pull, boot recovery, and remove the .apk of the applied theme with Aroma file manager.

Linux chroot won't work :crying: but this isn't a massive deal.

I've noticed CyanogenMod has definitely caught up with AOKP in some areas. There are more (useful) toggles in CyanogenMod, and atm simple things like button remapping isn't an option, although I figured this was because AOKP is originally built for Nexus devices with on screen buttons.

hmm... OK, I've figured this isn't up to be my dd yet, but I'll test when an update comes out :)

Also, on the official AOKP threads they have an AOKP "theme" sort of thing going on... I mean they have an AOKP banner and headings and stuff... take a look. Just wondering if you would be allowed to use them.

Also, am I allowed to use the "AOKP User" banner in your sig. ... 'cause I'm an AOKP user now ('cause of you, thanks :laugh: )