I nowadays switched to another phone, and thus have no mandatory use for my defy. Would happily do pin-point testing and/or other specific trials to aid in development in the best way i can (perhaps with some basic guidance).
Tried cm-11-20140919-EXPERIMENTAL-kernel3.0-mb526 but everytime I reboot it asks me to configure everything again! Like if I were booting up for the first time.-
Tried cm-11-20140919-EXPERIMENTAL-kernel3.0-mb526 but everytime I reboot it asks me to configure everything again! Like if I were booting up for the first time.-
3.10 Currently have problems with CPCAP, which cant be solved yet.Looking at Quarx's GitHub, there hasn't been any commit on the 3.0 and 3.1 kernel for about a month now. I'm wondering if Quarx has dropped this project because of his recent development for the ASUS PadFone S.
This would be really sad because the 3.0 kernel project for the Defy has made a great success and almost all parts are working by now. Also the possibilities of the 3.1 kernel, thanks to the sources we got from the Moto 360, haven't been used yet.
Therefore I would like to ask @Quarx: Is the 3.0 / 3.1 kernel development for the Defy dead or is it just interrupted because of your recent work for the PadFone S? If you plan to continue the development, when would this be the case?
Please don't get me wrong: I'm sure that every Defy user who ever used a CyanogenMod build on his Defy is grateful for every single line of code that you ever wrote for this great little phone! But if we want to keep it alife, I'm sure that only a working 3.0 / 3.1 kernel would really bring new life to our beloved Defy.
3.10 Currently have problems with CPCAP, which cant be solved yet.
Also i got a work. This just eat whole my time... and only free 3-5h per day.
Work with Asus PadFone S almost ended, already everything fixed in cm12. I bought its because of LTE and can't use 4.4, that's why i start make 5.0
Current version of 3.0 not have Telephony Problem, but need more tests. But it have problem with battery and red camera.
First CM12 for Defy will be with 3.0, but need fix RIL part. In 5.0, bionic very changed and many closed Defy binaries stop working.
I know all want fast CM12, but time really not enough.
First CM12 for Defy will be with 3.0, but need fix RIL part. In 5.0, bionic very changed and many closed Defy binaries stop working.
I know all want fast CM12, but time really not enough.
If you liked this project, you can donateTips:
Do not format System and Cache to F2FS!!!
1. To use f2fsl "/system/bin/mkfs.f2fs /dev/block/mmcblk1p25" or format via TWRP (Advanced wipe menu).
2. To restore ext4, in recovery unmount data, mount system, and do via adb shell /system/bin/make_ext4fs /dev/block/mmcblk1p25 or format via TWRP (Advanced wipe menu).
3. If you have 0 bytes free bug, reformat data to f2fs or ext3/4.
4. 1.1 Ghz can be enabled in performance settings.
Donate to Quarx
PayPal: quarx@yandex.ru
---------------------------------------
Donate to Blechd0se
PayPal: alex.christ@hotmail.de
git clone https://github.com/Quarx2k/jordan-kernel.git
cd jordan-kernel
git checkout --orphan p-android-omap3-3.0
git pull https://github.com/Quarx2k/jordan-kernel.git p-android-omap3-3.0
export CROSS_COMPILE=/path/to/your/toolchains/arm-eabi-4.6/bin/arm-eabi-
export ARCH=arm
make mapphone_defconfig
make -j12
echo 1 > /sys/devices/virtual/misc/writeback/writeback_enabled
(1 for enabled = default, 0 for disabled)
echo xx > /sys/class/misc/display_control/display_brightness_value
(0 will set the screen to almost 0,
9 will set the screen to some kind of blue-washed colors,
31 will set the screen to more warmer colors = default)
3.10 Currently have problems with CPCAP, which cant be solved yet.Looking at Quarx's GitHub, there hasn't been any commit on the 3.0 and 3.1 kernel for about a month now. I'm wondering if Quarx has dropped this project because of his recent development for the ASUS PadFone S.
This would be really sad because the 3.0 kernel project for the Defy has made a great success and almost all parts are working by now. Also the possibilities of the 3.1 kernel, thanks to the sources we got from the Moto 360, haven't been used yet.
Therefore I would like to ask @Quarx: Is the 3.0 / 3.1 kernel development for the Defy dead or is it just interrupted because of your recent work for the PadFone S? If you plan to continue the development, when would this be the case?
Please don't get me wrong: I'm sure that every Defy user who ever used a CyanogenMod build on his Defy is grateful for every single line of code that you ever wrote for this great little phone! But if we want to keep it alife, I'm sure that only a working 3.0 / 3.1 kernel would really bring new life to our beloved Defy.