[Kernel][GPL] Development 3.0 Kernel
- Thread starter Quarx
- Start date
Quarx & Blechd0se :victory::victory:
i have a few question ...
1-) whats "parts" of DEFY have propietary code ?
2-) This kernel and Aero has all drivers made from scratch
?
Thanks :good:
i have a few question ...
1-) whats "parts" of DEFY have propietary code ?
2-) This kernel and Aero has all drivers made from scratch
? Thanks :good:
Audio, camera, RIL, SGX - proprietary parts.
In 3.0 we made opensource audio lib and will use open camera libs.
In 3.0 we made opensource audio lib and will use open camera libs.
just thumbs up thanks or buy Quarx and other devs a Paypal-beer, no need to write him into megalomania....:beer:
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
I'll just post a kernel changelog of the current CM11 Build;
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
- 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
Some feedback on the 11-17th nightly
For testing, I installed cm-11-20131110-NIGHTLY-mb526.zip (after stripping it down to about 168 MB in size by deleting some unneeded files with 7-zip) ontop of my working installation of CM10.2.
Also, for those who are interested, switching from Dalvik to ART via Development Options went without problems (for this I was using a self-stripped-down version of pa_gapps-modular-mini-4.4-20131114-signed.zip which is just 17 MBytes in size), although updating the apps took some time and quite a few apps (e.g. TitaniumBackup) aren't compatible to ART yet.
All in all, even without ART, CM11 with kernel 3.0 has a very fluid user experience! :good:
I'm really hoping that in-call-sound and camera get fixed soon, so that we can start to use CM11 / Android 4.4 on a daily basis. :fingers-crossed:
For now I have to restore a TWRP backup of my CM10.2 installation, because I need my phone (for making calls) tomorrow.
Thanks @Quarx and @Blechd0se for this great development and keep up the good work! :victory:
For testing, I installed cm-11-20131110-NIGHTLY-mb526.zip (after stripping it down to about 168 MB in size by deleting some unneeded files with 7-zip) ontop of my working installation of CM10.2.
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.
Also, for those who are interested, switching from Dalvik to ART via Development Options went without problems (for this I was using a self-stripped-down version of pa_gapps-modular-mini-4.4-20131114-signed.zip which is just 17 MBytes in size), although updating the apps took some time and quite a few apps (e.g. TitaniumBackup) aren't compatible to ART yet.
All in all, even without ART, CM11 with kernel 3.0 has a very fluid user experience! :good:
I'm really hoping that in-call-sound and camera get fixed soon, so that we can start to use CM11 / Android 4.4 on a daily basis. :fingers-crossed:
For now I have to restore a TWRP backup of my CM10.2 installation, because I need my phone (for making calls) tomorrow.
Thanks @Quarx and @Blechd0se for this great development and keep up the good work! :victory:
Last edited:
Audio tunneling needs some requirements in hardware it seems, i wouldn't expect this feature on Defy
Bugeport 17.11 build
No call sound here
I Flashed straight on last CM10.2 w.o. factory reset....
In first time the rom was a bit buggy , but then it went really fast
Google account and all apps seems to work pretty good
No Display problems (only short time of usage not everything is testet)
Could not install xda app , maybe becaus of the app2sdcard bug
Wifi & Mobile Data seems to connect but no server could be found...
After factory reset Wifi,Data & Sound Bugs still present
Dmesg : https://www.dropbox.com/s/e3nxtll96639fqv/defy525red.txt
MB525 red lens
No call sound here
I Flashed straight on last CM10.2 w.o. factory reset....
In first time the rom was a bit buggy , but then it went really fast
Google account and all apps seems to work pretty good
No Display problems (only short time of usage not everything is testet)
Could not install xda app , maybe becaus of the app2sdcard bug
Wifi & Mobile Data seems to connect but no server could be found...
After factory reset Wifi,Data & Sound Bugs still present
Dmesg : https://www.dropbox.com/s/e3nxtll96639fqv/defy525red.txt
MB525 red lens
Last edited:
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
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
Last edited:
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
Aaaaand its fixed.
Thanks Quarks!
open or propetary
Which parts of this kernel are open source and which parts are propetary ? (motorola)
Which parts of this kernel are open source and which parts are propetary ? (motorola)
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
226Current state of 3.0 Kernel
WiFi/Thether/p2p - 100%
TouchScreen - 100%
Video Codec/hw 720p/ION stuff - 100%
Display/DSS - 100%
Phone/3G data - 100%
Sound/FM-Radio - 100%
F2FS support - 100%
GPU OC 266mhz - 100%
Bluetooth - 95%
USB - 98%, otg bugged.
Sensors - 98%, Need test all sensors, looks like all sensors works
Camera - 85%, Preview/Photo(Red have random problem)/Panorama works for both lenses. Video rec not work yet.
Overclock CPU- 0%, not implemented.
For CM10,10.1,10.2 < 07.11.13 users:
To install KitKat, need update recovery. Do not forget reboot, after install recovery.
http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
If you liked this project, you can donate
Download: http://quarx2k.ru/index2.php?dir=buildbot/roms/defy-cm11.0-3.0
Sources of kernel availabe here(branch p-android-omap3-3.0): https://github.com/Quarx2k/jordan-kernel/tree/p-android-omap3-3.0122Changelog:
17.11:
- 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
Logs or it didn't happen! If you want to report a problem, be sure to post a log file!
Here is a small guide when we need which log file and how to get it.
Old Changelog;
TODO:
- Add Overclock driver
- Fix kpanic with pvr and dss (solved?)
- Fix sleep problem
How To Build
Sys-Values explanation;
74
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.
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.53I'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
