[LG Optimus Black] Huexxx:
Good morning to all there...

I've testing different aspects of the ROM and I have some fresh bugs and a lot of info.

SD Card Problems

I'm experimenting (from yesterday) new problems with the SD card. I don't know if they are soft or rom related, but anyway I'm going to get them here.

The first sympthom was trying to modify 'governor' with a text editor. App told me that sdcard would be full or write protected...q

Trying different things, i've problems too with dropbox (downloading new files... 'It's impossible to see the galery without sd card or with USB conection) and with the photo galery (External memory full. Remove the non useful files from the sd card in order to get the app properly running). Also, the camera fails to get photos and videos (the shuther didn't make anything... no focus, no sound, etc)

Although, with root explorer I was able to create a folder, etc... maybe all the problem is a permission related one. Your 'nova' script can write to SD too.

Then, I decided to get the result of a 'mount' command:

rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/mmcblk0p5 /lgdrm ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=1,data=ordered 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p8 /system ext4 ro,relatime,barrier=0,nobh,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p9 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /dvp/hwkey ext3 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /dvp/userdata ext3 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:17 /mnt/sdcard vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs rw,relatime 0 0

The best thing is that I've encountered a way to get rid of this problems. Going to 'Settings' -> 'Storage' -> 'Deactivate SD card' and then 'Activate SD card' in order to remount the SD card. Then tried another 'mount' with different results:

rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/mmcblk0p5 /lgdrm ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=1,data=ordered 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p8 /system ext4 ro,relatime,barrier=0,nobh,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p9 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /dvp/hwkey ext3 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /dvp/userdata ext3 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:17 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

Now all the info relative to sd card mount has changed. All runs well after remount. I have to remount the sd everytime I reboot.

Autoboot governor selection problems

I've detected a problem using 'governor' file in order to choose governor automatically on boot. I've tried one by one all the options editing the file with the same result: using 'nova' it indicates that the currently used governor is 'ondemand'. Although, using 'nova' to change the governor, 'nova' properly shows the currently used governor.

'nova' script issues

- When the script prompts if the user want to set the change on autoboot... if you type 'y' or 'n', the script tells the same.. 'changes set on autoboot'.

- When the script modifies 'iosched' for the first time, porperly sets the i/o scheduler but deletes also all the commented text... then, if you try to manually edit the file, you can't see the available options.

- If you use the script to get the current values (of governor, i.e.)... you have to change the value or set the same value. I think that after to see the value, it would return to main menu.

OCing issues

After doing some research, I've understood why not to UV so much... it's useless. Let me explain myself.

I was trying to lower the voltaje value, but looking at /proc/overclocking/mpu_opps I've seen that all the changes only affect to the maximum frequency state while the others remain unchanged. Then, trying with max voltaje = 48, looking at 'mpu_opps' I see that while it uses voltaje 48 at 1GHz, also uses voltaje 56 at 800 MHz, voltaje 45 at 600 MHz and voltaje 32 at 300MHz; a complete nonsense.

Do all the governors use all the data at 'mpu_opps'? If the answer is yes, I think that to modify the max voltaje would have to modify the rest of the voltaje values in order to get coherence and save battery in a effective way. How to modify it? This is more difficult... and there are a lot of pssibilities... modify all the values in the same ammount, modify only the top value mantaining the lower and getting the intermediate values in a lineal way... a mix of the two last...

In the actual circumstances, put a voltaje below 56 is a nonsense.

In a similar way, when you want to get some OC/UC, maybe the rest of the frequency values should change too.

Video recording

It's true that the recorded videos shows an estrange ratio aspect... too wide and it deforms the image.

Another imprevement for OB could be to get .mp4 instead .3gp

CWM

In addition to the absence of progress bar when backuping... i've seen a lot of error messages when I run it.

E: Can't mount /cache/recovery/command

E: Can't mount /cache/recovery/log

E: Can't mount /cache/recovery/lastlog

E: Can't open /cache/recovery/log

E: Can't open /cache/recovery/lastlog

I hope all this comments will help you to get rid of our beast!!!

Regards!