yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] lexer98:
CNA 4.0 + BFS 30/12 no boot for me :( (Defy green)
[Defy Android Development] kHron0S:
CNA 4.0 + 30.12 CFS booting and running ok for me.

Sent from DefyX RED.
[Defy Android Development] domokos:
I can confirm: CMS works OK. BFS does not: it stops upon boot after red led is turned off, black screen, hard buttons with low backligh. Quarx 23/22, enough free space in /system, interactive, BFQ io scheduler, JellyX 30/12. The same happens with the pervious JellyX build.
[Defy Android Development] n0_alterNative__:
Neither for me. I tried with the last JB build, wiped data and cache and didn't work.
[Defy Android Development] kHron0S:
Watch out which version of kernel do you choose 'cos the 30.12 CM10 by quarx has trace enabled back CNA 4.0 build date is 27.12 and i think it doesn't have trace enabled.

Sent from DefyX RED.
[Defy Android Development] skeevydude:
I compiled rom and kernel from source yesterday (bfs) -- The first boot was just fine for me but I was unable to reboot afterwards. No amount of wiping would help and I did them all (all stock recovery wipes and all CWM.

@Blechdose -- I'm in the middle of tweaking the bootmenu to support your kernel -- all the extra governors are added (no tweak settings yet), removing the iosched_sio option and making a page just for IO tweaking (way too many options to add all the io tweaks to the end of Cpu Settings). Also gonna make a Kernel Tweaks page with things like echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled. Do you have any suggestions for Kernel Tweaks?

I plan on being done in another day or two -- its my first time writing new code in C. Even if all I'm doing is CRTL+C CRTL+V coding :p, its still my first time with new code and not merging and fixing conflicts.

To everyone else, I'll tweak the boot menu for Quarx's kernel once I'm done doing all of this -- it'll simply be deleting things to support Quarx's kernel by then -- B's has 14 governors enabled, 8 io schedulers while Q's has 8 governors and 3 io schedulers. (Might be off by one or two on the governors -- its early and I don't feel like fact checking yet).

Not related to the above or Blech0se's kernel, just a ? and idea

I also have a ??? if anyone can help. I've been experimenting with adding more capacitive buttons and realized that our touch drivers don't recognize touches where the phone says "Motorola" by the earpiece. Is there a way to tweak the touch driver to recognize that area? It would be a nice area to hide some media buttons (play, pause, track skip), a camera button, or whatever we can all agree on.

On the Bravo, we have enough dead space next to menu and back to include two more buttons down below (we only have 3 capacitive buttons in the same space that the Defy has 4) and that made me think if I can add buttons there, why not up top or the sides? Turns out that the sides will work, just not the top (according to the Touch Overlay in Dev Options).
[Defy Android Development] Aslolo:
Nice idea, but the Defy also has lots of space between menu and home and back and search^^

Fallen out of the sky, send by my Defy+
[Defy Android Development] skeevydude:
So do we :p. Just no search, which is useless anyways imho -- would rather it be an app drawer\long press recent apps button myself.

EDIT:

Crap, meant to ask -- which kernel is the most stable for gov and io testing? My kanged kernel from yesterday will only boot once...need to echo and cat the new govs and ios to find their supported values.
[Defy Android Development] Blechd0se:
In fact i thought about this too, however it was pointless for me because everytime Quarx pushed out a new build my bootmenu becomes useless. My idea was to solve this "problem" with an app, but yeah the bootmenu would be very nice :good:

There is of course one tweak for the BFS Scheduler "/proc/sys/kernel/rr_interval" you can look up all related tweaks here.

And of course all added governers could be tweaked, just like those in quarx kernel and the bootmenu. You can find those values in the source code of the governers here. There are probably lots of more tweaks, but i can't count them all here :p

This is my setup: Quarx Rom from 23.11 and my kernel 30.12 (interactive / zen). It should work, i guess those compatibility issues are related to the new rom updates, but we simply have to be patient :)
[Defy Android Development] Kayant:
" Blechd0se I was meaning to ask you this but the trace support you speak of is it related to this commit ?

I just wanted to know what exactly it's for and why it causes such a pain??

Thanks for your continued work and Happy Holidays to all ^_^
[Defy Android Development] ofmb:
it still seems to be broken i think

http://xdaforums.com/showpost.php?p=36137187&postcount=14468

do you think there's a reason that sometimes last_kmsg won't be saved ?

thanks for all your work !
[Defy Android Development] Blechd0se:
For the probably yes, can only say where its enabled it the kernel :) You can read all about tracepoints here http://kernelnewbies.org/Linux_2_6_28#head-87501bfdeacc6b01eea92db039af6a6150a4cd1f and like you see, its frustrating that the kernel needs it enabled when the rom needs it...

About that /proc/last_kmsg what doesnt work correctly?
[Defy Android Development] skeevydude:
Just a little update

All IO's + IO settings added and their scripting done, just need to get the proper values and adjustment rates. All governors added, half the settings done. Have to finish the governor settings, find IO and GOV values and rates, complete the governor script, finish both config files, and add an IO Settings to the main menu. I'll get on with the kernel tweaks after IO and Govs are finished. Currently there's 45 different IO settings alone (not including the 8 choices for schedulers). Not sure on governors yet since I haven't added all their settings in.

This ended up being a bit more than I thought it would be -- but its a really good learning experience for me. I've been trying to keep everything done under external/bootmenu but a few files under jordan-common need to either be patched or added.

Blechd0se, Did you mean the 12\23 rom? I can't find an 11\23 rom anywhere.
[Defy Android Development] Blechd0se:
Yes sorry about that i mean 23.12, was a stupid typo :)

And thanks to you work :)
[Defy Android Development] ofmb:
It seems I had a mistake and what happens is a quick extra reboot that overwrites last_kmsg.

Any idea how to bypass this behavior?

I'll try to get it from bootmenu-adb later this day

EDIT: HOW DID I MISS IT ?? IT'S THE 2NDBOOT!! :D

[ 0.000000] Linux version 2.6.32.9-ga28fcc4 (jfqk83@zch68lnxdroid07) :o

soooooo - last_kmsg works great, but just not

enough
[Defy Android Development] Sh0m1:
Can this be modified for Defy Mini?
[Defy Android Development] Kayant:
No it uses a different CPU (Qualcomm from my research), Stock = Locked bootloader which means kernel wouldn't load. The 2ndboot/2ndinit hack is needed for the kernel to boot.
[Defy Android Development] vinu.shukl:
Black Screen on Boot

I clean installed Quarx's latest build (31/12) after doing a full wipe. The phone (MB525, green lens) booted alright so I went into recovery into and installed JellyX. On reboot, it stuck on a black screen (the screen was ON, but with nothing on it). I had read that doing a data wipe will solve this problem, and it did.

However, once JellyX was up and running, I had to reboot for some reason the black screen reappeared on reboot. I couldn't afford another data wipe so I just flashed the latest Quarx build again.

TL;DR Black screen on boot, only data wipe fixes the problem all other wipes are useless. Help?
[Defy Android Development] Blechd0se:
Try my ramdisk here. I allows you to enable adb at boot. Send me the logcat and the dmesg output :)

By the way; did you tried it with the rom from 23.12?
[Defy Android Development] kapil_dheer:
Can you please elaborate....what's the procedure to get these logs at boot.

Thanks
[Defy Android Development] veddandekar:
I also faced the exact same problem as Kapil on latest CM10 by quarx(31st dec)

I also have a MB525 DEFY with green lens....
[Defy Android Development] skeevydude:
Same here as well. Phone and issue. Is it because of the stock froyo kernel, would the gb kernel work better. Used Quarx 23/12, 30/12, 31/12, 18/11 and your 3 newest kernels.

Best I've ever had was 18/11 Q and 22/12 B. Only booted once, rebooting once with no changes would cause the same issue to appear.

Having issues with adb and Mint 14 (DNS & X issues too). Reverting back to Mint 13 today -- ran better and plays nicer with android.

Also haven't had a single bfs build boot either.

//Didn't boot ics either, though I didn't seriously expect it would work :p
[Defy Android Development] vielikiy:
how to solve the problem of not ringing incoming calls?
[Defy Android Development] skeevydude:
Not sure....I also had a big issue with random calls (both in and out) sounding like Darth Vader underwater. Some weren't random and could be replicated very easily -- for example, my buddy has an Alaskan phone # and provider and I can't call him or receive calls while running any JB\custom kernel combo -- changing to 7 or 9 (no custom kernel) fixes it. The issue effects both my Defy and Bravo. FYI, the Defy\Bravo differences are similar to the Defy\Defy+ differences -- camera, battd, opprofdaemon. The Bravo is essentially a crappy Green Lens Defy :p.

//Imagine Darth Vader underwater talking through an old 28.8 modem...best way I can describe it. Effected my voice on their phone and my earpiece as well.
[Defy Android Development] hackergnome:
I believe they have fastboot
[Defy Android Development] ofmb:
so i tried now to get last_kmsg from bootmenu but the file doesn't exists .

booting the OS overwrites last_kmsg with the stock kernel kmsg so it's no help :/

do you think of any solution ? it appears i'm not the only one with such reboots though it doesn't seem to be jellys kernel
[Defy Android Development] mGforCe:
Same here, however with MB526, build CNA 4.0. Tried latest jelly X kernel, black screen after boot. Restored from Nand backup.
[Defy Android Development] Blechd0se:
Connect the phone to your pc, push my ramdisk (or install it in recovery and make a backup!). Reboot the phone and start adb on your pc an run "dmesg" and/or "logcat".

Send me the output (by the way, you could get this information with some research ;) )

This sound problems are related to my kernel or the rom? Do they happen with Quarx Kernel too?

I am using still Quarx Rom from 23.12, didn't test 31.12. Did a full wipe and installed then my kernel, then restored Apps.

This black screen happens for me too, but disappeared after I deleted chrome and i still don't know whats causing this problem,

it excisted for me since the 25.12, the problem was i nearly reverted every single commit from that day,

but still had black screen with chrome installed, so i am kind of "stuck" here...
[Defy Android Development] Kayant:
Linaro 4.6+ toolchain support for kernel compilation :D

Going to test this later when am done with school work could be interesting to see if we get any performance gains :)

Thanks to wskelly

http://xdaforums.com/showpost.php?p=36321082&postcount=85
[Defy Android Development] ccav2000:
Have reverted to the 23/13 build too, using the 22/12 JellyX. Is the 30/12 JellyX working with the 23/12 ROM too?
[Defy Android Development] ofmb:
yes
[Defy Android Development] niksy+:
+1! It sure does :) Been using 30/12 CFS JellyX + 22/12 CM10 for 3-4 days, all's perfectly fine!

Kayant, will you compile and share JellyX built using linaro? I'm very interested in doing some benchmarks...and sharing the results afterwards, naturally. I know benchmarks don't tell us much about the quality of everyday use, so please no comments on that :p And what benchmarks do you guys suggest as the best/better ones? Blechd0se praised AnTuTu... I got ~3580 last night on AnTuTu, if someone is interested :cyclops: (above mentioned CM10 and kernel + clocked at 1.1GHz, i/o scheduler set at deadline, V6 Supercharged (100%))
[Defy Android Development] joke19:
Hi, someone work on a nice cm7 kernel?

Sent from my MB526
[Defy Android Development] juan296:
Yes,Maniac..

Arch Linux User ..
[Defy Android Development] joke19:
Not much information but thanks.

Sent from my MB526
[Defy Android Development] Blechd0se:
Walter is also working on a kernel for his rom :)

If you cant wait, try to compile it for yourself :)
[Defy Android Development] niksy+:
Seems that he has just started, but it sure will be interesting to try a stock ROM running with a custom kernel! :fingers-crossed:

P.S. His 'hub is here - https://github.com/walter79?tab=activity
[Defy Android Development] _ReBoot_:
if I have not misunderstood, maniac is working too

https://github.com/maniac103/android_device_motorola_jordan-common/tree/gb_2ndboot

https://github.com/maniac103/android_device_motorola_jordan

And it's epsylons CM7 git with custom kernel https://github.com/tpruvot/android_device_motorola_jordan/tree/gingerbread

CM72-20121126-NIGHTLY-Defy.zip: http://defy.wdscript.fr/jordan-nightly/
[Defy Android Development] wskelly:
Hi Blechd0se,

I downloaded your ramdisk, and I tried to unzip it to see what you did to enable adb early. I tried with a couple of different tools but I think the file might be corrupt:

wskellenger@marquette ~/Projects/blechramd $ gzip -dc ramdisk | cpio -i

gzip: ramdisk: invalid compressed data--format violated
cpio: premature end of file
wskellenger@marquette ~/Projects/blechramd $ /home/wskellenger/Projects/cm/out/host/linux-x86/bin/minigzip -dc ramdisk | cpio -i
-dc: No such file or directory
cpio: premature end of archive
wskellenger@marquette ~/Projects/blechramd $ /home/wskellenger/Projects/cm/out/host/linux-x86/bin/minigzip -d ramdisk | cpio -i
/home/wskellenger/Projects/cm/out/host/linux-x86/bin/minigzip: can't gzopen ramdisk.gz
cpio: premature end of archive

It *does* unzip a few things but all of the init.rc files are not there. When I push this file with adb I just get bootloops with one of Quarx's old ROMs. I've created my own ramdisk image and I'm trying to enable adb early but it doesn't seem to work during the boot process.

I am getting the black screen problem as soon as I reboot the phone, I'd like to try and debug it.

The ramdisk I'm trying to create has the following:

default.prop is like yours:

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb

in init.mapphone_umts.rc, uncomment as appropriate:

#Adb at boot
#write /dev/usb_device_mode charge_adb
#write /tmp/usbd_current_state usb_mode_charge_adb
#chmod 0666 /tmp/usbd_current_state
#start adbd

Anything else required?

Thanks for any help.
[Defy Android Development] renoob:
Got black screen with CNA 4.0 & 30.12 bfs kernel, 30.12 cfs is running snappy with no issues!

Enabled 256m swap and will be test loading apps soon.

Sent from beyond the Droid
[Defy Android Development] Blechd0se:
Well, i got the same errors, however i have no clue whats causing this problem. i haven't even touched the audio-parts.

It started first around the 25.12 and i have gone through every commit that day, but still didn't managed to get it to boot without a data-wipe...
[Defy Android Development] wskelly:
I think I finally found the regression.

The problem seems to be this commit:

c061d4e3c2d5c5a330bf0ec666327aeb8de83276

Revert "Update jHash to v3"

Blechd0se (Wed 26 Dec 2012 08:45:10 AM EST)

Since this only affects a header file (jhash.h) this may have started an incompatibility involving the Jenkins hash function, I don't really know what it is used for but checkout the difference in kernel sizes:

wskellenger@marquette ~/Projects/kernelmod $ ./putkernel.sh

Copying kernel to HEAD-c061d4e3c2-kernel...

pushing kernel to device...

3495 KB/s (2316328 bytes in 0.647s)

wskellenger@marquette ~/Projects/kernelmod $ adb reboot

wskellenger@marquette ~/Projects/kernelmod $ ./putkernel.sh

Copying kernel to HEAD-befbbb88d9-kernel...

pushing kernel to device...

3843 KB/s (3192304 bytes in 0.811s)

wskellenger@marquette ~/Projects/kernelmod $ adb reboot

So the file *with* the incorrect version of this file is quite a bit smaller. Anyway. I am going to try and revert this change back on the HEAD of my repo and see if it boots.

:)
[Defy Android Development] ccav2000:
Interesting finding! Still, Blechd0se needs to sync his repo with the latest Quarx's commits, specifically the revert that prevent battery drain would be nice.
[Defy Android Development] Blechd0se:
I reverted this commit because i updated jhash completly on the 27/12. Therefore i introduced the new jhash implementation.

Things i noticed; if you have fsync diabled and your devices reboot for some reason, its more likely that this "black screen bug" occurs.

So i guess its related to some corrupt data or system files.

By the way; which filesystems do you use?
[Defy Android Development] Blechd0se:
Thanks for your effort :) , i will revert the following commits:

1dbc2fe - Probably useless anyway

8aff006 - won't revert this, because it simply doesn't work

15d2403 - will revert this, thought i bring some more stability

f01cdb9 - i don't think thats the problem, because CONFIG_TRACING_SUPPORT has to be enabled for this commit and we can simply turn it off (it changes nearly nothing)

c061d4e - jhash is kind of strange, this commits reverted my changes (so its the same with Quarx one), however 8f066ab does update jhash, so this should cause problems, not the revert

But i can't really test it since ones the kernel boots up it should run just fine, however i found out that installing chrome reproduces this bug (at least for me).

Last thing to mention: Thank you wskelly for your work! It's much better than this simply things like "My phone doesn't boot up". This should be an example how to report a bug properly. :)
[Defy Android Development] Fight4Music:
Blechd0se, can i use 13.01-CFS with quarx latest Build? Or should i use any other build?

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] Blechd0se:
Try it, its a test build mainly for those with the black screen bug. It doesn't contain the commits mentioned above except the jhash thing. If it boots up fine, bug solved (only if 30/12 didn't boot up).

It also has some additional features, i will update the changelog when i make a full release :)
[Defy Android Development] Fight4Music:
I will try it tomorrow morning and report back ;)

An other question, can we expect jellyx 3.x if quarx 3.x Kernel will Work? :)

(Just read theres progress with his kernel)

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] ktmbikerman:
Feedback on 130113 cfs kernel: No GSM network received, toggling airplane mode and rebooting doesn't help
[Defy Android Development] Blechd0se:
Which Rom are you using? Network is fine for me on 31/12. Did you have the black screen bug on a eralier build?
[Defy Android Development] Fight4Music:
i tried kernel 13.01 cfs on my defy+ with quarx 10.1 cm10. GSM is working fine but with jellyx 13.01 interactive and SIO it feels slower (a bit "laggy", SMS/phone app take More time to open) than qkernel of 10.01. For now i'm waiting for a full jellyx release which includes the latest commits which are applied in this thread.

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] ccav2000:
Kind request: specify the exact version (date) of the ROM you use, saying just "I use the latest" can create misunderstandings since the latest is not always the one you think.
[Defy Android Development] ktmbikerman:
Using quarx 100113, sorry for the lack of detail.
[Defy Android Development] ktmbikerman:
I installed the 130113 cfs kenel again over quarx 100113 rom on my Defy+ over lunchtime, just to confirm my previous finding. Same GSM problem, no connection. The RIL appears to be broken as I could not toggle through the 2G/3G modes and there was no APN info in the APNs screen. The APN info and GSM connectivity is restored when I flash a this quarx kernel again.
[Defy Android Development] wskelly:
Just booted and rebooted with the 13-01-CFS, I extracted zImage and pushed it via ADB.

Great job!

Jetzt... Was hast du gemacht?? :)
[Defy Android Development] Blechd0se:
Reverted the things you mentioned, but i left jhash untouched :) You can see my changes on github, i hope the next build wont have this bug, but again thanks to all of your work.

For the next release i have included some patches of the maunline kernel mainly for the ext3 driver and a backport of porportional rate reduction for tcp.
[Defy Android Development] wskelly:
Hm, okay my build of your latest changes as of last night had the black screen issue. I am going to check out 13-Jan and see what happens.
[Defy Android Development] wskelly:
I just built the most recent kernel from Quarx, f0ffc75c6f35, booted with no problems.

I tried to build your e03a633, with comment: Revert "Some kmemleak fixes" (posted right after "Disabled some things to solve black screen"), but could not get this to boot. \\

Which commit represents the 13-Jan build, since that seemed to work fine for me, I'd like to try to build that one.

Thanks!
[Defy Android Development] Blechd0se:
The build from 13/01 does contain all commits from 13.01 as far as i know, however i the most recent kernel i enabled CONFIG_TRACING_SUPPORT again, maybe those black screen issues are related to this commit ? Because its only enaled when TRACING_SUPPORT is enabled and its enabled in Quarx Kernel, but of course without this commit on slab.
[Defy Android Development] wskelly:
Hm... Don't change anything else yet.

I just got it to work using the gcc compiler and not the Linaro compiler. Then I went back to the Linaro compiler and it worked. So it *MIGHT* be some sort of corruption that is happening after 2nd boot. I would see the boot animation after a fresh ROM install (including your kernel) -- but then after 2nd boot, I would see the buttons light up and then normally where the boot animation would be, I'd get nothing.

I'll try to summarize the findings in another post here...
[Defy Android Development] wskelly:
Okay this is interesting.

Build entire ROM using your sources with HEAD @ ded367a473 (using vanilla gcc for kernel)

Flash ROM .zip and wipe cache + dalvik

Rom starts to boot, everything looks good. Boot animation starts.

Boot animation stops after some time and 2nd boot happens.

Get Moto logo. Screen turns black. Red LED is on. See test/init of button LEDs. Right to the point where boot animation should start...

Boot animation doesn't start and eventually the Red LED turns off.

Reboot into recovery and push the exact same kernel via ADB.

adb reboot

No change, the phone doesn't boot.

Pull battery and reboot into recovery.

Start adbd and push HEAD-befbbb88d9-kernel (this is your 'fix buttons for bravo') kernel

adb push HEAD-befbbb88d9-kernel /system/bootmenu/2nd-boot/zImage

adb reboot

Boot animation starts, phone boots.

WTF.

Now it gets more interesting.

Wait for the phone to boot, it has to optimize apps and whatever else. Takes a couple minutes. Now I reboot into recovery again.

/arm/boot $ adb push 2.6.32-ded367a473-kernel /system/bootmenu/2nd-boot/zImage

1310 KB/s (2306164 bytes in 1.718s)

The phone boots. Perfectly fine.

What in the hell??

It must be something in the file system, and whatever that something is, it doesn't affect the old befbbb88d9 kernel. Once that something is fixed, the new kernel works fine also.
[Defy Android Development] Blechd0se:
Sounds really creepy. Did you tried to revert my commit a4b8fe15bd ?

Don't know whats causing this, since it sounds really wired that a corrupt data prevent the display to show up.

And its funny that once you wiped your data the bug wont occur again (at least for me) and some even don't have this bug.

To shoot into the dark; maybe there is a problem that the ext3 filesystems get loaded via the ext4 driver?