yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Quarx:
Strange, there no special requirements, just flash zip....

Dark preview fixed https://github.com/Quarx2k/jordan-kernel/commit/905aa3ce2c19a30b376d412f0b6747bd349c324c

Hope this fix random display freezes https://github.com/Quarx2k/jordan-kernel/commit/631643f428097068c5050c815720d1ca6c05e653

About save photos with red lense

D/CameraHal(121): Received jpg 0x4dc47000 size 0

Size 0 is a problem...

D/TIOMX_CORE(121): Found component OMX.TI.JPEG.Encoder with refCount 0 pHandle (0x425dbf78)
D/OMX_JPGENC(121): OMX_ComponentInit():458 in jpeg-enc OMX_ComponentInit
D/OMX_JPGENC(121): OMX_ComponentInit():492 Inside Component Init JPEG encoder
D/OMX_JPGENC(121): OMX_ComponentInit():591 591 :: Malloced = 0x4255e400
D/OMX_JPGENC(121): SetJpegEncInParams():2610 2610 :: Malloced = 0x4255e500
D/OMX_JPGENC(121): JPEGEnc_Start_ComponentThread():352 Inside JPEGEnc_Start_ComponentThread function
D/OMX_JPGENC(121): OMX_ComponentInit():763 JPEG-ENC: actual buffer 4
D/OMX_JPGENC(121): JPEGENC_GetParameter():1073 Entering function
D/OMX_JPGENC(121): JPEGENC_GetParameter():1220 Exit function eError = 80001005
D/TIOMX_CORE(121): deinit count = 1
D/OMX_JPGENC(121): OMX_JpegEnc_Thread():128 fd max is 56
D/OMX_JPGENC(121): OMX_JpegEnc_Thread():182 CMD pipe is set in Component Thread
D/OMX_JPGENC(121): OMX_JpegEnc_Thread():193 eCmd 2147483646, nParam1 0
D/OMX_JPGENC(121): OMX_JpegEnc_Thread():257 Component Thread Exit while loop from EXIT label
D/OMX_JPGENC(121): JPEGEnc_Free_ComponentResources():545 Exiting JPEG FreeComponentresources
D/TIOMX_CORE(121): Found matching pHandle(0x425dbf78) at component 1 with refCount 1, handle index 0
D/CameraHal(121): Received raw yuv 0x43a32000 size 7547904
D/CameraHal(121): CAM_PERF: Time to raw 3734 ms
D/CameraHal(121): Received jpg 0x4dc47000 size 0
D/CameraHal(121): CAM_PERF: Time to jpg 3738 ms
[Defy Android Development] htto:
Yeah, I don't get it as well, I'd bet at bootstrap failing, though no idea why. Let's see if I can get uart to work

Looks like the jpeg encoder chokes and thus doesn't give a bit..

Edit:

Humm...

614 adb push ramdisk /system/bootstrap/2nd-boot

615 adb push zImage /system/bootstrap/2nd-boot

629 adb push system/lib/modules /system/lib/modules

Ok, doing the above on the 2.6build keeps boostrap working and kinda boots the kernel. I'm glad it has early adb support, cause the video driver ain't working yet (but that was to expect)

Edit2:

Adb pushing the libs even gets graphics, and the bootanimation and 'android is updating'...

If I had to guess I'd say that

-console=/dev/null mem=500M init=/init omapfb.vram=0:4M usbcore.old_scheme_first=y panic=30 mmcparts=mmcblk1:p20(kpanic)

+console=/dev/null mem=500M omapfb.vram=0:4M

the cmdline difference is the problem.

Because it's probably not

$BB_STATIC echo "inserting hbootmod.ko"

+if [ -e /cache/uart_en ]; then

+$BB_STATIC insmod ./hbootmod.ko kill_dss=1 emu_uart=115200

+else

$BB_STATIC insmod ./hbootmod.ko kill_dss=1

+fi

and the differing zImage, and ramdisks is to be expected.

w00t... it finished it's hackery boot.

"shell@mb526:/ $ uname -a

Linux localhost 3.0.8-g2149493 #1 PREEMPT Tue May 13 10:29:27 OMST 2014 armv7l GNU/Linux"

Though I doubt it would survive copying your cmdline :/

Edit3:

Uhh, now I wonder why you are able to boot

if (execute_command) {
run_init_process(execute_command);
printk(KERN_WARNING "Failed to execute %s. Attempting "
"defaults...\n", execute_command);
}

run_init_process("/sbin/init");
run_init_process("/etc/init");
run_init_process("/bin/init");
run_init_process("/bin/sh");

panic("No init found. Try passing init= option to kernel. "
"See Linux Documentation/init.txt for guidance.");

So, there's no /init in that list, thus I'd say no boot without init=/init. And just in case: is there a way to modify the system partition while not being able to get into running system/recovery?
[Defy Android Development] Stoku:
Cool, I'm waiting for an upcoming build, so I could test it :)

Btw. Are there any other HW differences between red and green lense Defy? Camera, display and... is there something else on what we should focus and is related to the "color" of Defy?
[Defy Android Development] niksy+:
[MENTION=513620]Quarx[/MENTION] Too late now, since you've fixed it already, but here they are side by side anyway :D

Also, the latest version of TWRP won't mount my sd card at all, automatic or manual :rolleyes: Anyone else with the same problem? The card works fine once Android has booted up and it's fine in a card reader :silly:
[Defy Android Development] Proverbs2:
Yes, I had the same problem a while ago, and fixed it by doing this.

Edit: by the way, don't do anything in TWRP until the card is fixed, or you may end up hard-bricking your phone like I did. :p
[Defy Android Development] mayur2j:
What's the advantage of 3.0.8 kernel over 2.6.32 kernel. Is our defy capable of handling it? If not its useless to work on a kernel which again will have some bugs which will slow down the device & will defeat the purpose of making it fast.
[Defy Android Development] DiegoxG:
If it was useless then they wouldn't spend nor waste time on it, be patient
[Defy Android Development] atulclassic:
read this and don't spam the board with unnecessary queries

http://en.wikipedia.org/wiki/Linux_kernel
[Defy Android Development] Stoku:
A new build (15-05) appeared here! I'm making backup now and going to test it especially for display freezes :)

Downloads:

15-05 rom

15-05 checksum

Changelog (compared to 11-05):

Test fixes for DSS freeze

Fix photo on red lense camera force closes after taking a photo, so probably will be fixed in the next build

Fix dark preview red lense

and more minor changes :)
[Defy Android Development] douglasanpa:
I wipe all my defy and installed with the gapps found on the site and now quarx2k not access the play store, is a bug of this rom or GAPPS? the internet works perfectly
[Defy Android Development] Stoku:
I had problems with connecting to my google account (when was adding it via settings>add account), but the play store work's fine for me.

The gapps I use: http://quarx2k.ru/GappsForDefy-CM11.0.zip

Confirmed on 15-05 and easy to reproduce (happens every wake up). Is it a feature or bug? I would like to see it as a screen off animation :p
[Defy Android Development] douglasanpa:
I have used this gapps also
[Defy Android Development] Stoku:
Have you added a google account before in Settings>add account>google?
[Defy Android Development] Fight4Music:
Feature :D

The kernel 3.0 buildbot nightlys are booting, cool :cool:
[Defy Android Development] DroidBot:
Voice Quality???

What about voice calls?? Is smurf voice issue solved? Can I try this build with lots of voice calls, because I don't have backup phone.

Btw Thanks for your feedback.
[Defy Android Development] niksy+:
But the screen on my DEFY+ wakes up without any graphical glitches? :rolleyes: :silly:
[Defy Android Development] Stoku:
[MENTION=4602875]Fight4Music[/MENTION]: yep, it boots fine :)

Just made a call and smurf voice is still there. Quarx will probably add some info here when he solve that issue.

Now I'm going back to my daily rom. I could use this one as a daily, but this smurf voice...

Conclusion? The 15-05 experimental works smooth and pretty stable. The only freezes I got were probably caused by apps (stock file manager frozen when I did something what I don't remember lol). I'm a bad tester cause of my poor memory...or I should note everything :p

Known bugs for 15-05 experimental:

[red-lense] camera force closes after taking a photo

short display artifacts after screen wake up (posted here and confirmed here, but it doesn't appear on Defy+ as niksy+ says here)

incall smurf voice and everything what is unfinished here

when screen turns off and the phone locks, it *clicks* ~3 times when USB mass storage app is maximized; happens on other KitKat roms too, minor bug

slow USB write speed, avg 1mb/s, can someone confirm?

/edit: added another issue(?), slow usb write speed. On 15-05 got average 1mb/s when I was getting around 2mb/s and more on other roms. Can anyone else test it and confirm? Maybe it was a temporary slow-down.

Writing ~140MB file on my SanDisk SD (class 10 iirc):

CM11 3.0.8 Kernel.

SlimKat 4.0.​
[Defy Android Development] douglasanpa:
began to run itself, I think something was out on google
[Defy Android Development] Fight4Music:
I've got the artifact after a restart (after our bootsplash, its showing very short) with my defy+ and todays rom. Tested twice. And i've got this artifact sometimes (not everytime) after power on the screen. To reproduce this, just play around with your power button :D
[Defy Android Development] htto:
Mhh just a quick heads-up

a) Looks like I really need that init=/init cmdline parameter.

b) current libstagefright crashes mediaserver in that new Sniffer code

c) using an older stagefright for b) helps but then libutils.so crashes mediaserver

d) had several lockups of the screen on bootup (it seems the kernel still ran, since the led colors worked)

e) userinit seems broken

f) am I the only MB525 non-plus defy user and thus got those problems?

Parts are probably due to crashing mediaserver and therefore failing service media.service..

/data/system/dropbox # ls SYSTEM_TOMBSTONE* | wc -l
236

I'll throw some debugging+logs together tomorrow...
[Defy Android Development] Stoku:
Umm...yes :P On my MB525 I had the similar problem once, when it looped at bootstrap, but the next full wipe/sbf/root and flash helped. Maybe it's your bl version? Mine is 9.10.
[Defy Android Development] Quarx:
I have both variants of defy, works on both.
[Defy Android Development] Quarx:
I have "In-band Error seen by MPU at address 0" too, no idea which driver cause this error.

Try latest builds from buildbot.
[Defy Android Development] htto:
Edit2-n

a) Looks like I really need that init=/init cmdline parameter.

b) current libstagefright crashes mediaserver in that new Sniffer code

c) using an older stagefright for b) helps but then libutils.so crashes mediaserver

d) had several lockups of the screen on bootup (it seems the kernel still ran, since the led colors worked)

e) userinit seems broken

f) am I the only MB525 non-plus defy user and thus got those problems?[/QUOTE]

Editn+1:

Bootup hang of the screen

<3>[ 15.957672] BUG: scheduling while atomic: kworker/u:3/62/0x00010003
<4>[ 15.957702] Modules linked in: wl12xx mac80211 cfg80211 modem_pm_driver netmux_linkdriver netmux cifs nls_utf8 compat
<4>[ 15.957763]
<4>[ 15.957763] Pid: 62, comm: kworker/u:3
<4>[ 15.957794] CPU: 0 Tainted: G W (3.0.8-g743ec50-dirty #1)
<4>[ 15.957794] PC is at omap_hwmod_enable+0x38/0x64
<4>[ 15.957824] LR is at _enable_sysc+0x174/0x184
<4>[ 15.957855] pc : [<c0055d40>] lr : [<c0054d80>] psr: 400f0013
<4>[ 15.957855] sp : dd70bde0 ip : c00543d0 fp : 3b9aca00
<4>[ 15.957855] r10: dd70be08 r9 : dd70be00 r8 : dd70be10
<4>[ 15.957885] r7 : 00000001 r6 : 0000001c r5 : 00000000 r4 : a00f0013
<4>[ 15.957885] r3 : 00002015 r2 : c07a7d00 r1 : c07a7d00 r0 : 00000000
<4>[ 15.957916] Flags: nZcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
<4>[ 15.957916] Control: 10c5387d Table: 9dad4019 DAC: 00000015
<4>[ 15.957946]
[..]
<6>[ 21.064483] PVR_K: User requested SGX debug info
<6>[ 26.142486] PVR_K: User requested SGX debug info
<6>[ 31.220733] PVR_K: User requested SGX debug info
[Defy Android Development] Stoku:
Just updated my list of bugs with some screenshots and additional information about minor bug #3.

[MENTION=513620]Quarx[/MENTION] is f2fs finished and were there any fixes for red lense camera since 15-05? I'm going to test some build on the weekend, but It must be worth it ;)
[Defy Android Development] hotdog125:
None of the 3.0 builds boot up for me, screen goes blank with all lights brightly lit after the M logo.
[Defy Android Development] Fight4Music:
For me todays build stucks at bootstrap, like all other kernel 3.0 buildbot nightlys except yesterdays. Can't enter twrp, so it's time to flash sbf again :P
[Defy Android Development] DroidBot:
Same thing happened with today, when I used 17-05 build. Now flashing sbf :P
[Defy Android Development] Quarx:
Yes, something wrong with buildbot... cmdline file is missing.

If add this file in zip, will be no problems:)

But next builds will be boot even without cmdline file:)
[Defy Android Development] Fight4Music:
Could you please tell us where the file is located in rom.zip? :) Then we could copy it into new builds by ourselves.
[Defy Android Development] Quarx:
In system/bootstrap/2nd-boot/
[Defy Android Development] YetAnotherForumUser:
Build broken, this fixes it

FYI, https://github.com/Quarx2k/android_...mmit/8e535e655bd13013cdbd93f8f20dde07b4e21e3d breaks the build. Fix it by applying the following in ./build:

diff --git a/tools/releasetools/common.py b/tools/releasetools/common.py
index 2ab16e9..3be61ec 100644
--- a/tools/releasetools/common.py
+++ b/tools/releasetools/common.py
@@ -994,6 +994,7 @@ PARTITION_TYPES = { "bml": "BML",
"ext4": "EMMC",
"emmc": "EMMC",
"f2fs": "EMMC",
+ "auto": "EMMC",
"mtd": "MTD",
"yaffs2": "MTD",
"vfat": "EMMC" }
[Defy Android Development] overclockthesun:
[MENTION=513620]Quarx[/MENTION] [MENTION=4855459]Blechd0se[/MENTION],

Came across this today. Wonder if it could help us out on our Defy.

http://www.xda-developers.com/andro...rect)|utmcmd=(none)&__utmv=-&__utmk=121406223
[Defy Android Development] Quarx:
Yes, already trying:)

3.0 kernel now can be compiled with 4.8 gcc.
[Defy Android Development] Fight4Music:
Today Build boots up well :) It feels smooth & fast :cool:

It seem that we now use Kernel 3.0.101?! :)
[Defy Android Development] Bobcus Leper:
Can't wait for this to be ported to the DROID X!!!:D Thanks Quarx!!!:D:D
[Defy Android Development] Shubhamqweasd:
is it smoother than 2.6 builds ??
[Defy Android Development] Fight4Music:
Maybe, but this was only for the first ~ 5min. After that, system went very slow.. I think this is caused by one of the last commits. Also Camera not working (defy+) but not crashing. After taking a picture you hear the shutter but it stays only black and the picture is not saved. Same while videorecording. I also noticed that after reboot all settings are reset. Now waiting for next build :)

[MENTION=513620]Quarx[/MENTION]

What is is fixed and what's not? :) This is from you Changelog :P

Phone/3G data - 100% <-- fixed?

Sound - 100% <-- fixed?

Phone/3G data - 91%. Problem with smurf voice Big thanks to [MENTION=4806452]czechop[/MENTION] for help with debugging netmux <-- not fixed?
[Defy Android Development] Stoku:
I see a lot of important stuff finished in 3.0 kernel :o

[MENTION=513620]Quarx[/MENTION]: there's "Phone/3G data - 100%" and "Phone/3G data - 91%. Problem with smurf voice" in your first post, but smurf voice is fixed, am I right? And how's with the IncallUI delay in 3.0? I've never received a call on tests and I'm just wondering :)

Now I'm waiting for a new build of "more-trusted/daily" 2.6 kernel to get familiar with CM11 and I'll try 3.0 in this weekend.
[Defy Android Development] Fight4Music:
Quarx just updated the changelog :)

I think, if camera for both lenses are fixed then it's time to call xda-news :) ..
[Defy Android Development] measel:
JustArchie fix

I was just browsing around to find out about the flag fix by JustArchie and I didn't find a clue that CM, Slim Rom or any other ROM Dev is trying to port that fix (except some Galaxy S3 devs).

Is there anything about it? Or is it placebo??
[Defy Android Development] Quarx:
Latest 3.0 builds included JustArchie tweaks.

Next build > 19may will have it too.

Btw, First post updated:)
[Defy Android Development] ccav2000:
Been a long time I post in the DEFY forums. I still have the device as a backup phone only. I flashed the 3.0 experimental 2 days ago, it booted fine but USB wasn't working at all, no PC connections and no charge either. When I turned it off and plugged the charger it did properly enter charging mode, so at least that works.
[Defy Android Development] atulclassic:
installed 1905 nightly.

-unable to reboot to recovery from bootstrap after flashing

-system partition full (even without Gapps), can't install any root browser to make some space

will check again with reduced nightly size
[Defy Android Development] Quarx:
Size increased due JustArchie tweaks

I think i should partially revert it
[Defy Android Development] Jarod42:
hmm... reading JustArchie's explanation to the tweaks, I thought that -O3 was one of the main factors for the speed improvement over -Os...

Jarod
[Defy Android Development] Quarx:
O3 increase size ~15mb rom and give max 5% perfomance and 60% placebo prefomance.

We just cant user it, only if move system to data or sdcard.

New build uploaded: http://defy.bytekiste.de/cm-11-20140521-NIGHTLY-mb526.zip
[Defy Android Development] Shubhamqweasd:
flashed the latest build without gapps :D

after first boot , i cant get past the initial setup , it keeps force closing ..

also cant enter recovery , it shows a black screen , i was on the latest twrp recovery :P

any solutions ??
[Defy Android Development] Fight4Music:
I flashed with gapps and its booting well. But, after every restart the system is doing a 'factory reset' so that all settings are lost which i did. Also noticed this in 19.05 Build .. Performance seems good :cool:

I don't understand the f2fs instruction, could anyone explain it step by step? :)
[Defy Android Development] hotdog125:
I couldn't enter TWRP, so no way of executing the F2FS instructions:(.

Basically you have to unmount the data partition in mount and then enter the line given by Quarx in advanced -> terminal command.
[Defy Android Development] Quarx:
[MENTION=4854448]hotdog125[/MENTION], [MENTION=4148472]Shubhamqweasd[/MENTION] Build from my post link? Buildbot builds bugged.
[Defy Android Development] Huncriter:
i get black screen after flashing
[Defy Android Development] ccav2000:
TWRP is NOT working in the build from OP, if you flash this you're going for SBF if you want to install anything else. Be warned, all you get is a blank screen
[Defy Android Development] bone101:
I flashed 21.5 build

wiped system & data partition before flashing & get

Black screen after bootsplashscreen...

Recovery work

Dmesg (in twrp):

https://www.dropbox.com/s/6q7mjahr4z3ajtq/21.5__cm11_kernel3.dmesg.txt

Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf as stock rom
[Defy Android Development] hotdog125:
[MENTION=513620]Quarx[/MENTION] The build I flashed was from the link you gave a few posts above.;)
[Defy Android Development] measel:
You sure? I mean, 5% would be a lot for a device that suffers from severe heart attacks. :)

One could save another 15 MB by deleting all media like ringtones exept the standard ones maybe and all wallpaper stuff... or move it to /data or /sdcard on the other hand that would make this build less original CM11 and it might be more work to maintain the repo?!

But of course if all the hype about that Fix is mere hot air, it's not worth the work, I guess...
[Defy Android Development] Fight4Music:
Here is (Defy+) twrp and rom working with 21-05..
[Defy Android Development] Quarx:
Sorry for this, maybe usb lock was a problem on random defy..

But recovery should work for all, because it use separate kernel.

Build re-uploaded with usb lock fix.
[Defy Android Development] ccav2000:
I don't know, recovery didn't work in the previous build either, it's a big problem. I will wait others to report before I try, 2 times flashing SBF today is enough for me.
[Defy Android Development] DiegoxG:
[MENTION=513620]Quarx[/MENTION] f2fs should be activated right after flashing build?
[Defy Android Development] Quarx:
[MENTION=5456353]DiegoxG[/MENTION], yes because mkfs.f2fs not exist in previous builds.
[Defy Android Development] 57op:
The latest build is booting fine for me.

Recovery works as it should and i also managed to format /data partition in f2fs.

This is a very huge work, thanks quarx :)

Anyway, if some of you is lucky enough to have the easyrecovery, no more sbf flash is needed.

I have an old cm7 version which i flash in case recovery screws up, then i flash a TWRP recovery and then cm11.
[Defy Android Development] Shubhamqweasd:
[MENTION=513620]Quarx[/MENTION] ,, we have f2fs system by default ?? or we need to convert both system and data to f2fs ??
[Defy Android Development] 57op:
only data is possible.

you have to format the partition after you flash the zip file (so flash cm11 kernel 3.0 build, and then reboot to recovery).

Look at 1st post for the command.
[Defy Android Development] hotdog125:
Unable to download, 404 error with the link. Will test tomorrow, it's getting late here. Thanks Quarx:D.

EDIT - Spoke too soon:laugh:, downloading.

EDIT 2 - Recovery works now, formatting to f2fs successful.:D
[Defy Android Development] Quarx:
I'm use sbf with cm11 for BL7:)Some days ago i flashed sbf 13times:D

[MENTION=4148472]Shubhamqweasd[/MENTION], only data. System cant use other FS.

Build re-uploaded again with recovery fix for random defy.

Next buildbot builds also will work:)
[Defy Android Development] bone101:
Build boot up fine but

I was not able to install a app...

Maybe because of no enabled f2fs ?

Phone gets still very hot...

Sorry no dmesg this time...

Sent d my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock c rom
[Defy Android Development] hotdog125:
Everything seems fine except for the usual camera problems. Seems faster and snappier than the 2.6 kernel, f2fs also seems to improve performance.

How do I format data back to ext4 though?

EDIT - Never mind, I replaced mkfs.f2fs with make_ext4fs in the command.
[Defy Android Development] bone101:
Were you able to install an app ?

Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom
[Defy Android Development] Fight4Music:
My Defy+ gets very hot after some time (for example while charging) - bug or a feature for the winter? :D
[Defy Android Development] ccav2000:
Intalled this ROM finally, TWRP works now but it is impossible to install any app. Internal storage appears to have 0 bytes available.
[Defy Android Development] Fight4Music:
+1
[Defy Android Development] Quarx:
You need reformat DATA to ext4 or f2fs.
[Defy Android Development] Fight4Music:
Any way to format data within twrp without adb? ..

[MENTION=513620]Quarx[/MENTION] could you provide us twrp with f2fs? :)
[Defy Android Development] ccav2000:
I see. I'll do the formatting procedure tomorrow, I'll try f2fs.
[Defy Android Development] Quarx:
Twrp already support f2fs, but need add format option, will do it:)
[Defy Android Development] DiegoxG:
All I have to do is to go terminal in twrp and go to /system/bin and type mkfs.f2fs /dev/block/mmcblk1p25 ? I don't understand too much, right now I'm doing a nandroid to try the 3.0 build :D
[Defy Android Development] majamee:
[MENTION=513620]Quarx[/MENTION]: Would you please be so nice to let me know more about your way of doing this. I have a red lense Defy and BL7 and it would be great to have an easy sbf cm11 disaster recovery solution for that.
[Defy Android Development] DiegoxG:
The only problem I have is the phone getting too hot,

To solve the factory reset every boot just reformat DATA like Quarx said before

No more smurf voice :D

Edit: After a while the launcher has glitches and becomes slow and unusable, installing apex, for now it has no problems
[Defy Android Development] shamo42:
I mounted "system" in TWRP and used adb shell. Using the terminal should work too.
[Defy Android Development] atulclassic:
Quarx has given a solution in first post for launcher lagging..disable KSM