[Kernel][GPL] Development 3.0 Kernel

Search This thread
By:
Advanced…
Lord_Flaya

Lord_Flaya

Senior Member
Jun 1, 2012
558
121
40
Tomelilla
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). :)
 
T

TheDelta

Senior Member
Nov 5, 2012
245
55
DEFY XT everything

Hi,

Sorry to hijack the thread, but seems like a good place to ask questions.

I am used to flashing ROM/Kernel on RAZRs and a friend of mine wants to start flashing on her Defy XT 535.
Can anyone point me to any link that will give me a working rooting guide.

Also please confirm how things will be for Defy, to flash a custom ROM/Kernel
For RAZR I usually root>install safestrap(recovery)> flash rom> flash kernel etc
Shouldn't the steps for Defy be similar? I don't know what recovery to use or from where to get the correct recovery as i am confused if everything works the same for defy, defy+ and defy XT.

Thanks in advance!!

P.S. - Kudos on getting the OTG working without external power, hope it comes to our RAZR soon :D
 
S

starbright_

Senior Member
Apr 11, 2010
1,472
262
It is really estonishing what Quarx and other devs are able to do.
Beside from the technical challenge to port a new kernel, what are the expected advantages?
 
H

htto

Senior Member
Feb 12, 2014
99
194
gist.github.com
ebol94 said:
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.-
Click to expand...
Click to collapse

Do you by chance have a ext3/4 /data partition? I had that problem, when the f2fs-detect script was unable to handle it and mounting of /data failed completely. Thus you get in-ram saving of data and loose it every reboot.
 
E

ela1103

Senior Member
Apr 24, 2011
684
289
HEART
We are all thing android l powered 3.10 kernel with our moto defy this year end .
Quarx working for 3.10 kernel with more imporvement
 
O

okij

Senior Member
Oct 24, 2012
2,028
3,934
Düsseldorf
Samsung Galaxy S10e
Is the 3.0 / 3.10 kernel development for the Defy dead or just interrupted?

Looking at Quarx's GitHub, there hasn't been any commit on the 3.0 and 3.10 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.10 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.10 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.10 kernel would really bring new life to our beloved Defy. :)
 
Last edited:
  • Like
Reactions: starbright_, Proverbs2, fairxda and 6 others
Quarx

Quarx

Inactive Recognized Developer
Jun 19, 2007
1,322
18,790
32
Omsk
www.quarx2k.ru
okij said:
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. :)
Click to expand...
Click to collapse
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. :(
 
Last edited:
  • Like
Reactions: Diresh, Saturnal, guanda80 and 71 others
santi1993

santi1993

Senior Member
Mar 24, 2012
789
135
Buenos Aires
Quarx said:
:)
Click to expand...
Click to collapse

Can we help you with something? your work with this device is awesome, you're awesome!
I hope that if u can reach these levels of stability with CM11, CM12 with custom kernel only will take some test time to work, less or more depending of your free time... but with your mind it could be done!

Thanks, thanks, thanks! i'll test whatever you upload to try help you development! hope best regards from south america Quarx! you're teh boss!

PD: do u havy any official merchandising? i will want a shirt that says quarx and the CM11 logo, i'll be proud of it and hope i'll could help you!
 
Last edited:
  • Like
Reactions: thekguy, fanghongjian, Redyro and 5 others
V

vulture BIAN

Member
Apr 13, 2014
27
1
Beijing
Quarx said:
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. :(
Click to expand...
Click to collapse

Thank you very much . . Thank you ., we will support you
 
D

dovw

Senior Member
Jan 26, 2015
70
19
Quarx said:
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. :(
Click to expand...
Click to collapse

My daily driver is probably the last non-LTE 3G CDMA only device - the Moto G (1st Gen) xt1028/xt1031 and it does not yet have any working 5.x ROM with outgoing calls and SMS after months of attempts to get it working. The apparent cause is that it seems that CM12 has introduced a SIM dependency. Are you aware of this from your early work on CM12 on the Defy (which also has a non-LTE CDMA variant)? Is this at least partially what you were referring to in your comments about RIL? Do you have any suggestions?
 
  • Like
Reactions: okij
S

s_u_n

Senior Member
Nov 6, 2012
476
37
Pune
I am visiting the Defy forum after a long time.

The last post from Quarx indicates that he is quite busy. Is there some news after that?

BTW: What is the latest 4.4.4 stable ROM I can download?
 
You must log in or register to reply here.

Similar threads

Quarx
[DEV][ROM] CyanogenMod 7.2.0 (Android 2.3.7)
Replies
18K
Views
6M
vai0
vai0
Quarx
[JB] CM10 Android 4.1.2 for the Defy(+)
Replies
18K
Views
7M
Sankyuuro
Sankyuuro
Epsylon3
[ICS] CM9.1 Android 4.0.4 for the Defy - now with 2ndboot kernels
Replies
8K
Views
3M
mick711
mick711
Quarx
[Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+)
Replies
8K
Views
3M
raphaelgamer981
raphaelgamer981
Quarx
[JB+][3.0.8/2.6.32 kernel] CM10.1 Android 4.2.2 for the Defy(+)
Replies
3K
Views
1M
M
mmbytes

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 226
    Quarx
    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.
    Click to expand...
    Click to collapse
    If you liked this project, you can donate :)
    Donate to Quarx
    PayPal: quarx@yandex.ru
    ---------------------------------------
    Donate to Blechd0se
    PayPal: alex.christ@hotmail.de
    Click to expand...
    Click to collapse

    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
    View
    122
    B
    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

    Code: 
    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)
    Click to expand...
    Click to collapse

    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)
    Click to expand...
    Click to collapse

    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
    Click to expand...
    Click to collapse

    8192 means 8 MB of free ram (in any case).
    View
    74
    Quarx
    Quarx
    okij said:
    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. :)
    Click to expand...
    Click to collapse
    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. :(
    View
    55
    Quarx
    Quarx
    Audio, camera, RIL, SGX - proprietary parts.
    In 3.0 we made opensource audio lib and will use open camera libs.
    View
    53
    B
    Blechd0se
    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 :)
    View

New posts