yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] sevenrock:
https://github.com/Quarx2k/android/commit/dd8c6c904639972b398835f4d28405e074b87e5b

PS: Flashed CM10-20130220-NIGHTLY-mb526.zip, it uses kernel 2.6.32.9 and "feels" good.
[Defy Android Development] Persechini:
I first got it a couple of times after the screen went erratic (probably moisture from being in my pocket while biking) and I had to remove the battery to regain control and wipe the screen. After that, since it happened once more without being in my pocket (learned the lesson) I wondered if maybe the water resistance was old and worn off (18 months of use). But I guess I'll try the new Quarx build now
[Defy Android Development] ajojohn:
Cynogen 10.1 new Camera !!

hi guyz, any checked this??

http://blog.gsmarena.com/cyanogenmod-10-1-stock-camera-app-enriched-with-high-dynamic-rage-feature/
[Defy Android Development] woodman:
Does it mean that the "ringtone" bug is gone with this new Quarx build based on 2.6.32.9 kernel ?

I mean, is it the same idea as you, sevenrock, to revert back to 2.6.32.9 kernel to avoid this bug ?

Sent from my Defy MB525 green lens
[Defy Android Development] YetAnotherForumUser:
Found the cause of excessive wakelocks, Android system battery 'use': reporting error

As I suspected, the excessive wakelocks and high battery 'use' for Android System in the JellyX kernel are due to erroneous reporting. These reporting errors are caused by a faulty patch in the JellyX kernel (and only the JellyX kernel, not in generic 2.6.32.60). The patch to kernel/power/wakelock.c needs to be reverted as it does more than just 'change some compiler warnings' - it causes the wakelock report to show expired locks as if they're still active.

Either reverse the patch or apply the following patch to revert the single change:

diff --git a/kernel/power/wakelock.c b/kernel/power/wakelock.c
index 0c231b3..4d28d80 100644
--- a/kernel/power/wakelock.c
+++ b/kernel/power/wakelock.c
@@ -222,7 +222,7 @@ static void print_active_locks(int type)
pr_info("wake lock %s, expired\n", lock->name);
} else {
pr_info("active wake lock %s\n", lock->name);
- if (!debug_mask && DEBUG_EXPIRE)
+ if (!debug_mask & DEBUG_EXPIRE)
print_expired = false;
}
}

With this change JellyX shows normal battery and wakelock statistics. Another one bites the dust.
[Defy Android Development] ktmbikerman:
I have a problem with the default browser... whenever I download an update from Quarx's website, the download crashes as it finishes, every time. Seems to be an issue with the writing of the download to the sd card, particularly large downloads. Smaller downloads are fine.

Any ideas?

Tonight's build is running great, by the way. Thanks Quarx, YAFU and sevenrock for all your efforts.
[Defy Android Development] sevenrock:
I hope so, current uptime with the latest Quarx ROM here is 4h.

Yes, the current Quarx ROM matches my latest ROM, but based on current git. I see no

reason why the ringtone bug should still be present in CM10-20130220-NIGHTLY-mb526.zip.

I am glad to see this development because I am overall short of time and had to divert more

attention to Android, because of the ringtone bug, than I wanted to at the time I bought my

phones in Nov 2012. My first flashed ROM was 17.11, the first ROM ever containing kernel

2.6.32.60, so I was affected with the ringtone bug from the beginning on until Jan 10th,

when I first compiled kernel 2.6.32.9. I am really enjoying my Defy+ phones, real good value

for the money and I will follow the developments here closely, but do not expect more ROMs

from me when the Quarx ROM solves its purpose :)
[Defy Android Development] lief.erl:
20.2 is great indeed - no more ringtone bug(hopefully), fast and responsive and cpu states now working(partially)

I have noticed following hiccups in this build:-

1. I have overclocked my phone with following setup - 300|600|900|1100 and I have noticed in system tuner times' tab(also CPU spy) that only 300, 600 graph/values are shown. Whereas, 800 and 1000 bar remain at 0. Shouldn't these apps must show current frequencies?

2. In battery option of settings, there is a blank process! I mean no name is shown for it. Any suggestion about this?

Update: After a reboot it disappeared.

BTW, is there ever going to be rtsp support in cm10?

Note: I did a clean install -> wipe data,cache and dalvik
[Defy Android Development] ccav2000:
Did anybody encountered excessive battery drain in Quarx's 20/02? I seem to get excessive wakelocks from mediaserver.

---------- Post added at 10:04 AM ---------- Previous post was at 09:50 AM ----------

Also my logs seem to be spammed by one repeating entry:

AudioHardwareMot( 1204): Output bufSize from kernel = 8192
[Defy Android Development] ccav2000:
Managed to get rid of the Media Server drain by deleting my music files and other crap from my SD. My research shows that Media Server problems are very common, and it's only fixed in Android 4.2.2.
[Defy Android Development] ppero196:
Epsylon's the faster one
[Defy Android Development] INZANEDUD:
Quarx gave to defy a new chance. An almost two years old device forgotten by motorola has an unoficial update

Enviado desde mi MB526 usando Tapatalk 2
[Defy Android Development] tarekh020:
Is the theme manager causing any crashes or what
[Defy Android Development] ktmbikerman:
Looks like we'll have data usage on the next build :thumbup:
[Defy Android Development] jurgen99:
Guys in confused :confused:

For install the 21/07 on defy green lense,i install limaro kernel o froyo kernel?
[Defy Android Development] XJeFX:
use froyo kernel, like cm7 kernel.
[Defy Android Development] zakoo2:
are you f-in kidding me?? SEARCH THE DAMN THREAD!!

this question has been asked at least a thousand times, why do you have to ask it again??

and we wont have linaro on our defy because of the locked bootloader, how hard is it to understand this?
[Defy Android Development] marhensa:
yes, it won't work.

due to almost every nightly releases, has different / updated framework-res.apk

i have some tutorial in another thread, but it's not final, I have the better one, but not yet published.

I'll pm you if it's ready, so you can create that mod for yourself, it's easy by the way.

Sent from TapaTalk | MotoDEFY - Android Jelly Bean 4.1.1
[Defy Android Development] overclockthesun:
dude not everyone is an advanced user. some people are still new and others just want to be sure that they don't destroy their device and its warranty. its ok to be cool with silly questions.:angel:
[Defy Android Development] zakoo2:
we need the four files in /system/usr/keylayout and modifiy our framework-res.apk and thas it, right?

---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------

that is why there is a q&a section. these questions must not be asked here, in the dev section. you know, this thread is for development.
[Defy Android Development] corrinti:
I think some can be just confused seeing jellybean_kernel_linaro & jellybean_kernel_stock in download section with no explanation in the first posts of the thread, that's all. And I suppose this thread is the best one now to explain some doubts about which kernel to use with builds from the thread
[Defy Android Development] marhensa:
yep:

- disabling capacitive buttons.

- editing framework: bool.xml for enable on screen buttons and dimens.xml for the height value of it

- also resizing proper png for on screen button's icon on system/app/systemui.apk

Sent from TapaTalk | MotoDEFY - Android Jelly Bean 4.1.1
[Defy Android Development] NI55AN:
On epsylons 20/07 I can't gain root access in apps like root explorer, terminal emulator and script manager. Just get permission denied.

Can't update binary via SU app... permission denied
[Defy Android Development] ksrao_iete:
For those who have root problems, here's the fix:

Wipe cache

Wipe d. Cache

Install http://downloads.androidsu.com/superuser/Superuser-3.1-arm-signed.zip
[Defy Android Development] NI55AN:
Thanks

Edit: dead link?

http://downloads.androidsu.com/superuser/Superuser-3.2-RC2-arm-signed.zip

is this right?
[Defy Android Development] ksrao_iete:
link updated now
[Defy Android Development] kanpurite:
Looks like someone's making it into the news :D

http://www.xda-developers.com/andro...mytouch-4g-slide-desire-hd-and-motorola-defy/
[Defy Android Development] NI55AN:
Should've been said we only just got hwa. I think its quite an achievement by our devs.
[Defy Android Development] ktmbikerman:
They got it all wrong... the defy is certainly very stable and perfect for a daily driver, thanks to our awesome devs.
[Defy Android Development] viper.:
Just wanted to say that mirrors and master host server are so slow .. it takes ages to download 100Mb at 15-20kb/s. It was much faster before.

Could someone upload last build to rapidshare or something , http://www.multiupload.nl/ ?
[Defy Android Development] AnTerNoZ:
AW: [JB] CM10 Android 4.1.2 for the Defy(+)

seeder binary is now integrated in our CM10 builds, u don't need the app to control it. look in running processes with system tuner or some tool that show all services and u see system/bin/rngd
[Defy Android Development] tombert.at:
Battery drain

Yes, after installing build 17-02 i got more than 5%/h over night ...

I am going to install the 20-02 build and see what happens.
[Defy Android Development] pepcisko:
yup, same here, mediaserver going crazy, dances the battery to death overnight :)

one more observation - I noticed there was some callrecording fix in the 20/02 build. But it still doesn't capture the whole conversation. It's cut, without capturing the end.
[Defy Android Development] ktmbikerman:
New ringtone bug

Just found a new bug on the 2002 build... muting the ringtone via the lockscreen (either using the hardware button shortcut or holding the up and down volume buttons) doesn't work anymore. The statusbar indicates that vibration mode is enabled but the ringtone is still heard loud and clear when you get an incoming call.
[Defy Android Development] pepcisko:
is the link correct? build.prop says

ro.build.date=Sat Feb 16 20:56:42 CET 2013

and you mentioned the repo was synchronized on 2/20
[Defy Android Development] Blechd0se:
SLUB allocator could cause problems with wifi, in fact the only allocator which worked fine for me was SLAB, even my backported SLQB caused problems. If you haven't such problems, tell me please what patch did you applied? :)

Sweep2wake is far away from working at the currently stage. I need somehow the right display sizes and if you enable it at the moment the touchscreen can behave very wired.
[Defy Android Development] YetAnotherForumUser:
It has said that for quite a few builds now. Check the kernel info...
[Defy Android Development] pawelsz:
Quarx 20130220 battery life very good, but after 1day of using ROM, after each call phone app crashing
[Defy Android Development] YetAnotherForumUser:
I have been using SLUB for as long as I've built Android kernels. I have never had any problems with Wifi... maybe those problems are not (directly) related to the allocator?
[Defy Android Development] frullewulle:
What app do you mean with BBS?
[Defy Android Development] pepcisko:
he meant BetterBatteryStats
[Defy Android Development] ktmbikerman:
Better Battery Stats... do a search on XDA for a free version, or support the developer by getting it in the Playstore
[Defy Android Development] ccav2000:
Has anyone noticed that the compass doesn't work in Google Maps anymore since a couple of months? It appears to be working fine in my Nexus 7 so there must be something wrong with our ROM.
[Defy Android Development] Kayant:
Yh it uses the same build.prop as the last build each time you recompile expect you delete the build.prop before recompiling or you can do a make clean or make installclean before using the make or brunch command to recompile.....
[Defy Android Development] rubjonny:
compas works fine for me on 20/02 quarx build, I had to calibrate it first though
[Defy Android Development] gkkovacs:
Testing YAFU's 20120220 build (why is it named 0216?) with JellyX kernel.

Battery drain problems still apparent.

Before it was called Android OS, now it's called *wakelock*...

The fact remains: out of 25 minutes uptime, something kept the (otherwise idle) phone woken up for 23.

How can I help investigate this?

*** EDIT *** It only showed *wakelock* for the first half hour of uptime, now it's back to Android OS and the rest.
[Defy Android Development] feh_pexto:
with latest jellyx and latest nightly I had no signal, no data, no wifi... :/
[Defy Android Development] pepcisko:
can't see that here. So far it behaves normally, no *wakelock* here, even media scanner seems to behave :)
[Defy Android Development] gkkovacs:
Interestingly, it only showed *wakelock* for the first half hour of uptime, now it's back to Android OS and the rest.
[Defy Android Development] YetAnotherForumUser:
Ah, so that is why it so stubbornly insists on backdating my builds. I tend to clean my table before brunch so I guess there is some logic to this, but still.

---------- Post added at 07:39 PM ---------- Previous post was at 07:36 PM ----------

The erroneous reporting bug tended to push Android System (not OS) to the top. If you have OS on top I guess there is something else at hand.

Before testing these things make sure to charge your battery to the max. This resets the battery stats so you start with a clean slate.
[Defy Android Development] YaPeL:
I'm in love with the last release, smooth, fast, and battery is really ok, 1,5% per hour on idle, wifi on, 3g on, facebook, gtalk, gmail, whatsapp, I had to delete LINE (before that, like 5% per hour).

I wonder how much better cm10.1 with kernel 3.0 can be, but I doubt much more .
[Defy Android Development] lief.erl:
Will CM10 ever support RTSP?

Is DSP manager and equalizer working for you guys?

Pardon me if this has already been discussed.

---------- Post added at 01:01 AM ---------- Previous post was at 12:58 AM ----------

What do you mean by "delete LINE"?
[Defy Android Development] 01ago:
I've asked this question before in this thread, but got no reply. But since the CM10 now approaches a stable state, I'm just wondering if anyone else experiences useless 'Allow decrease' in automatic backlight like I do. The backlight will automatically increase when I move to a bright place but will never decrease when I move back to a darker place.

Because of this, I have to set constant brightness, usually a low level to save battery.
[Defy Android Development] cyrusct82:
Enable Allow light decrease and set Decrease hysteresis to 10% in Display/Automatic backlight settings
[Defy Android Development] nedywest71:
Hi YAFU!

Which GAPPs pack (you use) shall I use with your build?

I would like to give a try.

Thanks in advance!
[Defy Android Development] 01ago:
I've enabled it and tried various hysteresis levels but still not working for me. The screen stayed as bright unless I turn it off and on again for it to return to the suitable level.

So is it working for you? That's strange, because once I even tried full wipe and it didn't help.
[Defy Android Development] YetAnotherForumUser:
Any of the available (JB-compatible) versions? I have only the lightest of the lightest of Google-bits on my phone which I promptly disable when they've done their things.

If anyone has any serious opinion on this let them speak up, otherwise just take the latest/greatest (or not) bundle and drop it in.

---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------

Does it respond on adb or is it completely dead when it shows that black screen? The solution will be somewhere in the mountain of patches between Quarx and Blechd0se, the question is only which of them... same goes for the 'ringtone' bug.

BTW, Blechd0se wants to know about your black screen: #643.
[Defy Android Development] gkkovacs:
YAFU, I've been meaning to ask this for a long time: is there a way to lock the phone app in memory?

One of the few things I hate about CM10 is that the phone app is almost always slow to start up, and since it's not a huge memory hog, it might be worth to lock in somehow.
[Defy Android Development] YaPeL:
Uninstall an app called "LINE" it was sucking all my battery, any way, the consumption on idle seems to be around 1.5/2.0, not bad, but could be a little bit better.
[Defy Android Development] YetAnotherForumUser:
I'm not really the right person to ask this question as I am more of a Unix/Linux type than a seasoned Android hacker. That aside I'd say anything is possible as the source is just a few keystrokes away. I have not looked into this as I hardly use the phone as a phone and I don't mind waiting a few more milliseconds for the phone app to show up. I know an earlier CM10 release by Quarx did just what you wanted. I also know this change was reverted, if I remember correctly because the memory is better spent elsewhere on these rather small-minded phones. If you search the (earlier parts of the) thread you'll find some more information on this.
[Defy Android Development] Antiga Prime:
http://www.xda-developers.com/android/lock-apps-in-memory-the-easy-way-or-the-hard-way-on-the-motorola-defy/
[Defy Android Development] erickxd:
I have a problem with my MB526.

The lights of the physical buttons do not light more MENU and SEARCH .

The MENU button stopped lighting when installed the build 20120217.

If you know how to fix?

Anyone else had this problem?

Thank you.
[Defy Android Development] theclaytons:
I did. Reinstalled different ROM and then went back to this one and it worked.
[Defy Android Development] fairxda:
Ringtone bug gone? Maybee ...

Before the Rom from 20130220 my defy+ got the ringtonebug ca. after 37-38 hours.

Now after 41 hours no ringtonebug. :good:

Will watch forward ...
[Defy Android Development] trurl3:
Let's look here:

http://xdaforums.com/showthread.php?t=1889300

or here:

http://xdaforums.com/showthread.php?t=1890495

Here you are in short (the light way):

Locking Apps In Memory

Create a file local.prop in /data (eventually instead of actually present)
Enter the names of the apps in the file:
Example:

sys.keep_app_1=com.android.contacts

sys.keep_app_2=com.android.phone

sys.keep_app_3=com.android.mms

sys.keep_app_4=another app

sys.keep_app_5=another app

- leave one empty line on bottom - it's important!

Reboot and enjoy!
[Defy Android Development] woodman:
Hi ktmbikerman,

Is your default browser download problem only related to the new 20130220 Quarx build ? I never experienced this kind of issue...

I totally agree, thanks to all of them and all other xda members's contributions. :good:
[Defy Android Development] wrase:
Whatsapp Location

Since 2nd Boot ROMS sending location on whatsapp leads a fc

problem known?
[Defy Android Development] my2ct:
AW: [JB] CM10 Android 4.1.2 for the Defy(+)

No problems here while sending location via whatsapp on 2nd Boot (latest quarx pure)

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] ktmbikerman:
I've actually noticed it for some time now, but never could pinpoint when in the download it failed. I'm on a 1M connection, so it takes about 30 min to download a 150M file. Nine times out of ten, the download fails as it ticks over from 99% to 100%, hence my assumption that it's related to when the file is transferred from a temp download location (RAM?) to the SD card.

I've tried with 3rd party browsers and they work fine.
[Defy Android Development] Deonix:
I saw on the Portal that small apps from the Xperia T/Z devices have been ported on all CM10 devices. So... to Quarx, can you try to include them? It will be nice to see them on the Defy.
[Defy Android Development] bbllaazzee:
Updated with YAFU's build (20-02) works great. Wi-Fi is working good as well.

My defy was stable on 28-11 Quarx and 03-12 BFS-JellyX, didn't update due to the ringtone issues and other difficulties faced by the members. So a direct update from 28-11 to 20-02, feels good. Cannot comment on the performance, as I see no difference, I will report on the battery part after a day or so. Quarx 28-11 with BFS JellyX, I used to get 3d-12h of battery on normal phone usage and occasional WiFi. One bug with BFS-JellyX was the soft-touch keys does not generate the vibration(random, but very frequent). Now it is gone with the YAFU's build :)
[Defy Android Development] woodman:
OK, I will try to check this but I use default browser from a long time now and as I said, I never noticed this phenomenon... Did you try with another sd card ?

I have to report about my cm10 tests :

I flashed 20130220 quarx build on my defy green lens but I had to revert to sevenrock 20130117 unofficial build because of RIL issue ! Just after a fresh install of this last quarx build, I tried to send to myself a MMS but sending failed. This fail is not very annoying. What is very annoying is that my RIL was out of order, no sgnal. At this moment, if i tried to toggle airplane mode, it didn't work.... Then, I reflashed 0220 build over itself with cache and dalvik wipes and I retried my MMS stuff and I finally not had the RIL issue. But I'm not sure that it would work everytime...weird... Anyone else with RIL issues ?
[Defy Android Development] marcospulido:
Can you edit and save the Light sensor levels?

This doesn't work for me, when i save the Settings process stop.. and restart..

anyone experiencing this or just me?
[Defy Android Development] htcmaxx:
Same problem here – since end of 2012 versions.
[Defy Android Development] Persechini:
This one is easy to "fix", you have to change the number os brightness levels each time you want to save it, say, if you have 6 steps, change to 5 or 7 (just repeat the number for the last step or set it to your liking). When you edit it again, change back do 6 and so on
[Defy Android Development] mikrom.cz:
it was only backlighted black screen (even it become from dimmed light to full like during boot animation). but after couple tries it was okay, i set couple things, try to enable Clever Conectivity and go to bed. morning phone shining with black screen. only solution was restore \data from 10.2. (because i skip that step with capital letters always backup before... :) )

edit: every try with clear cache, calvik, flash any zip.. end with stuck on "starting applications"
[Defy Android Development] gkkovacs:
Unfortunately, this easy "solution" does not work, I tested it on GB and on JB as well, nothing is happening.

The other, complex solution was being reported as not working as well, but I haven't tested it.

I'm not sure how Quarx did it befor, but I guess somehow before compiling the ROM.

I'm also not sure why he removed it, it makes for a very ****ty phone that needs several seconds of startup every time I try to dial somebody.
[Defy Android Development] fairxda:
After 51 hours still no ringtonebug ... Quarx-Nightly 20130220, Defy+.

To cite Homer Simpson: Juhu.
[Defy Android Development] AnTerNoZ:
AW: [JB] CM10 Android 4.1.2 for the Defy(+)

if I set apps in local.prop this way they started in group secondary server. normal without that they started in other groups, and the apps are a bit faster in response.
[Defy Android Development] gkkovacs:
With the latest Quarx nightly, I had the ringtone bug after about 1 day.

Now using YAFU's custom build with JellyX kernel, no ringtone bug so far, but some lagging is starting to show after 1 day of uptime.

This year's most stable and fluid build was sevenrock's 0117.
[Defy Android Development] fairxda:
Oh ... Is it the Quarx-Nightly from 20130220?

Ok, that was said already, that the ringtonebug could have more than one cause.