yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Sublimis:
You're quite right. Seems like our Motorola Phone () device, being numerated as 1-3, is not connected to usb2 but usb1, and musb hdrc is the only device on usb2.

It's beyond my comprehension what is the exact role of musb hdrc, especially regarding baseband connectivity, and especially because preventing usb1 (1-3) device from sleeping does not prevent telephony layer issues. Any ideas? Anyone?
[Defy Android Development] htto:
Well, I'd say the HDRC (Highspeed Dual Role Controller), as the name hints, is the usb controller that controls most of the stuff

Quoting from http://processors.wiki.ti.com/index.php/Inventra_HDRC_USB_Controller

Host mode driver:
Mass Storage Class (MSC) Host
Hub Class.
Human Interface Devices (HID)
Isochronous Devices(ISO)

Slave mode driver:
Mass Storage Class (MSC) Slave.
Communication Device Class (CDC) Slave support
Remote Network Driver Interface Specification (RNDIS) Slave support.

It could be the slave mode cdc part taken by the hdrc, and thus communications related. Or, what I'm thinking of, there's some sort of 'misunderstanding' of the host and slave driver, thus a suspended slave would confuse the host and maybe the other way around. Probably the wireless/bluetooth stuff gets handled there as well, and since the chips does all communication it gets kinda flaky [/wild guessing].

Btw, disabling autosuspend for usb2 drastically drains the battery. Doesn't seem to get some sleep even in airplane-mode. Scuked dry over night.

Depends.... I kinda did it without. Basically I didn't go for f2fs in the first place (and noticed that having a filesystem label breaks the f2fs-detection script), thus there's no need to restore /data. For /system it's a bit more difficult, because you not only need to put the zImage (maybe with ramdisk) and the modules back, you also need to stop the system from using /system/vendor. The latter one is because 2.6 uses a newer PVR graphics driver, which is unale to work with the older PVR userland from the 3.0 driver. Thus surfaceflinger gets nuked all over the place. Took me some time to figure out that there were two vendor libs for pvr.

I for one would prefer either same PVR version or at least same vendor lib locations (PVR userland in the 2.6 build is in /system/lib). But hey, I'm probably also the only one that's missing file(1) from userspace :D
[Defy Android Development] Pulec:
Build 0830 works great.

Camera works (green lens), no telephony problems anymore and battery now seems to be calibrated correctly. And its fast, thanks!
[Defy Android Development] Quarx:
I got almost same effect with telephony problem on 2.6.32

If remove https://github.com/Quarx2k/jordan-kernel/blob/AeroKernel/drivers/usb/host/ehci-omap.c#L741

"ret = request_irq(78, usbtll_irq, IRQF_DISABLED | IRQF_SHARED, "usbtll", pdev);"

In 3.0 code of ehci-omap.c splitted to ehci-omap.c and drivers/mfd/omap-usb-host.c

Need find way add correct this code and test.
[Defy Android Development] Lord_Flaya:
I nowadays switched to another phone, and thus have no mandatory use for my defy. Would happily do pin-point testing and/or other specific trials to aid in development in the best way i can (perhaps with some basic guidance). :)
[Defy Android Development] TheDelta:
DEFY XT everything

Hi,

Sorry to hijack the thread, but seems like a good place to ask questions.

I am used to flashing ROM/Kernel on RAZRs and a friend of mine wants to start flashing on her Defy XT 535.

Can anyone point me to any link that will give me a working rooting guide.

Also please confirm how things will be for Defy, to flash a custom ROM/Kernel

For RAZR I usually root>install safestrap(recovery)> flash rom> flash kernel etc

Shouldn't the steps for Defy be similar? I don't know what recovery to use or from where to get the correct recovery as i am confused if everything works the same for defy, defy+ and defy XT.

Thanks in advance!!

P.S. - Kudos on getting the OTG working without external power, hope it comes to our RAZR soon :D
[Defy Android Development] hotdog125:
Wrong place to ask a question like this:p.
[Defy Android Development] ebol94:
Tried cm-11-20140919-EXPERIMENTAL-kernel3.0-mb526 but everytime I reboot it asks me to configure everything again! Like if I were booting up for the first time.-
[Defy Android Development] Casper1982:
Same here, on 2nd reboot, asks me to configure everything again...
[Defy Android Development] CodeVanya:
http://quarx2k.ru/roms/defy-cm11.0-3.0/

The download link is not working. :(
[Defy Android Development] starbright_:
It is really estonishing what Quarx and other devs are able to do.

Beside from the technical challenge to port a new kernel, what are the expected advantages?
[Defy Android Development] htto:
Do you by chance have a ext3/4 /data partition? I had that problem, when the f2fs-detect script was unable to handle it and mounting of /data failed completely. Thus you get in-ram saving of data and loose it every reboot.
[Defy Android Development] Don DD:
The link works now but [MENTION=513620]Quarx[/MENTION] would modifiy the OP with the link to his new page:

http://quarx.cm-for.us/
[Defy Android Development] Fight4Music:
It's just a new location on his server:

http://quarx2k.ru/buildbot/roms/defy-cm11.0-3.0/
[Defy Android Development] CodeVanya:
Thanks man! :)
[Defy Android Development] ela1103:
We are all thing android l powered 3.10 kernel with our moto defy this year end .

Quarx working for 3.10 kernel with more imporvement
[Defy Android Development] okij:
Is the 3.0 / 3.10 kernel development for the Defy dead or just interrupted?

Looking at Quarx's GitHub, there hasn't been any commit on the 3.0 and 3.10 kernel for about a month now. I'm wondering if Quarx has dropped this project because of his recent development for the ASUS PadFone S. :(

This would be really sad because the 3.0 kernel project for the Defy has made a great success and almost all parts are working by now. Also the possibilities of the 3.10 kernel, thanks to the sources we got from the Moto 360, haven't been used yet.

Therefore I would like to ask [MENTION=513620]Quarx[/MENTION]: Is the 3.0 / 3.10 kernel development for the Defy dead or is it just interrupted because of your recent work for the PadFone S? If you plan to continue the development, when would this be the case?

Please don't get me wrong: I'm sure that every Defy user who ever used a CyanogenMod build on his Defy is grateful for every single line of code that you ever wrote for this great little phone! But if we want to keep it alife, I'm sure that only a working 3.0 / 3.10 kernel would really bring new life to our beloved Defy. :)
[Defy Android Development] 9Lukas5:
Side note: it's 3.10 not 3.1 ;)

Gesendet von meinem One mit Tapatalk
[Defy Android Development] Quarx:
3.10 Currently have problems with CPCAP, which cant be solved yet.

Also i got a work. This just eat whole my time... and only free 3-5h per day.

Work with Asus PadFone S almost ended, already everything fixed in cm12. I bought its because of LTE and can't use 4.4, that's why i start make 5.0 :)

Current version of 3.0 not have Telephony Problem, but need more tests. But it have problem with battery and red camera.

First CM12 for Defy will be with 3.0, but need fix RIL part. In 5.0, bionic very changed and many closed Defy binaries stop working.

I know all want fast CM12, but time really not enough. :(
[Defy Android Development] santi1993:
Can we help you with something? your work with this device is awesome, you're awesome!

I hope that if u can reach these levels of stability with CM11, CM12 with custom kernel only will take some test time to work, less or more depending of your free time... but with your mind it could be done!

Thanks, thanks, thanks! i'll test whatever you upload to try help you development! hope best regards from south america Quarx! you're teh boss!

PD: do u havy any official merchandising? i will want a shirt that says quarx and the CM11 logo, i'll be proud of it and hope i'll could help you!
[Defy Android Development] vulture BIAN:
Thank you very much . . Thank you ., we will support you
[Defy Android Development] dovw:
My daily driver is probably the last non-LTE 3G CDMA only device - the Moto G (1st Gen) xt1028/xt1031 and it does not yet have any working 5.x ROM with outgoing calls and SMS after months of attempts to get it working. The apparent cause is that it seems that CM12 has introduced a SIM dependency. Are you aware of this from your early work on CM12 on the Defy (which also has a non-LTE CDMA variant)? Is this at least partially what you were referring to in your comments about RIL? Do you have any suggestions?
[Defy Android Development] axel2230:
*bump* Any progress? Everything seems dead here. I'm looking forward to lollipop. Also thanks to Quarx our very talented developer in the Defy forums.
[Defy Android Development] s_u_n:
I am visiting the Defy forum after a long time.

The last post from Quarx indicates that he is quite busy. Is there some news after that?

BTW: What is the latest 4.4.4 stable ROM I can download?
[Defy Android Development] juan296:
Excellent job quark, I would like to know :

Is there any way to get Aircrack-ng at this moment? Since you can modify our kernel it would be awesome D:

Enviado desde mi C6943 mediante Tapatalk
[Defy Android Development] mjraogr:
awesome [MENTION=513620]Quarx[/MENTION]

I follow your work, and hope you keep this nice development and we have proud by the Defy is keeping alive

My Defy first generation 2.1 keep running even my others mobiles since 2010 wait for this
[Defy Android Development] dc239:
It would be nice if i saw defy with 3.0 kernel and android 5.0,but the developement is at the end point due the hardware limitation of defy i think
[Defy Android Development] mick711:
For me last Google Lolipop is not a good os like windows 8.1 i flash my old SBF with 2.2.2 Rom and i think i don't upgrade because i like to accept call just press accept button no slide just simple and i never see a new phone with accpt call button just an horrible slide .

So if google read this post simple action is very good no need to slide push jump to accept :D

Very good job with this 3.0 kernel just wait for a CM11 with 3.0 Stable and possible accept button lol :D if anyone know how make it thanks ;)
[Defy Android Development] mjraogr:
Hello [MENTION=513620]Quarx[/MENTION]

Some new for Defy development?

Thanks
[Defy Android Development] AndroidJohny:
How can i install this kernel to the 4.4 nightly cm 11.0?
[Defy Android Development] rootdefyxt320:
[MENTION=513620]Quarx[/MENTION] What modifications are required in the 3.0 kernel to make it compatible with 'Defy NewLife' partitions?
[Defy Android Development] laharl_22:
Any one can reup files for cm11?
[Defy Android Development] Alias X:
Is there still any useable version of the 3.0 Kernel around? For the old CM11.
[Defy Android Development] cristianosite:
New build is up.

Edit 1:

Error during instalation:

set_metadata_recursive:some changes failed

E:Error executing updater binary in zip '/sdcard/cm-11-20131120-NIGHTLY-mb526.zip'

Error flashing zip '/sdcard/cm-11-20131120-NIGHTLY-mb526.zip'

I'll try to download the file again and will report back.

Edit 2:

My bad. After upgrading recovery again (since I already did this few days ago) I was able to install the last nightly, which is running very well, according to the OP problems list.
[Defy Android Development] Quarx:
added to first post.

Bravo build soon too:)
[Defy Android Development] overclockthesun:
Was just reading your updates on github.... gonna download this and try it out now...... to think I just flashed 4.3 again from 4.4 1 hour ago :cyclops:
[Defy Android Development] pepcisko:
11/20 build - doesn't seem to connect to the cell provider's network at first boot..

Second boot is okay, connected to mobile network just fine..
[Defy Android Development] slimshady76:
Please keep the KitKat related discussion in its own thread. This one is meant to discuss issues/report feedback on the 3.0.8 kernel development.
[Defy Android Development] slaphappy76:
Sensors

Hi,

I just installed the new version today and it is a step closer to daily use.

What I noticed is that the sensors of the AK8973 not quite work orientation sensor and magnetic field and the temperature is 0.0 °.

Great Work :)

Slappy
[Defy Android Development] srijithn:
New audio libs.. The audio on headset quality has gone wild. This is best quality in industry now....

There are screen freeze happening. But. 20-11 build is leaps ahead of previous build...
[Defy Android Development] mitchum67:
Installed latest Version. After unplug and plug USB into Defy it doesn't load. After unplug power supply from wall, waiting 10 sec. and plug it again, then it loads ... I'm not a developer, I don't know if it is kernel specific.

Gesendet von meinem SGH-I777 mit Tapatalk
[Defy Android Development] atulclassic:
which temp..battery or CPU because Defy doesn't have a CPU temp sensor
[Defy Android Development] slaphappy76:
Sensor

Good morning,

the sensor has an integrated temperature sensor is read out to the time even with the previous Android versions. I think that the sensor is located near the battery ...

http://www.droid-developers.org/images/b/b2/AK8973.pdf
[Defy Android Development] kryzeK:
Gapps...?
[Defy Android Development] Lord_Flaya:
In gapps thread ...

---------- Post added at 12:16 PM ---------- Previous post was at 12:15 PM ----------

http://xdaforums.com/showthread.php?t=2012857
[Defy Android Development] vetko:
I've tried yesterday the latest build, but had some issues:

First I've installed it with the latest "MINI MODULAR PACKAGE" GApps from http://xdaforums.com/showthread.php?t=2397942,

But on the first boot, no Google Setup has been initalized, neither the Launcher, I've got a black screen, only the status bar worked, from where I could access some settings and etc.

After reinstalling it WITHOUT the GApps package, it booted correctly, but had some bugs:

1. Green LED always on

2. Browser was unusable through to rendering problems (black spots were rendered in some places of the page)

3. No data counter arrows on the data icon

4. I had the "Launcher3" crashed on first scrolling

Have not been tried it in more details, but I will, if I manage to get GApps working.

EDIT: I was installing it after completely cleaning /system, /data, /cache (everything)
[Defy Android Development] matiasrey:
1. A workaround was posted here or in the CM11 thread already.

2. True, a bunch of users reported it too.

3.Thats the way its meant to be on KK, arrows only appear on the data/wifi tiles, not on the status bar itself (Google said it was CPU consuming).

4. Never happened in my case.

Try to use core gapps from the gapps thread posted one post before yours, worked like a charm.

Cheers.
[Defy Android Development] xinrag:
For me the core gapps did not work. I see there a installed Google play service but an accessible app. The green led is still lightning here, too.
[Defy Android Development] overclockthesun:
You need to further strip down the gapps package. Use the pagapps Package.... Just in case you choose to use ART in the future
[Defy Android Development] cristianosite:
Well, I'm sorry to repeat this again, but maybe someone could try to help/clarify the GApps issue, since a few users are facing the same problem.

If I use 11-16_GApps_Core_4.4_signed.zip from the GApps Trhead the system doesn't boot anymore, just stays in the boot animation.

In case I use the pa_gapps-modular-mini-4.4-20131118-signed.zip from this thread, then the phone dos boot and I can see the option do include Google account and also I can include my Google account data. However, I am not able to synchronize anything and also I don't have any GApps installed (not even PlayStore apk).

Am I missing anything here? And sorry again to being off topic, but this is only happening in CM11 with 3.0 kernel version.
[Defy Android Development] groksteady:
Also, [MENTION=2915683]BaNkS[/MENTION]'s core gapps that [MENTION=4148153]TJKV[/MENTION] linked to works with ART.

I've had problems, too, with black screen and status bar with just about every different kind of gapps that's been linked, but yesterday I finally got the 1116 Core GApps to work. Possibly helpful, I slimmed CM11 down by deleting nearly all the ringtones, notifications and alarms out of /system/media/. I tried hard to slim down the pagapps zip, but didn't know where to begin on the libs, which is 20+MB right there. Also, I apparently had an error first time I downloaded the 1116 Core GApps (although, not from the thread linked on this page); that download had lots of process FCs. Redownloading fixed that.
[Defy Android Development] overclockthesun:
Hmm.... I see the Core Gapps package has been updated. It is now Odexed. The previous one wasn't. I apologize for telling people it didn't work. The new packa should work just fine.

For those who only end up with a black screen ...should delete ringtones/notifications/a;arms and most of the non-essential fonts.
[Defy Android Development] hrk:
Please, only KERNEL related discussion here. KitKat ROM has its own thread. Thanks.
[Defy Android Development] coolshahabaz:
Unnecessary post!

Deleted
[Defy Android Development] GodSlayer:
Worked at first boot. Had insane wakeup delay.

Second boot - does not boot at all
[Defy Android Development] playitlouder:
Nevermind...
[Defy Android Development] cyrusct82:
New build is up for 3.0 kernel:

http://defy.bytekiste.de/cm11-nightly-defy+3.0Kernel/snapshots/cm-11-20131123-NIGHTLY-mb526.zip
[Defy Android Development] mauroaraujo:
What was the changes at the kernel ???

The changelog is older...

:confused:

----EDIT----

Sorry, now I see the difference at the changelog :)
[Defy Android Development] Tausif Ahmed:
Does this kernel support ION memory management. If so can sense 5 be ported? :confused:
[Defy Android Development] overclockthesun:
Video Codec/hw 720p/ION stuff - 100%
[Defy Android Development] gamerxxxn:
Hey guys,I was trying this out on my defy,and the device never used to wake up after the screen went off. So i took a dmesg after one such issue and a subsequent reboot ( this is the first time I'm taking a dmesg/development initiative,please advise me if there's something better i can do in place of dmesg)

Hope it helps :)
[Defy Android Development] Blechd0se:
Hello, thanks for your log, unfortunately it won't help us much, since you rebooted.

I just post my [How-To-Debug]-Tutorial here, to remind everyone that debugging can be quite easy (point 8.) will be interesting for you).
[Defy Android Development] coolshahabaz:
A great guide that was, thanks!

D5+/cm10.2/1.2GHz.

Sent from Tapatalk app
[Defy Android Development] tmcookies:
Hi [MENTION=535343]all[/MENTION]:

i have a spare defy lying around here, so wanted to test this build. Right now i'm running CM10-20120912-NIGHTLY-mb525 with Android 4.1.1 and Kernel 2.6.32.9 (Fri, Jun 3 2011).

As far as i understood, i would have to first flash the update-recovery.zip from this thread and then i can flash the NIGHTLY you posted above. Do i need to flash the Kernel or is it included in the build?

thanks.
[Defy Android Development] cyrusct82:
Is included.
[Defy Android Development] tmcookies:
I tried to install both the latest snapshot (cm-11-20131123-NIGHTLY-mb526) as well as this one (cm-11-20131120-NIGHTLY-mb526) and in both cases the installer (Team Win Recovery Project v2.6.0.0) gave me the error message

"set_metadata_recursive: some changes failed"

What am i doing wrong? (By the way inbetween i installed the latest 10.2 (cm-10.2-20131020-NIGHTLY-mb526) version.

regards.
[Defy Android Development] GodSlayer:
Install the update-recovery zip and reboot before you flash cm11
[Defy Android Development] tmcookies:
Thank you GodSlayer, i was a little bit foolish and seem to have killed my defy, but i won't clutter this thread anymore and have posed my further questions in the Defy Q&A-Forum for anyone who would like to help.

regards.
[Defy Android Development] sunil_defy:
I was wondering if I can use 4.4 build on 2nd December be used as a daily driver. I have a trip coming up and I would very much rely on wifi so kind of skeptic ....any help ?
[Defy Android Development] hrk:
No, you can't. And wrong effing thread! :mad:
[Defy Android Development] thekguy:
Wrong thread: because 2nd December build does not have 3.0.8 kernel, and questions go in Q&A section. Anyways the build you're talking about has working Wi-Fi
[Defy Android Development] vetko:
Just some little shy questions (if You do consider them offtopic or spam, pls delete the post):

Could we know something about the current status of the 3.0 kernel? I mean:

What are the issues that are blocking the devs to finalize it?

Can they be solved, or currently we are staying in the dark with 3.0?
[Defy Android Development] hotdog125:
See the OP. They can be solved, it just needs more time and work.
[Defy Android Development] vetko:
It's ok, I am constantly checking the OP and the issues list, but since I haven't really seen any recent activity on github related to 3.0, I feared that maybe Quarx is blocked with something.
[Defy Android Development] hotdog125:
Yes, like any other normal person, Quarx too has other things to do like a job, eat, sleep, etc.

Anyway, the 3.0 kernel will definitely take more time to move into a beta state.
[Defy Android Development] DragonautMk:
Quarx is One of most important devlopper for the defy, i think after real life he have a lot of project to work, and i think that fix a kernel di not easy :)
[Defy Android Development] sipe1:
My two cents. Running Defy MB525 flashed to MB526 via sbf.

Running good, flashed first CM10, then CM10.2, update recovery and 4.4 with 3.0.8

Wifi running great, no wakelocks for now, everything seems like in first post.

Only problem is that is glitching in airplane and normal mode, it fast switches between airplane and no sim card, maybe is bug that I have no sim card in.

Activated airplane mod it's ok now.

One question if everyone know, can I switch to 4.4 kitkat with older kernel without problems? Can I just flash over 3.0.8 kernel and newer nigthly?
[Defy Android Development] sevenrock:
Blechd0se started to work on kernel 3.4 :)

https://github.com/Quarx2k/jordan-kernel/commits/p-android-omap-3.4
[Defy Android Development] playitlouder:
[MENTION=513620]Quarx[/MENTION] any news regarding the camera? Seems to be hard to get working. :(

[MENTION=4855459]Blechd0se[/MENTION] wich advantages would the 3.4 Kernel give us exactly? Fancy new memory management or better KitKat support?

And could any of the Devs update the build to 4.4.1 which should have improved ART support (working WhatsApp...), or is the CM side of things not ready yet?

[Don't get me wrong I don't wanna ask for ETAs :p]
[Defy Android Development] Blechd0se:
Our 3.0.8 Kernel was developed with ICS in mind, 3.4 was developed with JellyBean in mind. 3.4 just has better compatibility for android.

And by better i mean really better (androids staging area was re-merged in the 3.4 mainline release) and its a long term release.

I am just experimenting with it, see what i can do here and there. In terms of memory management, we are already on a good way. The

same goes for the cpu managment. I recently added some very nice patches for 3.0. Interactive has now a ondemand patch (which

was originally developed for server), to keep the performance up on high load scenarios.

What really grinds my gears is the power management as well as the dss (display)/pvr/sgx driver. The latter one seems to be really bugged,

i am not sure what really is causing problems, but its easy to reproduce; just let the device do a lot of graphical stuff in a short

amount of time. I could track it down to some gralloc errors, but thats just a guess. This and the PM-code (deepsleep takes about 20-30%),

are the only things that would keep me personally away from a 3.0 build.

Keep in mind that this is a truly dedicated 3.0 kernel thread, i can upload a recent 3.0 AOSP build, but only in terms of development,

not in terms of trying ART or any other productive things.
[Defy Android Development] bone101:
So give the good things their time that they´re need

All in all good news THX

[