yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Blechd0se:
Thanks, always appreciate it when somebody likes my work :)

Does this battery problem persists? No need to delete anything, because its working for you. I haven't wifi touched much and don't want to

rewrite the hole thing since Quarx does by far a better job at this place :)

Anyway pushed out a new build today again (need more sleep :silly: ). I finished my work on the dynamic writeback daemon and i am

pretty satisfied with it, you can enable and disable it if you want:

echo 1 > /sys/class/misc/wirteback/writeback_enabled

(1 = enabled (default), 0 = disabled)

It was also merged to our "mainline" .9 Kernel by Quarx (woho!) and as i saw some positive feedback about the performance i will continue

to push some commits into it.

Can't really something about compatibility (i am still on 26/03, because i have no time to update, but 04/04 should work). Also i switched to

SLUB, should also improve performance.
[Defy Android Development] Lolu:
On Quarx 09.04 i have constant rebooting into bootloader. I try flash your kernel with factory reset/wipes, without wipes and always the same thing.
[Defy Android Development] frullewulle:
I've installed this kernel update with just cleaning cache and dalvik cache, no factory reset....

it is safer to install the previous blechdose kernel before this one, to be sure that you have the right modules installed too
[Defy Android Development] flunk03:
Same here , cm 10 09.04 ROM + 10.04 kernel results in bootloop after wiping caches both custom and stock. Will try to obtain logs if possible.

IF it helps Defy green lens here .
[Defy Android Development] atulclassic:
worked like charm

installed 10.4 on 20130409 quarx build..worked like charm..no bootloops..nothins..only battery is a bit heated..currently at 39C
[Defy Android Development] HammDefy:
Same with my Defy. Made FullWipe & Dalvik Wipe, installed latest Rom & Gapps, fixed permissions, reboot -> Boots and everything ok.

Reboot into Custom Recovery, Wiped Cache & Dalvik, installed JellyX 09.04.(cfs) , fixed permissons, reboot ->Bootloop

Reboot into recovery, Wiped Cache & Dalvik, Installed JellyX 10.04 (cfs), fixed permissions, reboot -> Bootloop

Defy won't boot with JellyX on CM10 from 09.04.....
[Defy Android Development] Blechd0se:
Can someone with 09.04 rom test my kernel only with zImage and see if it boots up (delete all in zip except kernel), of course logs are better..?

Nearly all changes of 04.04 -> 10.04 are inside kernel, so no big deal using 04.04 or even 26.03 as a base :)
[Defy Android Development] demoliner:
Hello,

DEFY MB525 green, cm 10 09.04 ROM CM10.1 (4.2.2) + gapps ok

wipe cache davilk + kernel 10.04 ok

No problem for the moment......
[Defy Android Development] Krokogator:
Motorola Defy Green Lense

10.04 JellyX + 09.04 CM10 =

bootloop into bootmenu

Trying to install kernel with only zImage. Will report soon
[Defy Android Development] Krokogator:
After deleting everything in system folder except for kernel and update with wipe data/cache problem is still there.
[Defy Android Development] Blechd0se:
Did you deleted the modules too? it should really only update zImage in /system/bootmenu/2nd-boot/

So assume there is something new in CM10 (10/04) whats not merged in CM10.1(10.4), however 04/04 should still work :)
[Defy Android Development] Krokogator:
Yup there is only system\bootmenu\2nd-boot\zImage

And meta-inf of course

View attachment kernel_10.04-cfs-modules.zip
[Defy Android Development] pl4yeR:
It's the same for me. Reboot into bootmenu again and again. 09/04 CM10, defy red lens.

Could I ask a question? Are you guys having wifi tethering fully working with this kernel?
[Defy Android Development] Krokogator:
Nope, wifi tethering is still missing.

Edit:

Sry, wifi tethering is working, my fault :cowboy:
[Defy Android Development] pl4yeR:
:confused: people say that with latest build (ie new Wi-Fi driver) they have working tethering.. or maybe I'm misunderstanding?

My question was, assuming new quarx build, and flashing this kernel, could we have tethering working?

Sent from my Defy. Jelly Bean 4.1.2.
[Defy Android Development] Krokogator:
ooops sory my fault. Wifi tethering is working, just tested on latest quarx build.
[Defy Android Development] diamond_lover:
You should only go in the Boot Menu and set Interactive as governor, there's something messed up in overclock.conf.
[Defy Android Development] pl4yeR:
Do you mean that Jelly kernel works for those which have reboots into recovery if they set governor to interactive?

woah! let's try!
[Defy Android Development] atulclassic:
No way..i have smartass selected in bootmenu and smartass in settings
[Defy Android Development] HammDefy:
I tried interactive - Bootloop!
[Defy Android Development] Krokogator:
Changing governor and increasing voltage doesn't work. I have also already cleaned all files and left only zImage in kernel but it didn't work either. Blechdose has to update zImage to make it work with latest build. That's all...:cowboy:
[Defy Android Development] pl4yeR:
Nop. Still boot to recovery..

Sent from my Defy. Jelly Bean 4.1.2.
[Defy Android Development] ASHOKVARATHAN:
bootloops

i installed this jelly x kernel (10 april) on quarx build 9 april but i get bootloops ...any help
[Defy Android Development] atulclassic:
restore backup..reboot full..reboot recovery..change CPU governer to smartass..wipe cache only..flash zip.

i did same process with no bootloops..
[Defy Android Development] Krokogator:
With CM10.1 also bootloop. (GREEN DEFY)

Even tried Fullwiper.zip ... stil doesn't work.

On both quarx without and with custom kernel I get 1 bootloop on CM Logo. The difference is that on custom kernel maybe something changes in settings so it boots into bootmenu instead of booting system again?

Waiting for new (fixed) release :)
[Defy Android Development] Blechd0se:
With latest CM10.1? As is said, 26.03 works. Nope it doesn't change anything here, it probably detects a bootloop. I am working on a fixed version and got it even booting but then suddenly wifi doesn't work anymore and i have no clue why.

For those who want to test; install 22.03 kernel with ramdisk first, then 10.04.
[Defy Android Development] Krokogator:
Yup latest cm10.1 with latest JellyX

Edit:

Just tested 10.04 over 22.03 JellyX and booted without any problems but I got phone app crash and couldn't do anything with my phone. Needs more testing but may be solution for this problem.

I will test it more on both latest CM's and see what happens.

Edit2:

Made 3xwipe installed again cm10.1 and both kernels and now blackscreen....

Edit3:

Taking off battery helped but again phone and messaging app crashed with QKernel. Tommorow will test it on 4.1.2 cm10 and see if it works.
[Defy Android Development] rsk_kelkar:
i was running quarx 4.2.2 9-apr build with your 10.04. But now since BT is fixed on quarx will it still work after flashing your kernel too?? is BT included in your kernel?

EDIT: I decided to try the kernel out on new build. Forget BT. The ROM wont even boot. Always takes me to bootmenu. Never had problems with your kernels for previous CM10.1 builds
[Defy Android Development] Krokogator:
On Cm10 (4.1.2) installing 10.04 over 22.03 also worked, phone booted without any problems but wifi is not working (phone reboots and enters bootloop when switched on)

Tapatapped from my Google powered Defy
[Defy Android Development] vrl13:
Greetings!

I have installed 9.Apr cm10.1 after full wipe from both stock and custom recovery, booted phone -no problem.

Back to custom recovery, wiped both cache locations and installed 10 Apr jelly kernel. Booted phone - impeccable work!

Removed bloatware, installed minimal gapps. Upped the CPU freq to 1200 (interactive) and increased vsels for tier 3 and 4 with 2 and 4, activated the dynamic write back daemon, installed the new PLAY Store version and had NO ISSUE so far - the phone was up for 2 days with no glitch, WiFi ok, mobile data ok. phone ok.

Maybe these steps will help someone:)

Thank you for your work!
[Defy Android Development] kryzeK:
It's worth installing JellyX in CM10.1?
[Defy Android Development] hotdog125:
Wi-Fi not working

I flashed the 10.04 JellyX over sevenrock's 9.02 build. Everythings snappy and better as usual:D, but the Wi-Fi is not working at all:eek:.

I tried deleting the data/misc/wifi folder and rebooting , but to no avail.

I then tried 9.04 and 3.04 JellyX but they have the same problem. Any idea how to fix this?
[Defy Android Development] Blechd0se:
Becuase 09/02 has not the latest wifi drivers :) 09/04 by Quarx? If you turn on wifi, does it reboot?

Latest confirmed rom & kernel are 26/03 and 10/04.

I am trying to fix it at the moment https://github.com/Blechd0se/android_hardware_ti_wlan

But the hard part is; i can't get logs, it simply won't show anything if i turn on wifi, so hard to debug....

But i am still digging :)
[Defy Android Development] Divino:
- factory reset

- wipe cache

- wipe dalvik

- install quark 26/03

- install kernel 10/04

- wipe cache

- wipe dalvik

...red led then black screen... ;_(

- remove battery

- bootmenu

- set cpu to interactive

- format sd-ext to ext4

- reboot

...logo...

ta-daaaaa

- wi-fi on

...WORKS!!!

- zram in memory settings

...WORKS!!!

YEAH, now installing gapps, hope all works... ;)
[Defy Android Development] Krokogator:
Try reboot and tell if you get black screen

Tapatapped from my Google powered Defy
[Defy Android Development] flunk03:
@ blechd0se I think the bootloop issues are common to green lens users . Will try to get you some logs hopefully .
[Defy Android Development] Blechd0se:
No, i have a defy+ :) And no need for logs, but you can provide them of course if you want to:) Since the last ramdisk update,

it won't work, however this is easy to fix. The actual problem are those last wifi changes, if there were some.

Looks like its the fault of the kernel and not of modules, but dmesg and kmsg doesn't show anything when wifi is turned on,

but logcat shows something:

W/CommandListener(16899): Failed to retrieve HW addr for wlan0 (No such device)
E/WifiHW (17029): unexpected - found -1 phys in /sys/class/ieee80211
F/libc (17029): @@@ ABORTING: INVALID HEAP ADDRESS IN dlfree addr=0x2a25a8f0
F/libc (17029): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1708
5 (WifiStateMachin)
[Defy Android Development] atulclassic:
not working with Quarx 15.04

Today i tried to flash 10.4 with Quarx 15.04 build

Although it flashed successfully and booted perfectly but when i tried to find the CPU governers i found out that it didn't flashed at all..

Unable to understand why this happened..could somebody explain this.
[Defy Android Development] Spidinator:
Same here. I was able to flash jelly X on previous build with cwm but not with new recovery on latest build.
[Defy Android Development] Divino:
No black screen after setting cpu profile and format sd-ext.

All ok except fm radio, I don't know if it's related to rom o kernel...

...others can use fm radio?
[Defy Android Development] kins299:
Awesome temple run oz on my wiui v4 jb,powered by jelly x defy....
[Defy Android Development] Feche:
Me too.

EDIT:

Got a PM from PaleHorseman (he can't post yet)

So, that is the basic reason of why it doesn't flash, thanks to him :)
[Defy Android Development] Kayant:
Have a look at this it got help to getting a bootable 4.7 linaro optimized kernel?

I will try it myself later on ;)

https://github.com/garwedgess?tab=repositories

https://github.com/garwedgess?tab=repositories

Edit - also your recent merge into the mail line kernel broke the compilation of the wifi modules

Let's Go ^_^
[Defy Android Development] Blechd0se:
Will have a look at it late, thanks :) Although i guess zImage wont be decompressed and thats the fault why it wont boot...

Which one breaks it? autogrouping? Does it work if you not set it in deconfig?
[Defy Android Development] Kayant:
Am guessing autogrouping because I did a git reset back to HEAD( keyboard, defconfig cleanup) and it was compiling fine......

This was the error I was getting -

wireless/wl12xx/sdio.c:330:3: error: implicit declaration of function 'sdio_set_host_pm_flags' [-Werror=implicit-function-declaration]
[Defy Android Development] Blechd0se:
You mean the hole rom? Because kernel compiles fine for me, but rom didnt because another error (something with /boot, but not because of kernel)... Strange because my kernel got the same commit and compiles fine with modules, didyou make mrproper or make clean?

And my commit doesnt delete anything related to wifi :D

Also check if sdio_set_host_pm_flags is defined in drivers/mmc/core/sdio_io.c, line 708 and include/linux/mmc/sdio_func.h, line 169, because its definied in our main line kernel
[Defy Android Development] Kayant:
Will do later on.... Off to school for now ;)

Probably some flags somewhere that is messing it up I guess....
[Defy Android Development] hotdog125:
reply

Yup, you're right.. reboots randomly when I switch on Wi-Fi on 09/04..... Strangely it does work sometimes, but reboots randomly:eek:.
[Defy Android Development] Antiga Prime:
Given that I'm not interested in new WiFi drivers because of the signal jamming bug, is there any way to flash this over older ROMS, such as the 03/18 Quarx build, without replacing the WiFi driver/modules?
[Defy Android Development] Kayant:
No because the driver change is directing in the kernel so you would have to replace the new code with the old one then recompile before it will work and not forgetting you will have to revert some changes in framework, etc....

Let's Go ^_^
[Defy Android Development] rsk_kelkar:
Upgrade

[MENTION=4855459]Blechd0se[/MENTION] Can we have a kernel with the latest quarx commits for it to work on 15.04 build of quarx 10.1??
[Defy Android Development] Mavasilisk:
Its written in the OP that its compatible with 26.03 but its .9 kernel. I cant get it boot with it. Did I miss something or its typo?
[Defy Android Development] niksy+:
Yeah, but you need 04/03 JellyX for that build of CM10. (the modules are different in each of the JellyX builds that contains them, because of the updates Quarx has made)

Why not just use the latest, 09/04 CM10 + 10/04 JellyX? :confused:
[Defy Android Development] Feche:
Doesn't work, since CM10 uses different kernel version
[Defy Android Development] Mavasilisk:
I installed 10.04 kernel on 26.03 Quarx build with data format to EXT4
[Defy Android Development] Blechd0se:
Information

Just to clarify some things a little bit; 26.03(ROM) + 10.04(Kernel) should run totally fine, i was on this combi quite some time.

Everything that was released after 26.03 may have some changes in Wifi, therefore wifi wont work on 09.04(Rom) + 10.04(Kernel)

and you need to flash my ramdisk first to make it boot.

Why dont you just recompile modules again and make a new build?

Because i can't. Well i can, but there is something broken with Wifi (4.1 and 4.2)

and i dont know if its Kernel or Modules related. To be more precise; 26.03 was stable for me, can't complain about it,

but still looking forward to make JellyX work with every new Quarx Rom.

Also as you might have seen, i joined kernel development for Quarx Kernel. I do commits regulary, everytime Quarx released

a new build i will push them (so if there are bugs, you won't notice it, because untill the next release those are sorted out).

This is "my" release cycle, but i won't forget JellyX and talking about JellyX i also have to say something about DarkJellyX (3.0 Kernel);

You haven't seen any updates from me the past two weeks, because i wanted to help Quarx with Modem

in 3.0, its rather hard than simple, but Quarx managed it to get Modem detected. Only Problem left is,

that ehci-omap loose its usb speed from 480mb/s and goes to 12 mb/s. Because of that, the connection to netmux gets

lost.

If somebody has an idea why the kernel sets it back to 12mb/s that would be nice (you can go through the commits on github;

for Quarx: p-android-omap3-3.0 branch, for me: darkjellyx branch).
[Defy Android Development] flunk03:
@ blechd0se MB525 green lens defy here. Installed 26.03 rom with your ramdisk and 10.04 kernel . Phone boots up fine the first time unfortunately I rebooted it and changed the vsel values which resulted in a blackscreen . So any further attempts to get the phone to boot up resulted in blackscreen . Resinstalling rom+ramdisk+kernel produced the same results . So if possible please have a look into it . Am still unable to get any logs up for the 09.04 rom +10.04 kernel combination which results in a bootloop to recovery . Thank you .
[Defy Android Development] Feche:
Like I said before, 09.04 uses a different kernel verison (2.6.32.90), JellyX is is 2.6.32.60.. you won't be able to boot it.
[Defy Android Development] Pason:
can tell me how to flash your ramdisk and where I can dowload it?Thx.:)

MB525-Red Lens-Chinese 2.3.6 Rom
[Defy Android Development] ldiomedi:
I been using some time ago (Im now on 4.2.2, kayant's rootbox, and I wont go back :fingers-crossed:) the 17/02 rom with 22/03 JellyX kernel. That combination was for me the best experrience on JB, but I had to keep the default values for everything. If I changed vsel, governor, the phone reboot and gets bootloop. To fix this, I enter in bootmenu/cpu settings and select the Interactive governor (for some reason every time I did those steps that field was blanck), save the settings and reboot just fine. That was my experience with bootloops. May be this can help you.
[Defy Android Development] Blechd0se:
You can find it on my server, just search for the zip with "ramdisk" in its name :)

At least you should be able to boot it (with or without ramdisk). Thats the purpose of this modules.

Some news for JellyX; i tried lots of things to make wifi work, but it simply wont work. I compiled those modules nearly a thousend times,

but as soon as i turn wifi on it goes into bootloop. My next intension was to go back to the last point where it worked (before this suspend/resume

thing in wifi), however even this doesn't work. So there must me some change in CM or a change by Quarx in the latest ROMs that keep

preventing my kernel to work with it.

So to keep it short,i havent got any motivation anymore for this (because it looks like i can't fix it at the moment) and i dont want to waste my time with fixing

stupid bugs instead i want to create new things (just like this dynamic page wirteback), but i can't as long as this stuff happens.

I was on 09/04 for some days, but got crazy because of the sometimes very low overall performance. So what should i do? Start new with .9 branch (i dont like this idea, because this patches have a purpose!) ?

Try to find the cause? Make only stable releases? Revert the new Wifi driver? Terrorize Quarx with my phone? ;)

I think "our" 4.2 is much more usefull to use as a base (in every aspect), so let 4.1 deprecate? I am very open to hear your oppinion for this :)

For 3.0 Kernel; i managed to backport (or forwardport?) ehci-omap from .32. It still doesn't boot, probably because of many functions that

haven't been renamed yet, but if somebody has an idea regarding modem in general, shoot it out :)
[Defy Android Development] niksy+:
Well, since you're asking... :D

I always felt that JellyX was about going further and going beyond, so I vote against the stable-builds-only option :cowboy:

As for what to do, I wouldn't mind going back to the old WiFi driver if that would end the status-quo, so my vote goes for that :) (compiling the WiFi modules along with the kernel would be enough to make the kernel compatible with the ROM builds that use the new driver as standard, right? :confused: ) And it's always possible that one moment you'll simply have a brainwave and just figure out how to fix up the problems with the new driver and in this case you wouldn't have to be annoyed about previously switching to the .9 branch and starting over :)

And good work so far and good luck further on with the 3.0 kernel, hope you and Quarx get it patched up successfully! :) (that was all I could do to help :/ )
[Defy Android Development] ccav2000:
My vote would be to move forward. I always believed in that principal deep down, that's why I am using the latest 4.2.2 even with BT not working currently. If our device is to have any future, that lies on the 3.x kernel. Android 4.3 is on the horizon, expected to be announced in the upcoming Google I/O, and it may bring more driver changes. We need a new, modern kernel, for a new modern OS. Let 4.1 die...
[Defy Android Development] Feche:
Sorry for the ignorance.. but what is a ramdisk? and yeah, keep moving.. 4.2 is my vote :)
[Defy Android Development] thekguy:
Ramdisk is basically a bunch of core files required for booting

While trying to port sense, I had to edit the ramdisk, so I know something about it:D, but port is still not booting:(

Keep moving on..
[Defy Android Development] abhifx:
+1

4.2.2 is definitely better (smother, better multitasking etc) and thus full concentration should be on 4.2.2 (specially since 4.3 is about to be announced, we should at least get a stable 4.2.2)
[Defy Android Development] gamerxxxn:
I vote for moving forward..Android 4.2

Thanks for all your hard work into making this wonderful kernel !
[Defy Android Development] flunk03:
[MENTION=4855459]Blechd0se[/MENTION] I vote for moving forward . Just made the jump to 10.1 and I already feel its better than cm 10 inspite of the bugs . All the best and thank you for everything so far.
[Defy Android Development] matiasrey:
I think exactly the same, I believe the 3.X kernel is the best option to go with! :highfive: If you devs stay in 4.1 Defy development will die and i´ll have to change mi phone. :cyclops:
[Defy Android Development] coolzarjun:
Yes.. I too vote for moving forward to 4.2... 4.2 is better in every aspect :D
[Defy Android Development] pjgowtham:
May be people say 4.2 brought headaches to nexus users. 4.1 is better they say...
[Defy Android Development] adiif1:
Fix black screen on green lens?
[Defy Android Development] rizeN50:
Changelog for 28.04 3.0 kernel?
[Defy Android Development] Pason:
Can it work on walter's M2SGinger and Epsylon3's CM9.1 ?（all is 2ndboot rom） :) thx

MB525-Red Lens-Chinese 2.3.6 Rom
[Defy Android Development] bonedriven:
What is BFS and what is CFS plz.
[Defy Android Development] Blechd0se:
Q&A

Still on my "ToDo"-list, but first the wlan issue thing with 4.2.

Current state of darkjellyx branch, nothing special here, i uploaded it because of a user request.

No it wont work, mainly because of sgx driver and some other things.

Read the first post plz....

Looks like i made a decision, so no more 4.1 updates, only 4.2 :)

Edit:

Does somebody has two defys? I want to test a new feature, but need two, if yes feel free to pm me :)
[Defy Android Development] Bleak3993:
BFS = Brain F**k Scheduler http://en.wikipedia.org/wiki/Brain_****_Scheduler

CFS = Completely Fair Scheduler http://en.wikipedia.org/wiki/Completely_Fair_Scheduler
[Defy Android Development] unixr0cket:
im update hungry

No new updates since 10.04 8c!!!? and the kernel doesn´t work on cm10.1 c8
[Defy Android Development] vedhasd:
Sry if reposting the question

What should i try to fix black screen issue on green lense defy? Like trying to play with any values?
[Defy Android Development] pranks1989:
I got two Defys... However one is in service center and I intend to collect it this weekend. If not already done, I can help you out. :)
[Defy Android Development] Blechd0se:
Thanks, but i already tested it and moved on, i tried to bring some sort of gamma control interface to the kernel (had nearly the same interface written like on the nexus 4), but had no luck...

There are currently no updates for jellyx because i work now with Quarx on the Aero Kernel :)

So i dont have to worry about module compatibility.
[Defy Android Development] pranks1989:
That sounds great!!! :) I revently installed Quarx's latest build of CM10 and am amazed by the performance! It has the Aero Kernel I saw.. :)
[Defy Android Development] walter79:
Will not work. GPU driver was updated.
[Defy Android Development] Pason:
Thx.:)
[Defy Android Development] Delgado666:
how can I activate zRam? it doesn't appear in "performance" menu

i've installed cfs 10.04