external power? I can conenct mouse/keyboard or flash drives, no need external power.
its good news master quarx you are great developer for our moto defy
external power? I can conenct mouse/keyboard or flash drives, no need external power.
External power? I can conenct mouse/keyboard or flash drives, no need external power.
audio, camera, ril, sgx - proprietary parts.
In 3.0 we made opensource audio lib and will use open camera libs.
Audio, camera, RIL, SGX - proprietary parts.
In 3.0 we made opensource audio lib and will use open camera libs.
According to AndroSensor app, the magnetic sensor (and therefore also the compass) isn't working yet, but all other sensors are working.Sensors - 98%, Need test all sensors, looks like all sensors works
I experienced that quite often after switching the Defy on, just the softkey LEDs are lit, but the screen stays black. Turning it off and on again for a few times helps.
so now that you have opensource audio lib, is it possible to get low latency audio, and dsp tunneling on the defy? the last one would be killer
Does this mean that camera now works?I'll just post a kernel changelog of the current CM11 Build;
- Added timer slack controller
- Added dynamic fsync
- Added proportional rate reduction for TCP
- Added opensource camera driver (mt9p012)
- Added syspanic driver for panic_daemon
- Added sync framework (together with ION its part of androids graphical "project butter")
- Switched to SLUB allocator
- Enabled ram console Support
- Synced binder to mainline version (~3.10)
- Fixed reboot while incoming or outcoming call (fix proximity sensor in general)
- Many small performance patches and fixes for better android support all over the place
RAM console is a pretty big change, it allows much better debugging. So whenever you encounter any random reboot,
boot into android and run cat /proc/last_kmsg. This will give you a dmesg-output which contains your crash
Quarx2k pushed to cm11.0-3.0 at Quarx2k/android_device_moto_jordan-common
79c5d28 Initial support incall sound (works, but with whistle)
"But with whistle"
@abhi.eternal The camera doesn't work, they would definitely say that if it did I tested the build, it's not working But the driver is there, which is still a good thing and I guess what has to be done now is for various configs to be set-up correctly
Quarx2k pushed to cm11.0-3.0 at Quarx2k/android_device_moto_jordan-common
f246a3c Add support (incall) headset, earpice, speaker
Which parts of this kernel are open source and which parts are propetary ? (motorola)
Audio, camera, RIL, SGX - proprietary parts.
In 3.0 we made opensource audio lib and will use open camera libs.
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.