yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] 1of16:
I just installed 2014-06-11, but after that the recovery seems to be gone? every time I try to enter it my phones reboots.

already tried a fresh install (sbf etc.) but still got the same effect.

additional if I install 2014-06-11 and gapps (6-2 minimal) the setup wont work again, ain't got that problem with 2014-06-07.

but with the non working recovery i cant install gapps after the first reboot ;)

any ideas ? :confused:
[Defy Android Development] LimaBEERRE:
Bug list?

Do you have a bug list like the 2.6 one?
[Defy Android Development] Huncriter:
i have the same problem on latest biuld 12-06
[Defy Android Development] domokos:
Workaround:

1. Install the rom

2. Boot, install Ssh server from a local backup

3. Ssh to the phone

4. Remount /system rw

5. Unpack/copy the gapps zip content to the appropriate location

6. Reboot & Enjoy
[Defy Android Development] Anton111111:
How about 06.16 ? Is recovery fixed?
[Defy Android Development] frozenwaverider:
Working for me :)

22hours up time

SORRY WRONG THREAD

Please delete/ignore I'm using 2.6knl

MB525 Red, Nord BL7, HF5X, Quarx CM11 - 16/06/14
[Defy Android Development] frullewulle:
How about bluetooth connection to carkit and voicequality? any experience with that?

In latest CM11 with 2.6 kernel, when audio is connected over bluetooth to carkit, voice quality on the other side of the line is not that good, sometimes it's more or less fine, some times it's not good at all.
[Defy Android Development] Huncriter:
on 17-06 recovery is not working
[Defy Android Development] Anton111111:
I tried 17/06. Recovery doesn't working.

---------- Post added at 05:36 PM ---------- Previous post was at 04:48 PM ----------

have ability to fix recovery without sbf ?

---------- Post added at 05:59 PM ---------- Previous post was at 05:36 PM ----------

i'm on 17.06 about a hour and i again see telephon problem ;(
[Defy Android Development] maxilus:
no recovery

I have a similar Problem like some of the others.

The phone reboots after a few minutes and wants to be reconfigurated (login to google etc.).

If i want to go into the Recovery Mode a white screen flashes and the phone goes into rebooting and then into a boot loop.

I have access to the bootloader but Fastboot/adb dvices don't show me the device but it is installed corectly and the drivers are all there.

i would be greatefull if somebody could help out or has a workaround to get the Recovery running again.

Greetings Maxilus !
[Defy Android Development] ela1103:
its good news master quarx you are great developer for our moto defy
[Defy Android Development] mayur2j:
Great job Man.. :good: I can't wait to use this feature on my defy..
[Defy Android Development] lexer98:
Quarx & Blechd0se :victory::victory:

i have a few question ...

1-) whats "parts" of DEFY have propietary code ?

2-) This kernel and Aero has all drivers made ​​from scratch :eek:?

Thanks :good:
[Defy Android Development] Quarx:
Audio, camera, RIL, SGX - proprietary parts.

In 3.0 we made opensource audio lib and will use open camera libs.
[Defy Android Development] thekguy:
[MENTION=513620]Quarx[/MENTION] was just wondering if you can shed some light on triple buffering, vsync, and video encoding(720p) in our kernel? Thanks a lot for your work
[Defy Android Development] ela1103:
master you are great
[Defy Android Development] runeupo:
just thumbs up thanks or buy Quarx and other devs a Paypal-beer, no need to write him into megalomania....:beer:
[Defy Android Development] YaPeL:
so now that you have opensource audio lib, is it possible to get low latency audio, and dsp tunneling on the defy? the last one would be killer
[Defy Android Development] gyorgyszemok:
CM11 november 17 nightly uploaded...! Yay! ^_^
[Defy Android Development] 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 :)
[Defy Android Development] hrk:
/proc/last_kmsg is really a lifesaver for debugging. :good:
[Defy Android Development] okij:
Some feedback on the 11-17th nightly

For testing, I installed cm-11-20131110-NIGHTLY-mb526.zip (after stripping it down to about 168 MB in size by deleting some unneeded files with 7-zip) ontop of my working installation of CM10.2. :D

According to AndroSensor app, the magnetic sensor (and therefore also the compass) isn't working yet, but all other sensors are working. :)

I experienced that quite often after switching the Defy on, just the softkey LEDs are lit, but the screen stays black. Turning it off and on again for a few times helps. ;)

Also, for those who are interested, switching from Dalvik to ART via Development Options went without problems (for this I was using a self-stripped-down version of pa_gapps-modular-mini-4.4-20131114-signed.zip which is just 17 MBytes in size), although updating the apps took some time and quite a few apps (e.g. TitaniumBackup) aren't compatible to ART yet.

All in all, even without ART, CM11 with kernel 3.0 has a very fluid user experience! :good::D

I'm really hoping that in-call-sound and camera get fixed soon, so that we can start to use CM11 / Android 4.4 on a daily basis. :fingers-crossed:

For now I have to restore a TWRP backup of my CM10.2 installation, because I need my phone (for making calls) tomorrow. ;)

Thanks [MENTION=513620]Quarx[/MENTION] and [MENTION=4855459]Blechd0se[/MENTION] for this great development and keep up the good work! :victory:
[Defy Android Development] level_666:
Audio tunneling needs some requirements in hardware it seems, i wouldn't expect this feature on Defy
[Defy Android Development] bone101:
Bugeport 17.11 build

No call sound here

I Flashed straight on last CM10.2 w.o. factory reset....

In first time the rom was a bit buggy , but then it went really fast

Google account and all apps seems to work pretty good

No Display problems (only short time of usage not everything is testet)

Could not install xda app , maybe becaus of the app2sdcard bug

Wifi & Mobile Data seems to connect but no server could be found...

After factory reset Wifi,Data & Sound Bugs still present

Dmesg : https://www.dropbox.com/s/e3nxtll96639fqv/defy525red.txt

MB525 red lens
[Defy Android Development] abhi.eternal:
Does this mean that camera now works?
[Defy Android Development] niksy+:
Quarx2k pushed to cm11.0-3.0 at Quarx2k/android_device_moto_jordan-common

79c5d28 Initial support incall sound (works, but with whistle:D)

"But with whistle" :D :D

[MENTION=3557519]abhi.eternal[/MENTION] The camera doesn't work, they would definitely say that if it did :D I tested the build, it's not working :) But the driver is there, which is still a good thing and I guess what has to be done now is for various configs to be set-up correctly :)
[Defy Android Development] playitlouder:
Aaaaand its fixed.

Thanks Quarks!
[Defy Android Development] srijithn:
-deleted-
[Defy Android Development] frullewulle:
open or propetary

Which parts of this kernel are open source and which parts are propetary ? (motorola)
[Defy Android Development] 57op:
Already asked, already answered:
[Defy Android Development] rootdefyxt320:
You have to wipe data/factory reset in stock recovery. Then reflash SBF via RSD-Lite.
[Defy Android Development] maxilus:
Thanks, but it has been over a year since my last sbf flash. Which sbf is good for flashing from cm11 ?

Thanks for the help again.

Greetings Max
[Defy Android Development] YetAnotherForumUser:
Use piggybacked bootmenu to avoid need for SBF

To avoid the need to flash from stock after finding out recovery does not work or hitting some similar problem, may I suggest installing the piggybacked bootmenu I made a few months ago? It uses the stock kernel and as such is immune to kernel-related problems which cause the thing to fail to boot as well as failing versions of TWRP. The stock kernel does not support f2fs-formatted partitions but it does allow you to gain access through adb to root around the phone at will. Use a PC to access those f2fs-formatted partitions if needed.

After installing this zip and selecting 'recovery' during boot you should notice the blue led lighting up for three seconds. Press volume-down to start bootmenu, any other button (or just wait) to start TWRP.
[Defy Android Development] 9Lukas5:
Ypu can simply use the zimage-recovery and ramdisk-recover from the 2.6 kernel builds and place them in your system, set correct permissions and your recovery is working again :good:

L

Gesendet von meinem GT-I9505 mit Tapatalk
[Defy Android Development] bone101:
Delete , cheers

Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom
[Defy Android Development] bone101:
Don't work for me.....

And i found the reason :

system/bootstrap contains the bootstuff

your zip replace system/bootmemu

Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom
[Defy Android Development] YetAnotherForumUser:
Check again, you'll see what it does... as to why it doesn't work for you, no idea. Flash it AFTER you flash a new distribution.

Hint: /system/bootmenu = bootmenu, /system/bootstrap = safestrapmenu. Newer distributions only contain safestrapmenu, not bootmenu. The zip adds bootmenu on top of safestrapmenu. More info can be found by reading the posts about bootmenu, starting here...
[Defy Android Development] bone101:
So i added your lines to system/bootstrap/recovery.sh .....

with the result no blue led by entering the recovery....

16.6.2014 CM11

Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom
[Defy Android Development] YetAnotherForumUser:
You should not need to add any lines anywhere for bootmenu to function. When running 2.6.32 you can add something to make overclock work as before, but that is moot on 3.x as of yet.

Bootmenu is - or should be - started from /system/bootstrap/script/recovery.sh. This script exists in a standard distribution, a modified version of it is included in the zip. Check your phone for that script, it should contain a comment line referring to bootmenu ('Give user option to run bootmenu instead of recovery'). The script uses the toolbox and busybox binaries for some functions. Some versions of toolbox seem to give problems (crashing on getevent, etc), this is described in the thread. If this is what causes your problems, you should notice the blue led coming on for an instant. Bootmenu itself lives in /system/bootmenu, if that directory is missing on your device you did not install the zip or installed it before installing a new distribution.
[Defy Android Development] bone101:
blue led come for real short time ...

so its possible that i didn't saw it.

But if the vol. down button is pressed the phone reboot..

Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom
[Defy Android Development] YetAnotherForumUser:
Sounds like the aforementioned problem with toolbox not supporting or crashing on the getevent command, see here for more information and a possible solution. This version was only tested on earlier releases (with the 2.6.32 kernel with internal overclocking enabled) but it should still work, mostly. You could give it a try...
[Defy Android Development] DragonautMk:
What about new builds? :) A little bit of changelog? xD
[Defy Android Development] spear1403:
Telephony problem

When I use this app SoftLocker (doesn't allow the device to enter deep sleep) the telephony layer problem is no more.

Of course the battery is another story entirely:).
[Defy Android Development] 1of16:
recovery is still broken with 20140703 :-/
[Defy Android Development] fairxda:
With 20140707 recovery is not broken ...

but telephony layer - modem problem is still alive ...
[Defy Android Development] fairxda:
EDIT:

Unfortunately my second try to boot in recovery was not successfully.

The same with the rom from 20140720.

Now I will try with the rom from 20140721.

Oh year ... sbf-flash and the whole procedure ;) framaroot, sndinitdefy, cwm, twrp, twrpupdate, rom-flash etc.

EDIT2:

And yes, now it works. I have tried it 3 times with success to go into the recovery.

EDIT3:

Modemproblem still alive ... Maybe my old sim-card is responsible.

Display sometimes glides away ...

Batterynotification stands still.

EDIT4:

After deleting batterystats.bin and restart, batterynotification seemed to work again,

hm, a little bit fast to come to 100%.

But after unpluging the notification jumped to 93% and some seconds later to 87%, then 89 ...
[Defy Android Development] ironfisted:
Quarx: anyway you might be able to point devs in the right direction on Verizon note 3 with kexec? They have a discussion thread in developing section over there. If not I understand.
[Defy Android Development] Samuelgames:
You'll probably have better luck asking the HP Touchpad people, specially since both share a Qualcomm SoC, the way kexec works on our device is very specific to allow radio to reboot properly among other things
[Defy Android Development] ironfisted:
Cool I will look into it, thanks.
[Defy Android Development] fairxda:
Deleted ...
[Defy Android Development] ela1103:
Quarx

We are all waiting for our new born Rockstar Baby.

We are all thinking when Android L is going to release that the same time our Moto Defy Bulid with Kernel 3.0
[Defy Android Development] Bobcus Leper:
Yeah, I can't wait for [MENTION=513620]Quarx[/MENTION] to build Android L for the Defy, because when he does, the DX will have it to!:D
[Defy Android Development] m.ksy:
:cool:
[Defy Android Development] Bobcus Leper:
Of course, only with the Dev magic of m.ksy!
[Defy Android Development] htto:
The script android_device_moto_jordan-common / ramdisk / f2fscheck.sh is broken.

I was wondering why setupwiz wasn't getting a clue, turned out that my ext* /data was not mounted... Problem being:

<3>[ 3.431060] fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk1p25 at /data options: discard error: Invalid argument

Turns out that

FSTYPE=`$BB_STATIC blkid /dev/block/mmcblk1p25 | $BB_STATIC cut -d ' ' -f3 | $BB_STATIC cut -d '"' -f2`
if [ "$FSTYPE" == "ext4" ] || [ "$FSTYPE" == "ext3" ]

fails because

$BB_STATIC blkid /dev/block/mmcblk1p25 | $BB_STATIC cut -d ' ' -f3 | $BB_STATIC cut -d '"' -f2
fd0b1e01-abd7-4590-8b68-9d05d9bf68e0

because

# $BB_STATIC blkid /dev/block/mmcblk1p25
/dev/block/mmcblk1p25: LABEL="userdata" UUID="fd0b1e01-abd7-4590-8b68-9d05d9bf68e0" TYPE="ext3"

Btw. the non BB-blkid has a neat feature:

#blkid -s TYPE /dev/block/mmcblk1p25
/dev/block/mmcblk1p25: TYPE="ext3"

or how about using

# $BB_STATIC blkid /dev/block/mmcblk1p25 | $BB_STATIC grep -ci f2fs

to check for f2fs being on there?
[Defy Android Development] Sublimis:
Installed this 3.0 kernel ROM a few days ago on green lens. Clean install, formatted data partition to F2FS with the TWRP.

1. Had telephony layer problems, as someone said, basically every time the phone entered deep sleep. Switched baseband to South Africa 3.4.3-361 (was Central Europe 3.4.x), no more telephony problems (maybe helps someone). EDIT: didn't help.

2. Temperature sensor not working. It's available, but gives no readings whatsoever.

3. Battery life... 40 mins of GPS and a bit of fiddling around and the battery drops from 90% to 1% :) Still exploring whether this may be faulty charger, old battery, false battery sensor readings, or something else... any suggestion is welcome. The fact is, phone has still never turned itself off because of the low battery, even if GPS was used when battery <10%.

4. Everything else seems to be working just fine (oh, except button brightness cannot be adjusted). All in all, ROM feels more smooth and more powerful than 2.x kernel ROM - when you switch KSM off as somene suggested, because of the Trebuchet.

Still looking for a reason to go back to 2.x kernel ROM. ATM it seems like only high battery usage may force me to do this.

Keep up the good work :good:
[Defy Android Development] htto:
Well, I've somewhat different results ond my mb525 green lens. Battery life's pretty nice, had a ca. 3h long angry birds session, and and the battery just hit 4% right now. For me the Telephony layer makes it a mess, since it's missing the main feature of a phone ;) I've had the feeling it's more related to having used the telephony layer (getting an incoming Call, maybe also c2dm) killed it shortly after. Anyway, will try that out-of-central-europe-trick for the baseband. Does it actually matter or is just for enabling additional/different frequencies?

I also noticed, that panic_daemon tries to operate on /dev/ttyACM0, though I only have /dev/acm0...

And the actual memory seems to be more limited than with 2.6. Iirc I had ~476MB whereas now there's only ~458MB.

EDIT: Ok Sublimis seems to be quite right. Th TP-layer problem doesn't need any calls at at. Just oberserved the following:

- TP-layer problem occured with disabled WLAN -> auto reboot

- didn't touch the phone

- WLAN still off

- SIM not unlocked (since it's PIN protected and I didn't touch the phone)

- no strings attached, i.e. not charging, not adb'ing

- BB is south africa 3.4.3-361 (so this doesn't help me, neither did some other BB)

-> still a TP-layer problem plus reboot

--> had two of those exclamation mark notifications :/
[Defy Android Development] Sublimis:
To share my newest findings...

1. Telephony layer problems: Baseband switching didn't help. I also tried replacing the following files: /system/bin/rild, /system/framework/telephony-common.jar, /system/framework/telephony-msim.jar with the corresponding files from the 07-24 nightly (2.x kernel-no telephony problems) - didn't help.

(Got the idea while looking at the diagram at http://www.kandroid.org/online-pdk/guide/telephony.html).

Also wanted to try replacing corresponding library files (libril.so, etc.), but noticed that they are the same in both ROMs.

IMHO the only thing to prevent telephony layer problems from occuring on a phone at rest (ie. not charging, screen turned off, no wifi connected, no ongoing call) is to turn off the mobile data.

2. Temperature sensor still not working - can somebody confirm this?

3. As of battery life, I declared my Motorola charger dead. It smells like something burned out in it, so I'm testing different charger now.

458 MB vs. 476 MB memory difference is beyond my imagination :) Pretty sure Quarx or Blechd0se know the answer :)

EDIT: While finishing this post, just got RIL reboot prompt on a phone plugged to a charger, with wifi connected and mobile data turned off. :|
[Defy Android Development] htto:
1. It's pretty serious. It keeps looping (even though slowely) from bpanic to bpanic :/ Anyone able to tell if a pre-june-8th kernel-build works better in terms of the telephony layer

2. There's only battery temperature in /sys. Probably related to

<4>[ 0.073486] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_core
<4>[ 0.073516] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per
<4>[ 0.073516] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup

3. Mine's charging fine, the battery life is ok I'd say

4. About the ram... it seems to detect the ~476, though there's about 42MB reserved

<6>[ 0.000000] Memory: 224MB 247MB 3MB = 474MB total
<5>[ 0.000000] Memory: 468176k/468176k available, 43824k reserved, 0K highmem

5. Why the heck did CM include that frikkin only containing names, 1,2MB png of the contributer cloud in Settings.apk? :S
[Defy Android Development] jxk25:
Current Status Query

Can anyone tell me about the current status of this ROM on Red lens MB525? I'd appreciate if you could tell me your impressions on things like performance, stability and battery life.

I'm currently on the parallel 2.x build and thinking about making the switch if this one is mature enough :)
[Defy Android Development] Sublimis:
Workaround for telephony problem bug

Great news, found a simple workaround for telephony problem, the one which doesn't involve building the kernel :)

Open the following file with some rooted text editor: /etc/init.d/90userinit

Somewhere at the beginning, before the first 'if', write the following line:

echo on > /sys/bus/usb/devices/usb2/power/control

Save the file, and reboot at will

Basically it prevents the device 'usb2' from entering autosuspend. Usb2 happens to be the device our baseband processor is connected to, so it's quite obvious what we are trying to accomplish here - don't let our baseband sleep.

The battery impact of this workaround remains an open question.

Yes indeed, thank you. Although it remains a mistery to me where to get hold of this file?

I have also mistaken 'r' for 'retval' variable name in hub_port_init() in hub.c source (talking about poor coding practice..), so the first error ("device descriptor read/64, error -71") comes from usb_control_msg() call and not hub_port_reset().

But this basically changes nothing, as it turns out the problem is not in the resume-part, but rather suspend-part of the kernels' usb driver. Figured this out after comparing hub.c and message.c files between 2.x and 3.0 kernel sources, just to realize that resuming of usb devices is done basically the same in 3.0 kernel as in 2.x kernel, one notable change being support of superspeed (usb 3.0) devices, but this has hardly anything to do with the baseband processor of ours.
[Defy Android Development] sumeet_on_line:
Installation Help

Hello Guys,

I am on 2.x kernel and i want to install 3.0 build can any one provide installation guide for this, any prerequisites required or just like 2.x builds ?

Can i downgrade to 2.x after installing 3.0 ?

What are the things not working in 3.0, is it daily driver ?

Thanks in advanced.
[Defy Android Development] htto:
That disablnig suspend, will work around the issue, was to be expected (and it really does hack around the stall). That defconfig file is in arch/arm/configs and defines the kernel config options, hence the CONFIG_*. I don't mind building the kernel, since I build the rom myself anyway.

I'm a bit fascinated by:

shell@mb526:/sys/bus/usb/devices $ ls -l /sys/bus/usb/devices/usb2
lrwxrwxrwx root root 2014-08-15 08:03 usb2 -> ../../../devices/platform/omap/musb-omap2430/musb-hdrc/usb2

that means, I was looking at the wrong bus and one should look at

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 3.00
S: Manufacturer=Linux 3.0.101-04284-g20e53be-dirty musb-hcd
S: Product=MUSB HDRC host driver
S: SerialNumber=musb-hdrc
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

Which probably is http://processors.wiki.ti.com/index.php/Inventra_HDRC_USB_Controller (and not to be confused with HDRC for High Dynamic Range CMOS).

Which makes for more evident musb-driver failure, I'd say.
[Defy Android Development] Sublimis:
Pretty much the same procedure as for CM11 2.x kernel, except you MUST do a clean-install for the first time. Other than this, I had to reformat data partition and change filesystem from EXT3 to F2FS from the TWRP prior to installation, because of that 0-bytes free bug - might not be the case for your phone.

Downgrade only possible from a full backup.

Daily driver - because of the telephony problem, no, not quite yet.

Not working - magnetometer, temperature sensor. Telephony layer reboots the device when awaken from the sleep. Other things working like they should.