[Kernel][GPL] Development 3.0 Kernel

[Quarx]

Current 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

Tips:
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.

If you liked this project, you can donate

Donate to Quarx
PayPal: [email protected]
---------------------------------------
Donate to Blechd0se
PayPal: [email protected]

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.0

 

[Blechd0se]

Changelog:

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;

• Added new extra_free_kbytes tuable (4.4 compatibility)
• Added our Interactive Governor from 2.6.32 for additional performance
• Added a basic display control driver
• Added a dynamic writeback control interface
• Enabled cgroups for memory (4.4 compatibility)
• Enabled deadline and changed tunables to the same as on 2.6.32
• Enabled xattr and fs security for ext3/4
• Patched up trim (ext3/4) to the latest mainline version
• Switched to XZ compression for a smaller kernel image
• Reclaimed some RAM from logger and vram
• *Fixed the wakeup delay and the "funny" screen on resume

TODO:

• Add Overclock driver
• Fix kpanic with pvr and dss (solved?)
• Fix sleep problem

How To Build

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

Sys-Values explanation;

Let me explain some of this features a little bit. 3.0.8 offers completely new opportunities to do some magic stuff.
One thing i developed a while back ago is a dynamic writeback driver with a sys-interface. It uses the earlysuspend kernel api
to flush dirty pages more frequent when in suspend, while display is on it avoids it to give a more fluid user interface.
Can be controlled via the following command;

echo 1 > /sys/devices/virtual/misc/writeback/writeback_enabled
(1 for enabled = default, 0 for disabled)

Also new; a basic display driver! As i tried to fix some things in our dss driver i noticed that we have different panel configurations.One is for all defy green and one for defy red lense users. I exposed those values to user space so that they can be changed. The
new default one are those, which are used on the red lense defy. In theory there could be 256 values (0-255), however could only find the
following as useful. This is not the final gamma control i wanted to have, but at least it gives some control. If someone knows the proper
addresses for gamma values, i can add them too

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)

In order to run 4.4 more fluid, google made a guide and also published some recommended patches. One of them let you change
the VM's behavior to have a minimum amount of free memory. Also controllable over a interface;

echo 8192 > /proc/sys/vm/extra_free_kbytes

8192 means 8 MB of free ram (in any case).

 

[Fight4Music]

Thanks for this information

Gesendet von meinem Nexus 4 mit Tapatalk 2

 

[matiasrey]

If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?

 

[imharshadpatel]

a separate thread was really needed for 3.0.8 kernel.
thank u quarx and Blechd0se

 

[TJKV]

If I may ask, @Quarx and @Blechdose: which one of these items are the hardest to solve at the moment?

I am guessing it's the Camera?

 

[guidoido004]

Honestly, i think its time to stop working on the 2.6.32 kernel and focus on 3.0.x, looking as an atrix user, its definetly the best choice devs could do. Hehe

Sent from my LG-E975 using Tapatalk

 

[ebol94]

Once again, thanks!!!

 

[niksy+]

@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?

I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?

 

[mariosanoguera]

@Quarx @Blechd0se About the camera... Quarx, you asked in a post somewhere about our opinions on whether you guys should try to set it up with an open-source driver or with the old Moto driver. Maybe you could tell us what would be the advantages and disadvantages of which one and we could even vote if you want us to?

I'm guessing that we could get more out of the camera with an open-source driver, but it would be harder to set-up than the Moto driver?

its a 5mp camera, so we should go for the old moto drivers, easiest stuff to do right?

 

[frullewulle]

Once it works with open source driver for camera, free forever...

Sent from my Nexus 7 using xda app-developers app

 

[niksy+]

I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^

(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )

Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho

 

[Blechd0se]

I shouted "YES!!" out loud when I saw the commit about headset and microphone fixes! *edit* But the call speaker maybe isn't fixed just yet :/ Still, gotta try the new build when it shows up ^_^

(that's this one - https://github.com/Quarx2k/android_...mmit/8f5a44ca04ba1c005cb1ac2409639b62f6260d4e )

Combined with Blechd0se's stability fixes (especially this one that fixes the "deep sleep death" - https://github.com/Quarx2k/jordan-kernel/commit/f6b6de228a09f46ab7d6eff70f9225f88e7d3515 ) the next build is going to be very usable imho

Yes Quarx is doing a very good job here, still struggling with a last few bugs. Anyway, its progress! Also the huge battery drain should be fixed,
i disabled kmemleak. 3.0 is such a nice base to work with, no need to do hacky things, it just works out of the box.
Next version will have timer_slack controller (its working perfectly). Also many fixes for crashes and memory leaks.

One big thing is still the display. Although wakeup delay is gone for me, dss/pvr crashes sometimes. Its very random.
Also overclocking has two sides; on the one side its much easier to understand, on the other side it doesn't work as expected (can't overclock
to 1200mhz for example). But we have finally a nice voltage/frequency table.

 

[matiasrey]

Glad to read the good news, doesn´t seem too far from a usable kernel!

Have you decided what camera drivers you´ll go for?

 

[niksy+]

F* yeah! "isl29030: fix reboot of proximity sensor" commit signed off by Blechd0se

Quarx has been focusing on the in-call sound issue today, so things are looking brighter by the day


*edit* I'm guessing more and more people use the thanks button as the like button

 

[triovi]

When I wake up in the morning and read Quarx github , appear "Add Micron MT9P012 sensor driver" , so I think we can hope at an camera soon...

 

[mayur2j]

OTG!!

In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?

 

[major9]

In the description it says USB: 98%, "OTG" bugged. Does this mean we can connect pen drives, mouse and keyboards to our defy with this kernel?

Yes, but with external power.

 

[mayur2j]

Yes, but with external power.

So it's of almost no use then..

 

[Quarx]

External power? I can conenct mouse/keyboard or flash drives, no need external power.