yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] viruss:
Just to make sure - are you using the latest JellyX from 30/12/2012 or some self-compiled version? If so, would you mind sharing it for us to try?
[Defy Android Development] YetAnotherForumUser:
The lag caused by the potentially runaway mediaserver process would have been caused by memory starvation - I seem to remember it showed '0% cpu'. As I have not seen any problems with mediaserver (other than it barfing on 'corrupt' files every now and then, something which is not kernel-related but simply a bug in mediaserver itself) I can not speak from experience, but I'd wager to say the problems observed were not directly related to the mediaserver process but rather another symptom of the 'ringtone' bug.

As to the presence or absence of abnormal lag in the UI I can thus far state that I have not seen any change in UI response in the 52+ hours the phone has been running. Had I been running the kernel which is part of the most recent (20130110) version on Quarx' site the UI would have started to lag somewhere between 36-42 hours of uptime. This would have been noticeable on unlocking the phone as it would take a second or so between pressing the power button and the appearance of the unlock screen. The (stock) web browser is another good benchmark for the UI lag as it simply stops responding for longer periods of time (showing the '... has stopped responding, Wait|Kill' popup) after the mentioned uptime. Thus far none of these problems have become apparent on my phone. As it is possible the problems are just delayed instead of absent I'll continue the experiment for a few days. If the phone is still running fine a few days from now I'll consider this problem 'solved' in my current configuration. In that case the hunt for the cause can begin in earnest :)
[Defy Android Development] blairpoodle:
Great news. I look forward to it being my daily driver. I have still got a problem with the BBC iPlayer app crashing. I know this is nowhere near as serious as the ringtone bug but it's literally the only thing that doesn't work on the defy. How can I help to squash this bug?
[Defy Android Development] YetAnotherForumUser:
I'm running a kernel I compiled from the Blechd0se repository as it was at midnight on the 10th of January (45b0a007ac). If things still look good in a few days I'll post the kernel and related bits - the tiwlan_drv.ko module from a 'normal' Quarx build needs to be replaced as it contains references to the SLAB allocator while I used SLUB (other modules work fine). I don't want to post yet another half-baked kernel without some more testing. Even better would be to find the culprit so Quarx' kernel can be fixed without adding all the other changes found in JellyX.

---------- Post added at 12:39 AM ---------- Previous post was at 12:34 AM ----------

To help fix that bug you can a) fix it :^), alternatively you could try to find out what causes those crashes using the normal mechanisms (logcat, dmesg, tombstones, strace, etc) and post the results here. As that specific app only works for those who are blessed by the BBC I can not test it - I live in Sweden, the Vikings departed Jórvik before the BBC became an issue so we're out of the loop...
[Defy Android Development] blairpoodle:
Half tempted to say lucky you :) Sweden, BBC 4 is quite obsessed with all things Scandinavian (Wallander, Bron/Broen, The Killing and Borden are all big hits here)

I will post all of the above tomorrow and thanks for the response.
[Defy Android Development] okij:
As I wrote today, I'm currently testing sevenrock's kernel of 2012-11-09.

Unfortunately, I had a spontaneous reboot today after about just 4 h uptime (which I never had with the more recent Quarx builds, where only the 'ringtone bug' after 30+ h was the problem.)

Therefore I would be happy if you could share your build of Blechd0se's kernel, along with your settings like scheduler etc. If I experience another reboot, I would like to install your build to try if it's more stable. :)
[Defy Android Development] fryta22:
Does anyone have a ringtone problem. I have a ringtone in incomming call problem.
[Defy Android Development] K3n H1mur4:
I've been warning about this for over 2 months, now. The cpu leak issues related to media are the following: first, DRM-protected content storage. If one does no have any DRM'd content, it can simply delete the DRM-blablabla apk on /system/app, or disable it in the apps settings. After this, Download Manager will cause CPU leaks. It can be solved temporarily by force-closing the service with a task manager. It'll return after some time (given in miliseconds in the logcat right after closing it), or if thriggered (usually by downloading stuff via Play Store or attachments on the GMail app). I use Usage Timelines Free and SeePU to monitor it (the latter shows CPU and RAM usage on statusbar, so I can check 100% CPU use with phone idle; and the first is a nice task killer which can sort apps per usage - set it to show system apps and you're good to go - it can also replace the CPU monitoring of SeePU, but it takes a lot of processor time to do so). I strongly recommend you guys to investigate upon this, since only Usage Timelines will show the specific processes eating the CPU, Android's list on battery settings will only show that they're all related to the media process.

You could AT LEAST read the same page you posted on, since you're too lazy to use the search function. Ringtone issues are widely known and discussed already. Changing VM heap size seems to solve for some.
[Defy Android Development] sevenrock:
Yes, for details check the last 20 pages of this thread :)
[Defy Android Development] Gianluca85:
For a clean install, I do only wipe data and wipe cache? or i format internale and sd storage? thanks
[Defy Android Development] hDusan:
2013.01.07 version working on MB525 and where work download link ? :)
[Defy Android Development] Fight4Music:
DL's are over here:

http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/

Next time please look at op.

Gesendet von meinem MB526 mit Tapatalk 2
[Defy Android Development] hDusan:
good but I did not understand anything
[Defy Android Development] woodman:
Hi,

OP is here

You could read FAQ
[Defy Android Development] markos807:
Hi,

is there any way that I can fix my broken flashlight? I am using latest 10.1 build, but flashlight just flashes with, ex. 20% of full power, like it doesnt work. What I have to do?
[Defy Android Development] kur41:
Maybe the problem is that you asked in a DEVELOMENT thread without "understand anything"...
[Defy Android Development] rino-artemis:
The behavior of my Phone described by me in the post above, is not solved at all for me.

I tried out several combinations of roms and kernels. All the same.

Only switching of WIFI solve the problem.

The phone always lose connection after some time, then I roam around on our campus here with several wlan hotspots (I think Cisco Access-points).

So if there any other thing I can do to solve this behavior, so please let me know.

Bests

Rino
[Defy Android Development] vic160890:
My phone has an uptime of over 2 days and started exhibiting the ringtone bug just today.. I shall help you when I get home from work. I'll contact privately later this evening and if you still require logs or anything I will help.
[Defy Android Development] xlyz:
Need android.permission.dump

How can I set it?
[Defy Android Development] 57op:
I guess you're using terminal emulator app.

Try to run the command through adb (adb shell).

If you want to store the output in your sdcard, type:

dumpsys meminfo > /sdcard/dump.txt
[Defy Android Development] Krokogator:
Just use "su" command, then write "dumpsys meminfo", if on terminal emulator.apk :p
[Defy Android Development] drunk_ryder24:
feedback

for my defy greenlense(2.6.32.9-jellybean android@android #1)works like a charm,no random reboots,external .m4a ringtone set !00% working with no reboots,the 10.01.2013 build runs smooth
[Defy Android Development] bharathexe:
I'm able to find the DrmProvider.apk in /system/app. But I would prefer disabling DRM in settings rather than deleting the DrmProvider.apk

So can u please tell how to disable DRM? which app settings do u mean?
[Defy Android Development] paulle:
i had the ringtone bug this morning, but i rebooted the phone (for getting ringtones working for a while). next time i've the bug, i'll run the command. (ringtone bug after 3 days uptime).
[Defy Android Development] vic160890:
'm on the Phone șo just a quick upload of the dmped meminfo. I have something interesting on catlog.. But i' ll send that from home
[Defy Android Development] Benoe:
Now I have a serious slowdown on the phone, altough the uptime is not so long (8hrs). Attached all kind of outputs.
[Defy Android Development] fryta22:
Hi friends. Form personal the best build is 9.11. Is fast, stable, only battery could be live longer. Regards.

Wysłane z mojego MB526 za pomocą Tapatalk 2
[Defy Android Development] Mario.D:
Yes you can replace it, it's a hardware fault caused by a bad/wrong rom.

Skickat från min MB526 via Tapatalk 2
[Defy Android Development] vic160890:
So, as I have arrived home, and have promised a log cat of something.. here goes:

I was :

-listening to music;

-just switched on 3G and data to check this thread;

-started opera (page was loading)

when the screen went black.. I noticed a popup but didn't have the time to even guess what was written. I tried to use the power button to wake it up.. nothing happened.. tried some more.. than.. the buttons lit up but screen was still black. buttons off again.. I decided to wait.. after some 10-15 seconds I tried again.. although music was still playing, I could change the volume.. so the device was working.. I unplugged the headset and tried again and the screen lit up.. and it worked.. I went for catlog to save the log but it couldn't save the file.. (this is in the catlog too). I unmounted and re-mounted the sdcard and then it finally saved the logcat. phone is still on.. i did not reboot because i wanted to keep the ringtone bug ongoing to help research the causes.

I have attached the logcat.
[Defy Android Development] markos807:
No software fixes? :(
[Defy Android Development] bone101:
Yes , it is possible to fix if it is burned ?

You can replace it with a new one

MB525 red lense
[Defy Android Development] sevenrock:
During remount, the filesystem check reported errors, check your log.
[Defy Android Development] YetAnotherForumUser:
If/when this happens again it would be interesting to know what the following command sequence produces:

procrank=/tmp/procrank.$(date +%ss);toprank=$(procrank |tee $procrank|head -2|tail -1|awk '{print $1}');cat $procrank;procmem $toprank;rm $procrank

Output should look like this:

...
PID Vss Rss Pss Uss cmdline
2058 70992K 70872K 39013K 31780K com.cyanogenmod.settings.device.hwa
1811 65024K 64940K 32976K 26104K android.process.acore
1277 34140K 34140K 23969K 17292K /system/bin/surfaceflinger
1767 53648K 53588K 23609K 18524K com.teslacoilsw.launcher
1550 51640K 51616K 22775K 17820K system_server
....
.... (many lines deleted for brevity)
....
1271 328K 328K 112K 108K /system/bin/servicemanager
1289 108K 108K 104K 104K /system/bin/akmd2
------ ------ ------
274811K 214208K TOTAL

RAM: 488400K total, 22852K free, 72944K buffers, 136772K cached, 240K shmem, 27512K slab
Vss Rss Pss Uss ShCl ShDi PrCl PrDi Name
------- ------- ------- ------- ------- ------- ------- -------
8K 8K 0K 0K 8K 0K 0K 0K /system/bin/app_process
4K 4K 0K 0K 4K 0K 0K 0K /system/bin/app_process
....
.... (many lines deleted for brevity)
....
24K 24K 16K 16K 8K 0K 16K 0K [stack]
------- ------- ------- ------- ------- ------- ------- -------
70992K 70872K 39013K 31780K 39064K 28K 31900K 0K TOTAL

This lists the processes on the phone, ordered by 'proportional' size. It takes the top memory consumer (in my case the HWA helper application which I usually remove for exactly that reason) and gives a more detailed process memory dump.

As to the 'why' of this request this is yet another way to see where the memory goes. Your phone has run out of memory *and* swap space while the PSS of all things Android is only ~140 MB, an amount which should not pose a problem (on my phone it is ca. 226 MB without any slowdowns).
[Defy Android Development] fryta22:
I think, perfect rom will be stable and fast from 9.11 build and longer battery life from 10.01.2013.

Bay the way very thanks for quark for your job.

Regards.
[Defy Android Development] YetAnotherForumUser:
Hm, nothing really obvious there - or am I missing something? I'll wait for that logcat dump. You could try that command sequence I posted...

procrank=/tmp/procrank.$(date +%ss);toprank=$(procrank |tee $procrank|head -2|tail -1|awk '{print $1}');cat $procrank;procmem $toprank;rm $procrank

...the next time the phone stalls, it might shed some more light on where the memory went.
[Defy Android Development] bavo_t:
Thank you YetAnotherForumUser, and others that have been providing useful tips/commands/logs like this.

It's been a real pleasure to follow this thread the last few days, with the exceptions of a few post it looks like this is finally turning into a real development tread.

I'm currently on 2010-01-10 and so far it's the definitely best JB rom I've seen almost no issues (I actually haven't seen any yet), no lag whatsoever.

I have a Defy+, but i also have a Defy green lens lying around, but it has a broken power button, i'm going to try to fix it somehow, as soon as i find a way to boot it again I can do some testing to see whether some issue's are model dependent.
[Defy Android Development] blairpoodle:
BBC IPlayer

If this helps in any way. Please find attached the output of strace -p (BBC iPlayer app pid) -o trace and dmesg
[Defy Android Development] vic160890:
I'm quite new to this, and even colored catlog isn't very illuminating. could you please advise me in this situation ? (Should a backup and format of SD make things right ?)

Actually I did not notice how long the log was I was only going to save a part of it but with the phone freezing and me getting agitated, i just clicked save. The problem starts around 17:54 (time) I'm curious why it wouldn't light up the display until I disconnected the headset..
[Defy Android Development] sevenrock:
On 17:56 the first SD card error shows up in your log:

01-14 17:56:05.556 E/battery_widget_monitor(5661): Failed to write battery history: /mnt/sdcard/battery_history.txt: open failed: EROFS (Read-only file system)

Later dalvik could not create new files

01-14 17:59:35.056 I/dalvikvm(7216): Jit: resizing JitTable from 4096 to 8192
01-14 17:59:35.056 E/j (7216): couldn't create new file
01-14 17:59:35.056 E/j (7216): java.io.IOException: open failed: EROFS (Read-only file system)

On 18:02 the filesystem check of your SD card was checked:

01-14 18:02:07.525 I//system/bin/fsck_msdos(1154): ** /dev/block/vold/179:1
01-14 18:02:07.525 I//system/bin/fsck_msdos(1154): ** Phase 1 - Read FAT (compare skipped)
[...]
01-14 18:02:23.525 I//system/bin/fsck_msdos(1154): 6534 files, 4064584 free (1016146 clusters)

Check your current logs for further SD card errors, but I think fsck_msdos should have done its work,

no need to format your SD card afaics.
[Defy Android Development] vic160890:
Thanks. It's a lot more clear now.

Problem is that it's not the first time it happened. It usually comes along with the ringtone bug ( i'm not saying they are related ).Now it's just the first time I caught it on log (extra free time). It's not always so abusive. sometimes i just notice apps can't write on sd. and I have to remount for them to work again.
[Defy Android Development] ofmb:
WTF??!!

how many of you have the folder .android_secure with absolutely no files in it and without any permissions marked? (via root explorer)
[Defy Android Development] walter79:
Try to plug usb cable. remove battery. Put battery back. Phone should boot.
[Defy Android Development] YetAnotherForumUser:
Apart from those media-related errors sevensrock already commented on there are a few more clues to be had in that logcat:

$ grep 'frag case' /tmp/logcat
01-14 17:59:18.556 I/dalvikvm-heap(7216): Grow heap (frag case) to 13.059MB for 14416-byte allocation
01-14 17:59:54.056 I/dalvikvm-heap(7216): Grow heap (frag case) to 13.943MB for 108816-byte allocation
01-14 18:01:07.025 I/dalvikvm-heap(7216): Grow heap (frag case) to 13.802MB for 157456-byte allocation
01-14 18:03:30.525 I/dalvikvm-heap(7216): Grow heap (frag case) to 14.328MB for 157456-byte allocation

$ grep pid=7216 /tmp/logcat
01-14 17:57:39.556 I/ActivityManager(1434): Start proc com.nolanlawson.logcat for activity com.nolanlawson.logcat/.LogcatActivity: pid=7216 uid=10087 gids={1015, 1028}

While in itself this is just a sign of the virtual machine doing its work trying to grab the required amount of memory it does point at memory fragmentation. There are other indicators of memory and cpu pressure:

$ grep 'E/.*Load:' /tmp/logcat|sort
01-14 17:57:23.056 E/ActivityManager(1434): Load: 8.87 / 3.93 / 2.38
01-14 17:57:26.056 E/ActivityManager(1434): Load: 8.87 / 3.93 / 2.38

Look at that system load: 8.87 in the last 60 seconds, 3.93 in the last 5 minutes, 2.38 in the last 15 minutes. For comparison here is the system load on my phone while I'm browsing the web in a rather hurried way (scroll, click, scroll, click, rinse, repeat):

$ busybox top -n 1|grep 'Load average'
Load average: 0.84 0.27 0.09 1/592 7323

The high system load on your phone might be caused by the file system check and/or mediaserver scan running as a result of your sdcard shuffle. It could also be caused by another process, this can not be deduced from the log. You could try to execute that command sequence (the one with procrank & procmem) I posted a few messages back and show us the results.

As an aside may I point out you don't need to use an app to get logging info out of an Android device? Just use adb and redirect the output to a file:

$ adb shell logcat -d > /tmp/logcat

This works on Linux, on Windows you'll want to adjust the paths to adb and the dump file.
[Defy Android Development] polarfoxx:
I downgraded back to StockRom.

It's really good work of Quarx but I got huge battery drops with all Roms I tried so far and even tried different kernels.

Gonna rock if you can get it to work with StockRom Battery life.

Till then I'm back to Android 2
[Defy Android Development] YetAnotherForumUser:
For testing purposes only: JellyX kernel without 'ringtone bug' (?)

For those of you who feel the urge to experiment I have a fun project: test this kernel I compiled based on JellyX to see whether it solves the 'ringtone bug' for you.

The kernel is attached to this post in a CWM-flashable zip. That zip contains the following payload:

$ unzip -l jellyx-20130111-signed.zip |grep system
3176420 2013-01-15 00:18 system/bootmenu/2nd-boot/zImage
993804 2013-01-15 00:20 system/lib/modules/tiwlan_drv.ko

I had to include the tiwlan_drv.ko module as the version in Quarx' distribution contains references to the SLAB allocator while I used the SLUB allocator. All the other kernel modules seem to work without problems (which is not surprising as this is basically the same kernel version with a bunch of patches applied) so I did not include them.

Please be aware that this zip will delete the original (Quarx) kernel image and tiwlan_drv.ko module. If you want to go back to those versions you'll have to either re-install Quarx' distribution or extract those files and replace them manually. If this scares you, you're better off waiting for the 'ringtone bug' to be fixed in Quarx' distribution.

For those of you who wish to compile their own version of this kernel I included the .config file in another attachment (with a .txt extension to get around those silly file 'type' restrictions enforced by this BB). You'll want to clone Blechd0se's repo to be able to compile a working kernel. Read through the last few days of postings on this thread to know a) where to find this repo and b) which commit to reset your branch to.
[Defy Android Development] theclaytons:
Tried this and got black screen on boot. Just after red LED and before boot animation would usually appear. Defy red lense with latest Quarx.
[Defy Android Development] YetAnotherForumUser:
Reboot and try again (boot, not install)? I usually get that black screen every time I install a new (Quarx) version, followed by an automatic reboot, followed by a normal boot.

Of course I'm using an MB526 aka Defy+.

Another thing which can give problems is if your overclock.conf contains something which this kernel does not like. I'm using the 'default' interactive governor with some tried and tested vsel/speed combinations. I intentionally did not add overclock.conf to the zip as I assume most people have their own preferences in this respect. That might lead to problems if those preferences don't mesh with this kernel though...
[Defy Android Development] okij:
Thanks for sharing! :)

I'll now give it a try since sevenrock's build of CM10-20121109's kernel unfortunately didn't solve the problems on my Defy+. With this kernel I experienced:

1. A spontaneous reboot after just 4 hours.

2. An uptime of 10 hours before the ringtone bug appeared for the first time this morning.

3. After reboot an uptime of another 16 hours before the ringtone bug appeared for the second time later this evening.

The last ringtone bugs lead on my Defy+ to a state that prevented incoming calls at all, stopped the haptic feedback from working, cut wifi functionality and even prevented using the software terminal (i.e. no $ promt on the screen and thus no input possible) so that I couldn't even write a dumpsys meminfo as you asked for. :(

So now I'm setting my hopes in your build of the JellyX kernel... :fingers-crossed:
[Defy Android Development] theclaytons:
Ok. Did that. Confirmed new kernel installed and straight after reboot phone "seems" snappier. Had a few issues with google account being wiped after new kernel being installed twice. Probably not related though?

Time will tell if phone stays snappy or if ringtone bug appears.

Thanks for sharing.
[Defy Android Development] okij:
Sorry, but I just experienced the same as theclaytons. :(

It seems like the red LED stayed on for a bit longer and the soft key LEDs didn't light up as they usually do. Then the screen went black and stayed like this for >2 minutes before I took the battery out. I checked it a second time with the same result. I always have overclock.conf at Quark's default setting since I use SetVsel to set the voltages a bit lower after booting up.

Is it possible that there are some other files necessary with your kernel, as it was in sevenrock's build too? :confused:

EDIT 1:

I just read theclayton's second post and will give it a second try.

One question to theclayton: Did you do a full wipe the second time? I really don't want to do a data wipe because I need my Defy+ fully working...

EDIT 2:

After flashing CM10-20130110-NIGHTLY and jellyx-20130111-signed both once more (like I already did the first time), I got to the CM logo at the first bootup. After the usual self-reboot while booting, it resulted again in a black screen after the red LED went out.

Then I flashed jellyx-20130111-signed again and the reboot after this was without problems.

Even though this all was a bit strange, I'm now able to test the jellyx-20130111-signed kernel and I'll report back if it stays stable.

Thanks again! :)
[Defy Android Development] theclaytons:
Try install again. Works for me second time.
[Defy Android Development] okij:
What exactly did you do the second time?

EDIT: Works now, see above.
[Defy Android Development] theclaytons:
What memory settings do you have for zram and ksm? Seems a lot better with both disabled.
[Defy Android Development] K3n H1mur4:
Settings > Apps > All > look for DRM Provider > select it > select the "disable" button. Don't forget to use Usage Timelines Free to check "Download Manager" CPU leaks after doing this. As I said before, this isn't a solution, though, but a workaroung 'til someone finds out the real issue and solves it. I'm having this situation since CM9, so it's not JB related.