Search This thread

vrl13

Senior Member
Apr 29, 2012
413
294
Bucuresti
Interesting. I always thought (read it somewhere) that the kernel should be flashed after the ROM. What is the disadvantage of doing it this way?

Hello,

From what i've read so far it seems that the kermel is, first of all, a collection of drivers. It initializes the hardware and provides its functionality to the OS, or the ROM in our case. That means if you want your os to be aware of the available drivers you need to install them in this order. Otherwise the results may be unpredictable... i think:D

Anyone feel free to correct me if i'm wrong.

Hail to the Q!

Sent from my MB526 using xda premium
 
  • Like
Reactions: Viva_SA

hackergnome

Senior Member
Apr 21, 2011
2,613
875
Bengaluru
6yT6X8f3

http://db.tt/6yT6X8f3
IMAGE DOESN'T WoRK :(

Benchmarks are useless!

Sent from my MB526 using xda premium
 
Last edited:

sami2704

Senior Member
Oct 18, 2011
59
41
Mumbai
Hi, i've tried all cm10 roms and with all due respect to quarx because everything seems to be working properly, there is one issue, i wouldn't like to call it a bug, that has been reported, probably slipped unnoticed. When the phone rings, i drag the circle to the right to answer the call and though it seems to have stopped ringing it goes for one more ring. Just to make my ear explode.. this is very annoying when i'm in a hurry to answer :D

If this would be fixed I would be very gratefull.
Thanks for your efforts.

Vic.

Ps: the ringtone is custom (ringtone from crank :D) maybe this helps in some way

+1 I am also facing same issue... Hence i wait for 2 seconds before saying hello to caller ;)
 
Dec 29, 2007
41
4
just installed v04 09
wonderful job just 2 issues now for me.
1) when i plug wall charger i lost 3g data. network icon stay at grey.
2) i am using apex launcher. each appli i launch causes apex FC.

I know it's experimental build. so i'm waiting for the new one.
i hope this post will help.

Sent from my MB526 using xda premium
 

corrinti

Senior Member
Jun 15, 2009
786
233
Lublin
Interesting. I always thought (read it somewhere) that the kernel should be flashed after the ROM. What is the disadvantage of doing it this way?

Hello,

From what i've read so far it seems that the kermel is, first of all, a collection of drivers. It initializes the hardware and provides its functionality to the OS, or the ROM in our case. That means if you want your os to be aware of the available drivers you need to install them in this order. Otherwise the results may be unpredictable... i think:D

Anyone feel free to correct me if i'm wrong.

Hail to the Q!

Sent from my MB526 using xda premium

Or :cowboy: newer nightly can have some newer parts included, which overwrite kernel's contents. Please correct me if I'm wrong
 
Bro, I was speaking of defy+ which was released 08/2011 :) I have red lense defy and always use defy+ builds. But like I said before, I'm sure they will release a new boot loader to boot the new kernel

Sent from my MB526 using xda app-developers app

It's not necessary... they just have to release jb with kernel signed with the same key to work on our bootloader. They don't have (and will never do) to unlock bootloader

Enviado desde mi MB525 usando Tapatalk 2
 

bone101

Senior Member
Jan 6, 2012
692
137
I've got problems with Wi-Fi data connection ... the Wi-Fi symbol in status bar stays grey , connection is established but no data are transferrerd....

After an reboot every thing works

Problems since i use mobile data

Sent from my MB526 using xda app-developers app
 
Last edited:

sami2704

Senior Member
Oct 18, 2011
59
41
Mumbai
Or :cowboy: newer nightly can have some newer parts included, which overwrite kernel's contents. Please correct me if I'm wrong

I dont think new nightlies or any other ROMs do any changes in Kernel. They just use drivers in kernel to talk with hardware thats all.

I had installed CM9 kernel & Gapps only while flashing CM10 that too because i had done full wipe. For any other subsequent nightly i only install nightly. No kernel, no Gapps. It work just fine.

Just do wipe cache and dalvik cache before and after install from SD card... :good:
 

ppero196

Senior Member
Apr 14, 2012
3,184
1,213
Up north!
I dont think new nightlies or any other ROMs do any changes in Kernel. They just use drivers in kernel to talk with hardware thats all.

I had installed CM9 kernel & Gapps only while flashing CM10 that too because i had done full wipe. For any other subsequent nightly i only install nightly. No kernel, no Gapps. It work just fine.

Just do wipe cache and dalvik cache before and after install from SD card... :good:
Well ROM CAN & it DOES include new stuff into kernel....
New drivers and so on...all done via kernel patching
 
  • Like
Reactions: corrinti

FcukBloat

Senior Member
Jun 18, 2012
6,284
3,012
last build is so nice.. except for video recording still lagging..

also, previously purchased can not be installed via play store.. as I was afraid.. :( they download properly but then installation fails with unknown error -24 :(
what could it be? i tried two apps i did puchase (tapatalk.. really need it! and quarx donate app).. both fails during install.. instead other free apps from my account can be installed without problems.. please help forum via browser is so slow.. :(
 
Last edited:

Persechini

Senior Member
Mar 12, 2012
439
151
Rio de Janeiro
I'm loving this build so far, very smooth - I know I complained about perception of smoothness after a clean install, but this time if it's not real I really fell victim to this illusion =P (mb525 build installed over previous mb526 build only clearing cache/dalvik). Proximity sensor is responding swiftly =)

There are still a few cons that were occurring for me for some time:

- Compass calibrates ok since the fix, but it still points north with an approximate 15 degrees error (it will point either correct north or a bit off either clockwise or counterclockwise every time I take it up and place it down again)

- GPS doesn't fix unless I'm in wide open space (and I mean WIDE, not even a big window is enough). For what I read over the forums other ICS/JB ROMs have this issue too, specially outside the US (I'm in south america). GPS fixing apps take as much time to lock as google maps (and can't lock in the same situations it can't), and this is with data and/or wifi enabled, I gave up trying to use GPS without data enabled even in the open. Last time I could get certain GPS lock every attempt, even indoors, was with GB or earlier ROMS (namely MIUI GB and stock froyo)

-Brightness sensor seems to get stuck every once in a while (won't light up when moving from shadow to direct sunlight, etc) but this might be due to me changing from defy+ to defy build without a complete wipe (but I did flash the correct kernel)

Plus, I never seem to have this question answered, but here I go again:

What difference does it make flashing the kernel before of after the ROM? does the ROM contain anything the the kernel zip replaces or vice-versa? Are there any technical aspect preventing the ROM to come with the respective kernels built in?

And lastly (please don't hate me) does the leftovers from the SBF flashed before a custom ROM take any part in this? I mean, I've read people saying that CEE or Nordic SBFs were a better starting point for flashing custom ROMs over
 

vaibhav palande

Senior Member
Jan 27, 2012
293
111
Pune
-GPS doesn't fix unless I'm in wide open space (and I mean WIDE, not even a big window is enough). For what I read over the forums other ICS/JB ROMs have this issue too, specially outside the US (I'm in south america). GPS fixing apps take as much time to lock as google maps (and can't lock in the same situations it can't), and this is with data and/or wifi enabled, I gave up trying to use GPS without data enabled even in the open. Last time I could get certain GPS lock every attempt, even indoors, was with GB or earlier ROMS (namely MIUI GB and stock froyo)

-Brightness sensor seems to get stuck every once in a while (won't light up when moving from shadow to direct sunlight, etc)

I agree with GPS and Brightness sensor issue... I did full wipe before installing latest nightly..
About brightness sensor: When i go from direct sunlight to shadow or vice-versa screen brightness doesn't change.. i have to lock phone and when i unlock it, i get the proper brightness... Any1 with the same issue?
 

lief.erl

Senior Member
Mar 29, 2012
67
4
for whoever is using apex/Nova launcher but experiencing lags try holo launcher HD (free version available). it is actually made for jb unlike other launchers, which haven't been updated for months.

Sent from my MB526
 
  • Like
Reactions: vaibhav palande

vaibhav palande

Senior Member
Jan 27, 2012
293
111
Pune
for whoever is using apex/Nova launcher but experiencing lags try holo launcher HD (free version available). it is actually made for jb unlike other launchers, which haven't been updated for months.

Sent from my MB526

Yes, HOLO Launcher HD works great and it is specially made for JB, so all the new JB animations are there..
 

FcukBloat

Senior Member
Jun 18, 2012
6,284
3,012
me too.. brightness sensor seems to work.only after locking display.

which apps are.you using for compass? i'm using compass from catch.com and seems to me pretty precise!
 
Feb 9, 2012
47
41
La Rioja
Gapless playback

What about gapless playback? I far as I know, official JB supports it. Correct if I'm wrong.

Thank you very much Quarx for your awesome work. You're a surprisingly skilled dev! Please keep your abilities with our rock-solid defy! :D
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1710
    Android 4.1.2 Jellybean for Defy and Defy+

    Download Link: http://quarx2k.ru
    Epsylon3 Builds: http://defy.wdscript.fr/
    Mirrors: http://defy.bytekiste.de/
    http://d-h.st/users/Quarx
    Gapps: http://goo.im/gapps/
    Minimal gaaps(Gmail,Market,Gtalk,Synchronisation) http://quarx2k.ru/gapps-jb-20120726-minimal.zip
    Gapps + Working Google Now - http://xdaforums.com/showthread.php?p=30988910

    Status:
    12.07: Boot up :)
    14.07: Phone, Mobile Data, USB, Mass storage, Sensors, Camera(Photo), GPS/AGPS.
    18.07: Audio (thanks to maniac103), Video rec/play, Panorama, FM-Radio.
    19.07: Install app to sdcard, mp3 codec, video codec fixes, rework fm-radio, cyan update.
    22.07: Usb fixes, USB Tethering, Data Usage, Preferred Network (umts/cdma) selection, CrystalTalk
    23.07: Fix audio lock-ups (thanks to nadlabak), a2dp, fix volume change, OS FMRadio and fm volume change in background by maniac103, leds
    26.07: Themes, button backlight, fix lag bootanimation, imei/mac... cyanogen updates.
    28.07: re-fix button backlight, holo fm-radio, Option for enable/disable On-Screen Button(36dp)
    04.08: Fix volume rocker music controls, Realtime switch of OnScreenButtons and size of it, Phone/SMS apps now in memory all the time, Enable CPU TLS Register, Auto-Backlight Settings, Boosted governor by default... maybe forgot some more..
    08.08: Improved stablity of camera (bayer have problem with sound), DroidSSHD, Trebuchet, common stablity fixes.
    10.08: update Moto RIL to v4, fm-radio to lockscreen, hwui blacklist on mb525, fix realtime OnScreenButtons, Fix MotoPortal, Disable get local ipv6 adress.
    12.08: Auto-backup battd, Port phone features from cm9, Add national data roaming and make it optional (from AOKP).
    22.08: Fix ability change brightness of buttons(Defyparts), compass fix, Apollo intent fix (which fixes last.fm etc), dalvik heap 128mb -> 48mb, wifi changes
    25.08: Disable lock in memory Phone and sms apps(by users requests), fix OnScreenButtons, ipv6 tweaks.
    28.08: Fix 00:00:00:00:00:00 SSID in apps, fix audio routing in dock modes
    03.09: Fix Audio in video rec(not ideal) and decrease fps in preview camera (not in video), 2Channels for audio, DSP-Manager in software which support JB (ex, apollo) it's not a bug, support multiboot, wifi-tethering (thanks ot devs of ml2, maybe have bugs, not tested)
    04.09: Fix compass, update sgx libs to JB, fix wallpapers, improve video perfomance, new touch driver (for test, only 2 fingers for now, more will be enabled in next build).
    12.09: Fixed touch driver (allow touches upto 10), Fix for data connection, thanks to SlugZero, also some more fixes for stability ril, disable fps limit in preview.
    24.09: Video rec fixes, add 720p rec (not by default, unstable),cyanogen updates.
    2ndboot builds: one build for mb525&526
    10.10 Android 4.1.2, CRT-Animation , custom kernel, experimental. Included patch for flashlght(not tested, but shouldn't burn it)
    11.10 Fix red camera, updated 2ndboot.ko, fix pds mount and permissions.
    18.10 Kernel update:fix wifi tether(reboot), reduce battery drain, fix charge only mode, cleanup unused drivers, fix button lights, fix slow boot and lags after boot.
    02.11 Add power hal, interactive governor+bootpulse(should be default in bootemnu for correct work power hal),kernel fixes from upstream, cleanup/disable unused drivers, fix SGX clocks, add bp_ptc service(only service), fix battery drain, add fuse rw-ntfs/extfat fs support(not tested, but should work), fix backlight settings, fix small problem with fm-radio on notfication drawer, add cm file manager(can work incorrect), restore live wallpapers, cm sync....

    17.11 Update kernel to 2.6.32-60, backport some optimisation from 4.2, fix mount options for ext4, cyanogen update, restore conversion to RGB->YV12 for video.
    18.11 Apply many optimisations: Android compiled with latest Linaro toolchain GCC-4.7, kernel compiled with Linaro toolchain GCC-4.5.4. Little wifi fixes.
    28.11 Disable linaro for android, fix adhoch, new battd, fix bt.
    04.12 Partial linaro, Fix upnp/dlna(thanks to nadlabak), fix reboot in bootmenu/recovery, cyan fixes.
    05.12 Fix root, fix adb, fix ROOT/ADB settings from dev menu , cyan fixes.
    22.12 Stability fixes, cyan updates.
    23.12 Fix shutdown, built-in call rec function(thanks to nadlabak).
    29.12 Revert to .9 kernel (for audio tests and stability), fix root permissions on CMFileManager, adb can be disabled now, bootmenu now has only one custom recovery option.
    30.12 Restore .60 kernel, some fixes in android which can cause ringing problems.
    07.01 Again fix root permissions on CMFileManager, fix battery when ADB disabledl, again some fixes which can cause ringing problems.
    17.02 rgnd service, increase performance of camera.
    07.03 Fix for deskclock (from YetAnotherForumUser). Based on clean 2.6.32 moto tree, should fix many random problems... or add more :p
    24.03 Completely new wifi/wifi-ap driver, switch to wpa_supplicant8, Wifi ap AP - 72mbps :)
    25.03 Some fixes in wifi, fixed MAC, WiFi direct implemented
    26.03 Improved stability of wifi.
    09.04 Suspend optimization.
    11.05 Updated USB-Gadget to native for 4.x, fix mtp/ptp/storage/tethering. Removed usb.apk/usbd.
    16.05 Very experimental build, contain a lot of updates from kernels 2.6.33 - 3.1. Increased performance, added swap. Memory management updated to 2.6.39(3.0) state. Some parts updated to 3.1. Blechd0se patches for interactive gov.
    22/23+ experimental.
    16.06 Updated wifi driver & wpa_supplicant, improvement in interactive governor by @Blechd0se. Updated kernel with some patches from upstream.
    09.07 Stability fixes. Updated bootmenu. This build not contain ZCache/Zram/Swap
    30.10 Fixed Video playback, latest kernel changes(same as 10.2), gpu 266mhz...

    TIPS: LG Camera app works better with video rec.
    Do not enable "Allow purging of assets" - it makes many lags.

    Some users ask about new donate app, https://play.google.com/store/apps/details?id=com.donatecm_10 :)

    F.A.Q
    Just funny video:)

    device-2012-07-13-002749.jpgdevice-2012-07-13-002457.jpgdevice-2012-07-13-002509.jpg
    128
    I appreciate some of the comments here about the difficulty of keeping threads like this cleaned and organized, especially with so many users not following instructions. However, this is the job I signed up for, so it's not a big deal. :)

    That being said, since nothing else seems to be working, I'm going to temporarily close this to force people to use the other support threads for this ROM. If you have a legitimate bug to report and serious question that needs answering, use the support threads (an absolute last resort would be PMing the developer). This will be reopened at the appropriate time.

    [Support] - [JB] CM10 Android 4.1.1 for the Defy(+)
    [FAQ] [JB] CM10 for Defy/Defy+ (by Quarx) (Added DPI Mod Guide)
    [SUPPORT] Quarx's CM10 PROBLEMS reporting thread

    closed_cleaning.png
    105
    Build will not removed.
    Demo build is uploaded for everyone.;)

    Android 4.2 has new libc/linker, which breaks compatibility with old moto binaries. Need some time to fix it:)
    And i think, better discuss 4.2 in different thread.
    73
    Sound now works:)
    All thanks for help to maniac103:)
    68
    Thanks guys for found workaround, it can be caused by adb.
    Please try this ramdisk and check battery http://quarx2k.ru/ramdisk
    Replace in /system/bootmenu/2nd-boot