[Optimus One, P500 Original Android Development] flanco:
My first post on this, so if i miss something, please bare with me. tx!

I installed a modified cm-10-20120909-UNOFFICIAL-p500 over a cm 7.2 beta.

Modified by editing Latin fonts to only contain EN and removing some specific language fonts linke nanum or lohit in order to reduce storage to be able to install all gapps (tiny version), since i read about insufficient storage issues. Doing this, reduced the System apps with around 25 MB and System fonts with around 12 MB.

The installation went smooth, and installed also gapps-jb-light-20121018-signed and Adreno Upgrade. Verified that an active desktop (bubbles) is working under locked screen, as someone mentioned that it wasn't working prior adreno upgrade.

Set cpu to work 245 to 787 MHz with smartass v2 scheme. Don't go with 122 MHz as on CM 7.2 the device was becoming unresponsive quite often and the only way to recover was pulling out the bat.

Now these being said, some of the problems i ran into:

1. Was trying to use interactive cpu scheme, but noticed that each time i select it, the cpu freq is frozen to the value it was when the scheme activated. It doesn't go up / down anymore. So i had to move to smartass v2. Don't know more which is better, i was using interactive on CM 7.2 and was very good. Might be a problem to investigate.

2. I can't access the alarms. Whenever i open clock and try to enter alarms section, it crashes "unfortunately, clock has stopped". This is ddms' log:

10-28 14:43:54.639: E/Trace(3660): error opening trace file: No such file or directory (2)

10-28 14:43:54.869: E/SQLiteLog(3660): (1) no such column: incvol

10-28 14:43:54.879: E/AndroidRuntime(3660): FATAL EXCEPTION: main

10-28 14:43:54.879: E/AndroidRuntime(3660): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.deskclock/com.android.deskclock.AlarmClock}: android.database.sqlite.SQLiteException: no such column: incvol (code 1): , while compiling: SELECT _id, hour, minutes, daysofweek, alarmtime, enabled, vibrate, message, alert, incvol, profile FROM alarms ORDER BY hour, minutes ASC

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2185)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2210)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.ActivityThread.access$600(ActivityThread.java:142)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1208)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.os.Handler.dispatchMessage(Handler.java:99)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.os.Looper.loop(Looper.java:137)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.ActivityThread.main(ActivityThread.java:4930)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at java.lang.reflect.Method.invokeNative(Native Method)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at java.lang.reflect.Method.invoke(Method.java:511)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at dalvik.system.NativeStart.main(Native Method)

10-28 14:43:54.879: E/AndroidRuntime(3660): Caused by: android.database.sqlite.SQLiteException: no such column: incvol (code 1): , while compiling: SELECT _id, hour, minutes, daysofweek, alarmtime, enabled, vibrate, message, alert, incvol, profile FROM alarms ORDER BY hour, minutes ASC

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteConnection.nativePrepareStatement(Native Method)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:882)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteConnection.prepare(SQLiteConnection.java:493)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteSession.prepare(SQLiteSession.java:588)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteProgram.<init>(SQLiteProgram.java:58)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteQuery.<init>(SQLiteQuery.java:37)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:44)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1314)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:400)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.database.sqlite.SQLiteQueryBuilder.query(SQLiteQueryBuilder.java:294)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at com.android.deskclock.AlarmProvider.query(AlarmProvider.java:73)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.content.ContentProvider.query(ContentProvider.java:652)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.content.ContentProvider$Transport.query(ContentProvider.java:189)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.content.ContentResolver.query(ContentResolver.java:370)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.content.ContentResolver.query(ContentResolver.java:313)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at com.android.deskclock.Alarms.getAlarmsCursor(Alarms.java:135)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at com.android.deskclock.AlarmClock.onCreate(AlarmClock.java:199)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.Activity.performCreate(Activity.java:5008)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)

10-28 14:43:54.879: E/AndroidRuntime(3660):	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2139)

3. The device performance drop when activated the bubble animated desktop. The drop was very visible, but could be be tolerated i guess. I'm back on static wallpaper.

4. Youtube videos on hq are extremely choppy, tested on the presentation video for rom toolbox (sassibob's) and the image updated every 5-6 seconds while audio was playing at normal rate. Without hq it runs almost smooth, but the image quality is obviously degraded. On CM 7.2 was running fine.

5. Battery seams to drop pretty fast, lost 26% in around 5 hours of the same usage that on CM 7.2 i was losing 15% or under, but since i'm only using the build for less than 24 hours, i can't tell for sure. Will get back with more info hopefully in the next days

6. More a question than an issue, had a lot of problems with internal storage getting lower and lower without actually installing anything. Got it from 50 MB to 3.5 in the first 10 mins from the first time i started the device with the new fw. Had to uninstall stuff in order to keep the apps from not crashing. After a while it stabilised. Do you know why the internal storage goes down like that?

These being said, i'm looking forward for the next version, this one has some issues but does look very nice and promissing.