Yes you can look on atached files BUT never in the future use the cmupdater to update the rom,just dnld the rom zip and MD5 waping ONLY dalvik and casche and reboot, you never have such a problem(happen to me in the past),i wrote this many times.
Hi,frient the 27/3 build you asked is now uploaded by me here: https://docs.google.com/file/d/0BxgubD3FybzeQjhnVC1PX0hmbWc/edit?pli=1
PpsaaiiiilsMwnulllolalolloqqqsaajibsaq wlOjoio(wouupwwd;qzz
we have the same bl(09.10),i think you dind understand what i said and what i send.No mind,so you have to flash first the defy_twrp_recovery_2.6.3.0(included on files send to see) i dont now if possible by 2.7.1.0 but i suppose so,also follow excactly whatn is written on #1 and then proceed on next steps that you know now?If you have problem start from sbf following the way.txt(also send) using the sbf which refered on this txt.You must be calm first and your mind clear as you seems confused yet.Sorry for suggestions
15/10/14 and then(last 10 days) i use
I agree with you granazis. I bought a Defy to add it to my smartphone collection and it would be neat to brag about having Lollipop on a 4-5 year old device.
Quarx I'm grateful for your KitKat port which runs nicely on my phone. I'd love to see Lollipop running in my device eventually.
SlugZero found some documentation for .bts file format of the TIInit file here which may help with further improvements. Here I collected some information that might be useful for fixing bug #2b. Bug #2d is fixed since at least 07-24 nightly. Bug #2e has been solved by courtesy of Quarx. Bug #2f has been fixed. Bug #2g has been fixed. Bug #2h has been solved by courtesy of Quarx. Volume is somewhat lower than under CM10 or under stock ROM, but - as frozenwaverider wrote here - this is the same on other devices running on CM11 and not Defy specific. Here you can find a list of BT headsets that were reported to work well. If it occurs, usually a reboot or a hot boot (e.g. with a Rebooter app) helps to get the IMEI back quickly. Sometimes this bug still happens even with the workaround, though very rarely. If you want to have a look at the status bar (e.g. for checking the signal strenght), you can still swipe it down, as Pecan-fan explained here. Additionally, to have the device wake up quickly, it can help to disable suspend for Interactive governor and change hispeed_freq to 1200000 (or whatever maximum frequency you use) in Aero Control. Also please keep in mind that running heavy apps can lead to a longer wakeup time due to memory management. As frozenwaverider wrote here, disabling all call lookup in Phone app also helps to reduce call delay. If you still encounter problems with incremental updates (which might occur if your system files have been changed), download the full build here and install it manually via TWRP over your working CM11 installation as a workaround. As Quarx wrote here, users reported about problems with zRam, so this option is not available since Android 4.4. Please note that overclocking and undervolting can lead to random reboots and that CM11 is more sensitive for this than e.g. CM7 (using the same OC/UV settings), as several users have reported. Also overclocking the CPU to 266 MHz can lead to random reboots or telephony layer problems, so Quarx set back GPU to default 200 MHz since 06-09 nightly. If it's stable for you, you can still overlock GPU to 266 MHz via Aero Control. However, I still recommend Online Nandroid Backup, which can make TWRP compatible backups with the advantage that you can make the backups while your Defy is running, so you don't have to reboot to TWRP. Remember to make the swipe (sort of) straight downward, because if it's too diagonal (e.g. when using your thumb), the status bar doesn't get pulled down. For red lens Defys (including Defy+), this fix was in conflict with their 720p video recording capabilities, but newer versions (> 4.7.0) of Barcode Scanner were reported to work again. Please note that sometimes the update server can't be reached (which isn't a bug on the software side). As hendrikmerkel wrote here, this bug might be provider / network dependent, although this problem doesn't exist under CM7. Here and here hendrikmerkel and Avesi gave summaries of what they tried to get MMS to work. As Quarx wrote here, he did some changes for MMS, so maybe this bug got better. As jsoi wrote here, now sending and receiving MMS is at least working with Wifi for him, but not with mobile network yet. As I, ooo and hendrikmerkel wrote here, here and here, MMS still isn't working in 09-08 nightly. x53 wrote here about his test results for this bug. hendrikmerkel wrote here, here, here and here some new infos concerning this bug. Additionally, using RAM Booster helps to keep the system responsive, as masbitxo reported here. 
root@mb526:/ # mount
rootfs / rootfs ro,noatime,nodiratime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,noatime,nodiratime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,noatime,nodiratime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,noatime,nodiratime,cpu 0 0
tmpfs /storage tmpfs rw,noatime,nodiratime,mode=050,gid=1028 0 0
/dev/block/mmcblk1p1 /bootstrap ext3 ro,noatime,nodiratime,errors=continue,barrier=1,data=writeback 0 0
/dev/block/mmcblk1p5 /system ext4 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mmcblk1p6 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mmcblk1p7 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk1p8 /pds ext3 rw,noatime,nodiratime,barrier=1,data=writeback 0 0
ramfs /tmp ramfs rw,noatime,nodiratime,relatime 0 0
/dev/block/vold/179:1 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
root@mb526:/ # df
Filesystem Size Used Free Blksize
/dev 239.5M 140.0K 239.4M 4096
/mnt/asec 239.5M 0.0K 239.5M 4096
/mnt/obb 239.5M 0.0K 239.5M 4096
/mnt/fuse 239.5M 0.0K 239.5M 4096
/storage 239.5M 0.0K 239.5M 4096
/bootstrap 49.2M 18.6M 30.6M 4096
/system 617.1M 286.3M 330.8M 4096
/cache 47.2M 4.3M 43.0M 4096
/data 1.0G 640.1M 433.8M 4096
/pds 3.9M 1.1M 2.8M 1024
/mnt/media_rw/sdcard0 1.8G 1.6G 205.1M 4096
/mnt/secure/asec 1.8G 1.6G 205.1M 4096
/storage/sdcard0 1.8G 1.6G 205.1M 4096
root@mb526:/ #Thanks for problem list@Quarx: Thanks a lot for todays nightly, which is running very stable and smooth so far! :victory:
For your next nightly, could you probably look after bugs #3 and #5? Both should be easily fixable, because in my bug list I already pointed to the necessary patches, and some of us are really missing the torch tile - after all, this would bring a light to all of us in the wait for Christmas!
WIll be in next nightly.
