yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Antiga Prime:
There has been something interesting that has happened to me with every CM10 rom for the past few months. For some reason Android OS uses ridiculously large amounts of data on Wifi as far as I know. The last time I was up to 15gb, on 31/12 build. Now I'm not really sure if these are just false alarms and the OS is showing bad stats or not, but one thing I can be sure about is that this does NOT happen on the unofficial 17/01 rom compiled by Sevenrock.

Even though it's currently showing Whatsapp using about 40mb, which, considering the usage I've had since I flashed this rom a few days ago, there is no way that can be right, at least it's not Android OS that is showing high data usage like it usually happens with other roms. I have used other apps to try to pinpoint what is using the data (Onavo, My Data Manager, among others), and they all show it's Android OS.

I always use roughly the same apps, and even got to the point that I even used Droidwall/ Android Firewall to only allow certain apps, and the data usage was still extremely high.

Now the only thing different from most of the recent builds is that they use the .60 kernel, while Sevenrock's build is using .9 kernel. I didn't use the 20/02 official build long enough to see if the high data usage is gone on that rom too.

Now, I don't know if this has actually anything to do or not, but I was wondering if anyone else on either kernels who use wifi most of the time could check their data usage and see if it's unusually high, and maybe post their results here, unless some other dev could shed some light on this.
[Defy Android Development] Antiga Prime:
Even though I do not see Deskclock in the attached dump, I do use recurring alarms on a daily basis, as also scheduled tasks with Tasker, so I was wondering if you find anything out of the ordinary. I cannot post it because it's too long for the 30k character limit specified by the forum.
[Defy Android Development] vic160890:
Ok, I did play with the alarms a little and I have now up to 91 RTC_WAKEUP events. How can I apply your patch to this apk (the 4.2 clock)
[Defy Android Development] woodman:
Hi all,

On post #15693, I reported an issue I had about media managment / SD card access. I said that I will report, what I'm doing now. I though it was the famous 'ringtone' bug but apparently it's NOT.

I'm currently testing with sevenrock's 20130117 build and after 4 days and 21 hours of uptime and intensive music playback (stored on my sd card). I did NOT encounter my described issue I had with 20130220 Quarx build (it could occur with previous builds too).

The issue was that music playback suddenly stopped and it was impossible to play music again (and ringtones didn't work too). nevertheless, it was possible to access to my sd card with a file explorer app. The only way to recover music playback was to do an unmount/mount of my sd card.

With 20130220 Quarx build this issue occured twice in 2 or 3 days of uptime.
[Defy Android Development] YetAnotherForumUser:
The mere fact that the alarm table exceeds the quote length limit should set off a bell.

No, I did not find deskclock in your list. What I did find was 140 scheduled RTC_WAKEUP events for com.google.android.gsf, all scheduled to go off at the same time. Clearly it is not just com.android.deskclock which mis-handles AlarmManager. As GSF is closed source it is not as easy to fix the bugs there. On my phone I disabled the whole Google family, to be enabled on demand and disabled right afterwards. If you can't fix 'm, disable 'm...

Also... Tasker... 683 wakeups. Rather excessive.
[Defy Android Development] ktmbikerman:
I noticed this behaviour with Android OS and battery usage and I think it's related. Many apps and games don't display there own battery usage but lump it in the Adroid OS bucket, hence the high usage.

When comparing usage on stock 2.2, this is not the case.
[Defy Android Development] measel:
Still HUGE wifi and data drops

Hi all,

I had wifi problems with all versions of CM10 except one of the first if I remeber correctly.

For the sake of eliminating leftover problems i started from scratch (beginning with sbf) to install CM10 13-02-20.

At first I didn't get any data/telephony connection with my usual baseband 3.4.x but switching to unusaul 2.21 helped but I'm pretty sure it is not the best for me here in Germany.

But my wifi problem is still there. What happens is that as soon as I try to install an app either from the website or the play app wifi turns off and on again rapidly, same when I try to use the browser or any kind of up-/download activity. I went to flight mode and turnded wifi on only but that didn't help either. I recorded a log (no GSM/UMTS enabled!). Maybe someone can help in solving that problem because it really is a show stopper here! :/

Thank you.

/btw.: I got an exgreenlens-after-earpiece-replacement-nowredlens defy.
[Defy Android Development] YetAnotherForumUser:
You apply the patch by patching the source, either automatically (using the patch command) or manually. I tried the patch on the AOSP 4.2.2r1 version of DeskClock and found it did apply (with some offset and fuzz). After applying the patch you rebuild the apk, if you have the build system configured correctly you can use the [FONT="Monospace,Courier New"]mm[/FONT] command to build a single subtree. As I currently only have a 4.1.2 tree setup I can not rebuild the 4.2.2 version just yet. It is probably possible to use baksmali/smali to edit the code in the apk directly but that is a silly solution when the source is available. I PMed Quarx with a link to the patch so with a bit of luck he'll apply it in his tree and you'll be able to pull a patched DeskClock.apk from his next build. Given the way things are going on the 3.x kernel front it might soon be feasible to move to 4.2.2 altogether.
[Defy Android Development] Antiga Prime:
Under other circumstances I'd agree with you that it might be a possibility, but considering the fact that I use a firewall, and have even tested this with EVERYTHING blocked (that includes programs that run as root and the kernel), there still is no explanation as to why the OS is reporting these high levels of data usage.

---------- Post added at 12:25 PM ---------- Previous post was at 12:18 PM ----------

Regarding tasker, I use it during the day to turn wifi on every 15 minutes, leave it on for 60 seconds, then turn it back off, if/when the screen turns off. It does the same thing during the night except with a 1.5 hour interval. I haven't done the math yet to see if it actually warrants that amount of wakeups.

Are there any setbacks in disabling/freezing any/all of the GAPPS, mainly the Google Services Framework??

I usually use Titanium Backup to freeze system apps that I'm not going to use such as Apollo, DRM Protected Content, Picasa uploader, Pico TTS, Gtalk, Gmail, but I figured those other Google apps (such as GSF) were sort of important such as Google Partner Setup, Google Bookmarks, Backup Transport, Services Framework, and others.
[Defy Android Development] sepp.:
defy green lens

Hi

I do not know how many times I tried different ROMS and kernels....

but latest (at least for my green lens defy (no+)): here are my latest experiences

1. cm-10-20130216-jellyx-UNOFFICIAL-mb526.zip by yafu

After a full wipe wipe reboots and reboots after some days of useage (@office)

2. CM10-20130220-NIGHTLY-mb526.zip and applying the battery setings by marcospulido

very promising at 1st few days - but had a reboot today (@office)

3. Now I try cm-10-20130209-UNOFFICIAL-mb526.zip by sevenrock (as I remember on of his kernel builds was very stable for me - but my bookkeeping in the past was :confused: )

What never happend was any sort of problem with any of this builds was out of the office

@home I have WLAN I use (WPA2PSK) and good coverage)

@office I have WLAN I use (WPA2PSK) and intermediate coverage so the phone switches often from WLAN to GSM/WCDMA and vice versa

@other location only GSM/WCDMA

I do not know if that will be any help in debugging, but I will keep you updated (and now keeping book more accurate as in the past - I promise)

kind regards

sepp.
[Defy Android Development] YetAnotherForumUser:
Setbacks to disabling Google services depend on which of those services you use. I don't use any of their services so for me the only slight negative is that I have to enter my username/password every time I enable the services tp update or install software. Since I don't do that very often (most software is 'side-loaded' using a bunch of scripts which tailor a new installation to my purposes) this is not a big problem to me. Other than that, I see no setbacks.

I have given up on Tasker and its ilk. My day to day routine is to erratic to be caught in a few scripts so I ended up overriding whatever those 'helpful' programs did more often than not. My power-saving routines are simple but effective: manual flight mode when I go to bed, manual enable when the alarm rings (this could be automated but bedtime is also quite variable...). Manual sync, with a few daily automatic daily backups of addressbook and calender to my own caldav server. Manual email sync, I check it every now and then anyway and I don't have the time or inclination to respond when I'm doing something else. Google services on demand. Anything which does not serve a clear purpose gets disabled, removed or switched off. With 'purpose' I mean it has to serve me in some way as I consider this to be my phone.

You know, there might be a snazzy brand name in there samewhere, something like 'MYphone'...
[Defy Android Development] K3n H1mur4:
Testing here. So far, so good, phone feels snappier than before, but it may be only because it's a fresh install (even though I restored my apps+app data using Titanium Backup). Will only be able to tell about battery life in a couple days, but previously it was around crappy 5-6hours per charge, my phone charges to ~45% than goes straight to 100%, and has various drops on discharge.

What I can tell for now is about benchmarks. Here are my results:

AnTuTu (higher is better):

Previous: 3035 (801 CPU/1443 GPU/498 RAM/297 I/O); now: 3469 (895 CPU/1473 GPU/551 RAM/550 I/O)

BenchmarkPi (lower is better):

Previous: 2347ms; now: 2177ms

CF Bench (higher is better):

Previous: 2916 native/941 java/1731 overall; now: 3081 native/1026 java/1848 overall

Linpack (higher is better):

Previous: 15.962 MFLOPS; now: 16.909 MFLOPS

Quadrant (higher is better):

Previous: 1012 (1272 CPU, 1675 RAM, 624 I/O, 290 2D, 1200 3D); now: 1382 (1482 CPU, 1745 RAM, 1467I/O, 917 2D, 1297 3D)

Conclusion: the tweaks give various improvements, from barely noticeable (on FLOPS and 3D rendering) to major overhauls (like 2D rendering and I/O management). It surely is a boost and something nice to have running.

I have, though, two issues: my two main monitoring apps, SeePU (to monitor CPU and RAM usage) and Usage Timelines Free (to track CPU leaks per individual app) are unusuable. SeePU crashes all the time (works for ~10 sec and than crashes), and UTF shows only 0% of CPU usage for any app (though it shows RAM usage correctly). I think there might be something related to how CPU usage is being reported to the phone, because SeePU, in the very little time it has to run, also shows no CPU usage, and the same thing happens if I choose to show the CPU usage overlay in developer options.

If anyone knows how I can get rid of this issue, I'd be very glad. Plus, marcospulido got my thank for the extremely useful instructions.
[Defy Android Development] Antiga Prime:
In the latest roms, something changed that I guess doesn't log CPU usage per process. On the other hand, YAFU posted a patch that fixes the logging of CPU States, the same which I think was included in the 20/02 build, because BBS reports the CPU states in that build.
[Defy Android Development] sebx_g1:
Is somewhere floating flashable kernel from latest Quarx build ? I need only kernel .
[Defy Android Development] K3n H1mur4:
Is it in this thread? I couldn't find it searching here.
[Defy Android Development] woodman:
Yes, it's in this thread.

Patch explainations are here : http://xdaforums.com/showthread.php?p=38218495

This patch has been commited and it's in 20130220 Quarx build.

And YAFU posted one of his build here : http://xdaforums.com/showthread.php?p=38282947

Hope it's what you were looking for...

Sent from my Defy MB525 green lens
[Defy Android Development] eagleeyetom:
Thread cleaned. Stay on topic.
[Defy Android Development] configuration:
Seriously?

We were talking about a patch to fix battery drops in this build, and the posts just get deleted?

We were specifically discussing a patch for this ROM, not some off-topic battery discussion..

With all due respect, but that sounds pretty much on topic to me..
[Defy Android Development] ttocs99:
I used the same battd file from cm9 as you but im on mookee which is 2.3.7 and now i only have 1 battery drop from 34% to 19% and my defy battery is 2 years and 2 months but i have red x all over the white sticker on my battery so what does gha mean??

DEVICE: Motorola defy/MB525

ROM: Mookee crazy speed LITE

TWEAKS: Crossbreeder

CPU/VSEL: 300/16 700/35 1000/48
[Defy Android Development] GinoDivx:
Searched and didn't see it in the thread - my US TMO phone looses WiFi when I flash CM10.1. Meaning I can't enable it at all (doesn't even turn on). Works fine in CM10. Any ideas please?
[Defy Android Development] niksy+:
Maybe because you looked for info in the wrong thread? What you need is here - http://xdaforums.com/showthread.php?t=2013059 - and you might notice that first post says something about WiFi not being functional at the moment.

Reported both your and my post.
[Defy Android Development] nekher:
thanks so much quarkx. Working like a charm so far.
[Defy Android Development] K3n H1mur4:
Unfortunately, it's not what I was looking for. I already saw this one, haven't tried but I'll stick with the one I'm using, for some time. This build solves wrong measures in apps like BetterBatteryStats and CPU Spy about CPU states (if I remember well, BBS reports deep sleep all the time and CPUS reports top CPU clock all the time), which have been happening since 2ndboot implementation. My issue is related to CPU usage (generally and per-app), which wasn't happening in any other 2ndboot builds I tried.
[Defy Android Development] cyrusct82:
I'm suffering by the RIL bug so I have disabled my mobile data connection. For 5 days I haven't rebooted my phone. Everything was ok (no ringtone bug, no battery drain, no RIL bug, no lag) until I have enabled my mobile data connection for 30 seconds only and surprise, 1 hour after my phone lags, no touch response for some time or ghost touches, battery drain. After 8 hours from the time I had enabled data the RIL bug has appeared.

I use the latest Quarx build only deleted the rngd bin file.

One more thing: I'm disabling data connection first and after that I'm changing the baseband with another one that is working.

I'm not saying that this is a bug because the RIL bug appears in every Rom that I have tried.
[Defy Android Development] paulle:
cm10 20130307 is out

cm10 20130307 is out

and running fine so far. thanks quarx
[Defy Android Development] kur41:
I don't have any problem either mounting or accessing it through ES Explorer :)
[Defy Android Development] Clark Joseph Kent:
Members there is a Q&A thread for this ROM, as listed in the OP, please utilize it; Thank You.
[Defy Android Development] ofmb:
volkov mirror usually works & same now

http://volkov.ath.cx/quarx2k.ru/cm10-2ndboot-nightly-defy(+)/
[Defy Android Development] AlexGraves:
Hm. Any special reason for removing KSM and zRAM features from the latest build?

Sent from my CMX - MB525 - 4.1.2
[Defy Android Development] oSandmaNo:
Changelog says kernel is built from pure moto tree. So all extra features in kernel are gone.
[Defy Android Development] sunil_defy:
extra features like ?

Quarx2k.ru is down
[Defy Android Development] ktmbikerman:
Just a friendly warning... I had to delete data to get the 070313 build to get past the boot animation, for some strange reason. I recommend doing a backup before installing, just in case.

I came from sevenrock's 170113 version, which has been pretty close to perfection, time will tell how this build goes, so far (few hours) so good.
[Defy Android Development] elyashiv1994:
I have problem since cm9

When I install\update apps the phone got stuck and very slow and laggy

Someone knows how to fix it?

(did wipe data between cm9-cm10)
[Defy Android Development] cyrusct82:
Confirming that after removing rngd bin file the drain is gone. Android OS is not anymore the top consumer.
[Defy Android Development] gkkovacs:
I have installed Quarx's 20130307 after a full wipe, data restore.

Compared to sevenrock's 20130209, the new build:

- is slow and laggy, especially apps and app settings start very slow, also browser and lockscreen are lagging

- looks like I/O operations are much slower than before

- battery consumption is higher (Android OS and Mediaserver).

Did it remove the lags for you?

How can I delete that?
[Defy Android Development] Antiga Prime:
You need a file manager with root access, e.g. Root Explorer. With Root Explorer you can mount the system partition as R/W (read/write), then you navigate to /system/bin. In there you will find the "rngd" file. You can delete it, although I would recommend just renaming it to something such as "rngd.bak" or "rngd.old". Then remount your system partition to R/O (read-only) and reboot.
[Defy Android Development] cyrusct82:
System/bin/rngd with a root explorer.

No I didn't had lag. I always overclock my defy to 1200.
[Defy Android Development] eagleeyetom:
Thread cleaned. Non relevant issues like battery life or small problems should be discussed in Q&A thread.

Regards,

Tom
[Defy Android Development] xdamala:
I find it strange that this ROM contains rngd since the effect of this has been seriously debunked.

See this: http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/

I am in no way surprised that the rather strange concept of rngd is causing problems.
[Defy Android Development] Kayant:
This is why it's included --- > https://github.com/nadlabak/android...32dfbc9112547b59ae/prebuilt/etc/init.d/30rngd
[Defy Android Development] walter79:
AW: [JB] CM10 Android 4.1.2 for the Defy(+)

Did anyone else have problem with start data connection? Sometimes it works only after reboot. I replaced libril-moto-umts.so from ms2ginger and there is no problem now.
[Defy Android Development] ktmbikerman:
Sounds good, any chance of posting the file here so we can try it?
[Defy Android Development] walter79:
AW: [JB] CM10 Android 4.1.2 for the Defy(+)

Search this or cm9 thread or check my google drive (ms2ginger folder)
[Defy Android Development] ktmbikerman:
I've made a zip for the RIL file, as per Walter's suggestion. Time will tell how stable the data connection is, but so far, so good.
[Defy Android Development] cyrusct82:
I've tried the fix from Walter long time ago(2-3 months ago), but no luck.
[Defy Android Development] walter79:
AW: [JB] CM10 Android 4.1.2 for the Defy(+)

Did you changed baseband?
[Defy Android Development] cyrusct82:
Yes. Only with data disabled I don't have RIL bug.
[Defy Android Development] woodman:
Just an observation with 20130117 sevenrock's build on my green lens Defy.

Few days ago, I I've encountered an USB fail, which I think, caused a big battery drain.

My Defy was connected to a "charge only" USB cable durning few hours but suddenly the charging led tuned off, the phone has stopped charging although the cable was properly connected.... So I unplugged it and then plugged it again and the charging led turned on, I though everythink was OK, but..... Following night, my phone had an abnormal battery consuption : 2.5 or 3% / hour in airplane mode. Usually my consuption is 0.2% / hour in airplane mode.

I rebooted my phone and the night after, in aiplane mode my battery consuption was back to normal (0.2% / hour).

I think it's USB managment related but I'm not sure.

I already had this problem with other builds in the past, I don't think it related to 20130117 sevenrock's build.

I haven't tested yet but perhaps we could reproduce by playing with USB cable...

Anyone else ?

EDIT : I'm quite sure this problem could occur even with last Quarx's build (20130307) because I've never seen any fix about that on Github since last few months...
[Defy Android Development] S_xda:
Quarx on Facebook:
[Defy Android Development] hacktheheaven:
Can't take panorama shot...!!!!

Hello YAFU, I am very much satisfied with this build... using it from the day u released it.... today I just tried to take panorama shot and the mobile got restarted... after restarting tried again but with no luck... I didnt face this problem with previous builds.... Is there any work around for this problem.... Once again thnx for all the people who involved in this project...
[Defy Android Development] eagleeyetom:
Guys, just a reminder. This thread is not a place to ask questions not related with development. Please use Q&A and all threads created to give user-2-user support.
[Defy Android Development] YetAnotherForumUser:
Hmm, odd... I never had any problems with the camera in that respect. Is it the standard camera which exhibits these problems? Does it show anything in logcat before crashing? You can check that through adb, just open a remote logcat and take a panorama shot.

As with all things Android, wiping cache/data for the relevant app(s) might help. No, I don't like that method either but it does sometimes cure odd/unwanted behaviour - even though a crash clearly indicates a bug in the kernel somewhere. The JellyX kernel is rather patchy in many respects, both literally as well as figuratively. It might be that I just happened to build from a tree which had just had some dodgy patch applied which later got reverted.

Now that Quarx seems to have gone back to basics with regard to the kernel because of obscure bugs potentially triggered by any of the myriad patches which have been applied to later images I'd say there is a place for a 'quality first' updated kernel. JellyX could be used as a template to cherry-pick useful patches from. Only take those which show promise, and revert anything which does not seem to deliver. I'm rather short on time at the moment so don't count on me publishing such a kernel within a foreseeable time frame. If 3.X has not gotten up to speed when I have some more time I might have go at this.