yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] TJKV:
Hi! I have a question about the data dropping bug. I recently switched carriers, and I experience the following constantly on the new one:

1. Every hour or so mobile data stops working, even though the E or 3G/H symbol is shown. Of course the uplink/downlink arrows don't show at this point either.

2. When this happens, i turn off and turn on data. Now I lose signal and then the phone reconnects to the network.

3. I again toggle data off and on, and either immediately or in a few minutes I am connected properly again.

I don't really notice any difference with the xt_qtaguid fixes. So my question, is the above description what everyone means when they say data dropping bug?

Note: I have not been on CM since a while, I have tried the kernel with xt_qtaguid fixes only on my SB builds, which uses the SB opt_telephony branch (with a few commits from Quarx). I intend to compile one using Quarx's CM based branch when I get the time and try to rule out any absent CM stuff in the SB branch.
[Defy Android Development] hotdog125:
[MENTION=4148153]TJKV[/MENTION] The data drops you described happen to me too, but mostly in the same parts of the city everyday (since I use data daily when commuting to college). The drops happen randomly too, but rarely, since I don't keep data on for more than 1-1.5 hours at a time.

Sometimes I lose signal when I toggle data on and off, and sometimes it goes into roaming. At other times while using data, I abruptly lose signal, and I won't get back signal until I reboot.

EDIT - This problem exists for me on all ROMs except MS2Ginger, even if I use correct baseband and a fresh install.
[Defy Android Development] TJKV:
Funny, I never had problems on Vodafone. I'll pm you ;)
[Defy Android Development] Blechd0se:
Unfortunately i don't think we can do much about this in kernel space (as i already pointed that out on github).

Most likely the only place where we can actually "fix" something here is probably in the Android OS.

I really want to be proven wrong here though.

I guess in your case its just the carriers fault :(

[MENTION=4916555]okij[/MENTION]

You can add a new bug to your list; after suspend/resume the governor can't be changed (if started from interactive).

I already investigating this and know how to solve this temporarily (suspend_enabled = 0).

Furthermore i suggest you open up a new thread or something in the general section (because everytime i want to take a look

at your bug list, i have to search it first up :( ). You can also structure it a bit. Like kernel related issues, framework related issues,

confirmed/not confirmed, etc ;) I would appreciate that. Its probably good for users too, to see which bugs are really there.
[Defy Android Development] TJKV:
Yup, slugzero did say that it only "might" fix the data drops. And yes in my case it definitely is my carrier's fault, in combination with the device ril problems. A friend with a Nexus 4 on the same carrier often has problems connecting to data too, though once connected it is stable unless he loses signal legitimately.

Just fyi, quarx has linked to his post in the OP :)

But yeah, I find the bug list very useful too, I always have a look at it before I compile to keep up with the patches :)
[Defy Android Development] polarfoxx:
My camera doesnt work somehow.

It always tells me:

"Couldn't connect to camera"

17.09 build.
[Defy Android Development] slimshady76:
I jusr experienced a weird /data corruption episode. I was charging my phone, and when I tried to awake it, I saw two warnings at the notification area. I thought the RIL bug had stroked me again, but it wasn't that. I was being asked to enter my Google account again. I couldn't turn wifi on, and Google services complained again and again it couldn't recognize my password. I ended up rebooting the phone and it presented me the "Android is updating" toast before the system finished booting normally. I tried to search dmesg and logcat logs to see if anything wrong could be spotted, but all the previous records (the ones from before my reboot) were wiped. The only consequence I could see from this strange data corruption happened to my contacts. All the whatsapp ones appeared dissociated from their Google ones. I just deleted my whatsapp account and set it up again, and the contacts got synchronized in no time.

I could only spot these errors in LogCat:

--------- beginning of /dev/log/system
[COLOR="Red"]10-10 14:58:09.826 E/SchedPolicy(2276): Failed to find cpu subsys[/COLOR]
10-10 14:58:40.170 E/ActivityThread(2774): Failed to find provider info for com.google.android.partnersetup.rlzappprovider
10-10 15:03:46.912 E/ActivityThread(3871): Failed to find provider info for com.google.android.partnersetup.rlzappprovider
--------- beginning of /dev/log/main
10-10 15:24:20.882 E/cutils-trace(4653): Error opening trace file: No such file or directory (2)
10-10 15:24:28.437 E/Term (4671): onCreate
10-10 15:24:33.101 E/cutils-trace(4709): Error opening trace file: No such file or directory (2)
10-10 15:25:26.288 E/Term (4671): onCreate
10-10 15:26:27.272 E/MediaProvider(4740): /storage/sdcard0 volume ID: -1111288828
10-10 15:26:29.483 E/AudioHardwareMot(1235): Error:Unsupported key = screen_state=off
10-10 15:33:10.405 E/AudioHardwareMot(1235): Error:Unsupported key = screen_state=on
10-10 15:33:19.640 E/cutils-trace(4890): Error opening trace file: No such file or directory (2)
10-10 15:33:20.468 E/cutils-trace(4911): Error opening trace file: No such file or directory (2)
10-10 15:33:21.429 E/cutils-trace(4932): Error opening trace file: No such file or directory (2)
10-10 15:33:22.468 E/cutils-trace(4967): Error opening trace file: No such file or directory (2)

The line I highlighted in red was almost the first one logged since I made the phone reboot. However, it's working as expected.

Let me know if I could gather any other data if necessary.

---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------

This happens normally when Focal crashes. Reboot your phone and you'll get the camera back.
[Defy Android Development] Antiga Prime:
+1

Also, I usually leave my phone in airplane mode from 2:00am to 6:00am, and everytime after I disable airplane mode the phone never regains signal. If I toggle airplane mode on/off for a short period of time it regains the signal easily, but I'm pretty sure that after being in airplane mode for quite a while something happens that prevents the phone from finding a signal again.

Turning radio on/off doesn't help, only rebooting the phone works; hotbooting doesn't fix it either, so I imagine it's a problem that requires everything to be restarted at a kernel level.

I've tested this every morning for that past few weeks.
[Defy Android Development] sevenrock:
CM 10.2 is now reporting as Android 4.3.1.
[Defy Android Development] TJKV:
Fun fact: Want by to check out the Moto X phone? Head to Settings –> About Phone –> Safety Information :p

Happens on SlimBean, should happen in cm too. Probably a missing link that is redirecting, since moto has been bought by Google and all that.
[Defy Android Development] coolshahabaz:
That link was present since moto x launch....
[Defy Android Development] okij:
Yesterday I had to drive in my car for a couple of hours and all in all I had about 5-6 mobile data drops. :(

In comparison, with CM10 I easily could drive for a whole day without a single data drop. :o

So by now I'm quite convinced that SlugZero's new kernel with the xt_qtaguid fixes alone still doesn't fix the mobile data drops.

As a starting point: SlugZero wrote that the mobile data counters - which now definitely got fixed by the xt_qtaguid fixes - are essential for his SlugZero patch to work.

And since the mobile data counters now are working, I'm quite sure that there is still something amiss with the SlugZero patch itself, i.e. just something which still has to be adapted to CM10.2.

Unfortunately I'm not a programmer, so with this post I'd like to address especially [MENTION=4841764]SlugZero[/MENTION] and [MENTION=1892363]xdaid[/MENTION] (who both have contributed in writing and/or adapting the SlugZero patch and therefore are our experts for this issue) and of course also [MENTION=513620]Quarx[/MENTION] (if he got time, because he seems to be busy with other things ATM) to look for the missing fix. :cowboy: What is still wrong in the code that prevents the SlugZero patch to work properly under CM10.2? :confused:

IMHO the mobile data drops - besides the BT issues - are the most important bug to get fixed in CM10.2 because our smartphones are just too unreliable if we e.g. don't get our E-mails in time (because we didn't see that mobile data is not working) or if we use a navigation software but don't get the latest traffic infos and thus drive into the next traffic jam (which happened to me yesterday). :)

OK, I will add this bug to the list soon (I'm just not sure if I manage to do this before today's football match GER - IRL). :D

Edit: The match is over and so I added the mentioned bug as #18, as well as deleting some obsolete information from some other bugs.

As TJKV already has written, Quarx has linked to my bug list in the OP. Therefore I intend to keep it at this place, but I will update the list when new nightlies or patches come out. Besides this, I think it that this list belongs in the CM10.2 development thread itself. :)

I'm also intending to keep the order and numbering the same as it is now and just add new bugs at the end, as well as marking solved bugs as solved by striking them out, and not deleting them from the list. IMHO it is important that the numbering stays in the same order so that references to e.g. bug #6 always mean the "mobile data drops" bug in this thread, so people don't get confused.

I'm happy if the bug list helps both users and developers, because that's what I intended it to be. It's the least I can contribute to this project because I'm not a programmer myself (well, I did some C and 68000 assembly programming, but that was more than 15 years ago...) :)
[Defy Android Development] slimshady76:
Shouldn't this patch posted by [MENTION=1316716]YetAnotherForumUser[/MENTION] get rid of the bluetooth problems?

That's certainly something it's worth trying!
[Defy Android Development] sevenrock:
No, this will not fix the BT voice quality problem. The patch only fixes

BT-related build errors due to new commits made by the CM team.
[Defy Android Development] gymfreak7855:
I find it interesting that SELinux is disabled on this build. Is that for any particular reason?

Also why does the launcher not keep itself in memory? I thought Trebuchet did that by default? Or at least it did with my previous device on cyanogenmod 10 builds.
[Defy Android Development] yogesh324:
[MENTION=4916555]okij[/MENTION] can u add to ur bug list that flash videos are not working in browser such as ucbrowser etc
[Defy Android Development] Hasuris:
this isn't a bug. Google discontinued flash support with jelly bean. Html5 is supposed to take its place.
[Defy Android Development] yogesh324:
I know adobe has stopped its support from jb ROMs but my friend has HTC one x with pre installed jb and flash is working on it
[Defy Android Development] josuearisty:
Its a missing feature in the rom, adobe flash works perfect in 4.3.

I think it has to do with 720p decoder!

I think it will take too much time to get it, I think nobody is working on this bug right now.

Enviado desde mi MB520 usando Tapatalk 2
[Defy Android Development] Proverbs2:
data partition corruption bug

I've been using MarcinRN's CM10.2 build from this post, along with SlugZero's fixed kernel from here, and his wpa_supplicant patch from here. I must say, this is a winning combination: extremely smooth, fast, and reliable.

Unfortunately, I've just discovered that the data partition corruption bug is still present. This bug is also present on the latest CM10.1 build, and there are numerous reports of the bug in the CM10 thread as well.

It is easily reproducible: simply let the battery go to 0% while running a CPU-intensive app like Stability Test. (WARNING: make a TWRP backup before trying this!) Then recharge the phone and try to reboot. Occasionally after doing this experiment, the phone will boot normally. However, on most trials the phone will either hang on the boot animation, or it will reboot successfully but act as though you've done a factory reset: all your apps and settings will be gone.

I just tried this experiment again this evening, and the data partition was corrupted so badly that I wasn't even able to restore a TWRP backup. Thankfully, I was able to reformat the data partition using the "tools" option in the bootmenu, then I was able to restore the backup.

okij, could you please add this bug to the list? In my opinion this is the most serious bug with CM10.2, and I'd be grateful if it could be solved. Quarx and Blechd0se, please let me know if there is any further information I can provide or any further tests I could do to assist in solving this bug. Thanks!

-----------------------------

Update: I've been experimenting to try to capture a logcat during a data-corrupting shutdown, and so far I've drained the battery to 0% six times in a row (while Stability Test and other battery-draining apps were running) without any data corruption. I guess the bug isn't as easily reproducible as it seemed in my previous experiments. I'll keep experimenting, and hopefully I'll be able to reproduce the bug and capture logs so that we can finally solve this mystery.
[Defy Android Development] okij:
Thanks for reporting, I added it to the bug list! :)

I'm on the same combination of build and patches as you and just didn't add this bug yet, because I wasn't really sure if it is still existent in CM10.2 and because I always try to keep my battery above 30% (which still isn't an assurance because of the battery drain bug...)

[MENTION=513620]Quarx[/MENTION] and [MENTION=4855459]Blechd0se[/MENTION]: I agree with Proverbs2 that this is the most serious bug with CM10 - CM10.2 for the Defy! In combination with bug #13 (battery drain) one can easily be caught unawares by data corruption. :(
[Defy Android Development] overclockthesun:
[MENTION=513620]Quarx[/MENTION] [MENTION=4855459]Blechd0se[/MENTION] [MENTION=4841764]SlugZero[/MENTION] phone call Blacklist is not working for me. I can confirm this.
[Defy Android Development] sevenrock:
Just tested, wfm.
[Defy Android Development] okij:
"ehci_pm" is causing bug #13, battery drain due to wakelocks

Two nights ago I had the battery drain bug again and made the attached screenshots. The first two were made before a manual reboot, the second two about 6 1/2 hours after the reboot.

On the first two screenshots you see that the battery was draining at about 6% per hour, my Defy+ didn't get any deepsleep, and that this was caused by a kernel process called "ehci_pm", which triggered almost 50000 wakelocks in 5 1/2 hours! :eek:

On the second two screenshots you see that after the reboot everything was back to normal, so the battery consumption was under 1% per hour, my Defy+ got 96% of deepsleep and "ehci_pm" triggered just 780 wakelocks in 6 1/2 hours.

As an additional information: Before I made the manual reboot, I first tried a Hot boot, but this didn't stop the wakelocks (which is quite logic since "ehci_pm" is part of the kernel).

Because of this IMHO it's safe to say that "ehci_pm" is causing bug #13, battery drain due to wakelocks. :)

[MENTION=513620]Quarx[/MENTION]: In my post from 2013-10-04 I suspected your Wifi driver as the cause for battery drain, but obvoiusly I was wrong (the cause must have been "ehci_pm" then too, but I didn't make a screenshot of the kernel wakelocks that day). I'm sorry for this! :o

I my post from 2013-09-24, where I first wrote about the battery drain, you can see in the fifth screenshot that "ehci_pm" also caused a whopping lot of wakelocks, which supports my thesis.

Now what is "ehci_pm"? From here I get that it must be part of the Enhanced Host Controller Interface (EHCI), so it must have to do with the USB driver. From this post I get that the 2G/3G-modem is internally connected as USB peripheral, so also the modem driver might be the real culprit for the wakelocks.

[MENTION=513620]Quarx[/MENTION] and [MENTION=4855459]Blechd0se[/MENTION]: With this new information, could you please further investigate this issue? It would be great if you could soon fix the battery drain bug in the kernel, because (especially in conjunction with the data partition corruption bug) it is quite dangerous to use our Defy's on low battery! :fingers-crossed:
[Defy Android Development] major9:
Works fine on Quarx's 17th build.
[Defy Android Development] overclockthesun:
Hmm, thats strange, it just does not work on my phone. Guess I am going to have to try a full sbf flash and have a go at it again. some ting wong:confused:
[Defy Android Development] bigmoew:
Hey guys, new to the Defy community so be gentle ;)

How do I get into fastboot? adb reboot-bootloader sends the phone to the boot menu. I'd like to flash the zimage of Slugzero's kernel
[Defy Android Development] Lord_Flaya:
http://xdaforums.com/showthread.php?t=1216982. <--- great place to start :)
[Defy Android Development] gymfreak7855:
Would I be able to get my hands on the source for this rom? May I have a URL???
[Defy Android Development] TJKV:
Welcome!

Locked bootloader, no fastboot here. Our device first boots up using the stock kernel in the /boot partition, then at one point in the boot it is cleverly replaced by the custom kernel which is located in /system/bootmenu/2nd-boot/zimage.

See the thread that [MENTION=4669272]Lord_Flaya[/MENTION] linked, read everything before proceeding.

https://github.com/Quarx2k/android/tree/cm-10.2
[Defy Android Development] arod81:
Deep Sleep bug

Hi,

this is my first post in this thread, so please be patient..with this ROM (which for the rest is wonderful, I have to say), I have just one important bug..every 2 or 3 days the phone doesn't wake up from sleep, the only solution is to pull battery and restart. I didn't find this bug in the list of known bugs; I tried to search in the thread, but to no avail..is it happening only to me? Do you have some hints to help me?

thanks to everyone..
[Defy Android Development] atulclassic:
do not drain battery below 20%(safeside)..also reboot your device once every 2 days..there are memory leaks which are still to be fixed.
[Defy Android Development] Antiga Prime:
No it's not just you; I get that a lot also. IMO it should be on the bug list, but I can't seem to reproduce this bug at will, so it's hard to debug.

Do you use apps such as Green Power or Deep Sleep Battery Saver, or alike?
[Defy Android Development] arod81:
Yes, I agree with you that it's really difficult to reproduce and debug.. ;)

I use only Go Power Master as a battery saver..do you think that it's better to uninstall it?
[Defy Android Development] TJKV:
That non waking up happens here whenever system_server hogs too much memory and not enough is left for foreground apps.
[Defy Android Development] okij:
[MENTION=4148153]TJKV[/MENTION], [MENTION=5336733]arod81[/MENTION], [MENTION=5134017]atulclassic[/MENTION] and also [MENTION=4855459]Blechd0se[/MENTION] for information:

I just added a note about the device not waking up from deep sleep to bug #4, because it's related to the "memory leak after some days" bug. I wrote "for some users" since I personally didn't have this problem with CM10.2 yet, even after an uptime of 14+ days. For me, this bug was more common under CM10 and CM10.1.
[Defy Android Development] atulclassic:
[MENTION=4916555]okij[/MENTION]..thanks.

Can you please confirm your devide configuration (what all apps you installed by which you are able to have a uptime of 14+ days)

Thanks again in advance
[Defy Android Development] okij:
As I wrote under #4 of the bug list, I had an uptime of 14+ days with Quarx's 08-01 nightly, running on my Defy+.

Currently I'm on MarcinRN's unofficial nighty with SlugZero's fixed kernel and fixed version of the wpa_supplicant .

With this combination I have to restart my device about every 5-7 days because bug #13 (battery drain due to wakelocks) tends to occur after 5+ days. I didn't have this problem when running Quarx's 08-01 nightly for 14+ days, probably because I was on holiday then and so didn't often switch between Wifi and G2/G3 (as a guess: if this battery drain due to wakelocks is related to the modem, maybe switching G2/G3 off an on triggers this bug after a while?) :confused:

I have 100+ apps installed, but that IMHO that doesn't matter as long as those apps that try to lock themselves in memory are greenified. :)

The apps that usually stay in memory (and are not greenified) on my Defy+ are:

Nova Launcher

K-9 Mail

MailListWidget for K-9

Hacker's Keyboard

Business Calendar Free

TrustGo Antivirus & Mobile Security

Wi-Fi Matic

Greenify

SetVsel

My Vsel-Settings are quite moderate (300@25, 600@35, 900@50 and 1100@60). Governor is Interactive (of course), I/O scheduler is Deadline. zRam, Allow purging of assets and KSM are all disabled (because after trying those and also Swap for a while, I got to the conclusion that my Defy+ runs better ATM without the use of virtual memory).

I have HWA disabled for everything but Google Maps, YouTube (because they need them to work), Nova Launcher and System-UI.

So that's my device configuration. :)
[Defy Android Development] Blechd0se:
#4; Yes, there are still some memory leaks, but it got much better. I fixed quite a bunch. Normally i have to use kmemleak detector and

use the defy just as normal. This has two disadvantages however; first its quite time intensive (sometimes it needs up to 20 minutes to see

some valid detections). Second, these results are not transferable to any other user, which is a huge disadvantage!

So i you really want to help here, compile the kernel with kmemleak and debugfs enabled, flash it and try to reproduce the problem.

Then send me the logs. :)

About system_server; If google or cm derped here (i guess cm...), i can't do anything.

#13: I don't need screenshots, i trust you anyway ;)

What i really need is a log (dmesg/kmsg) if you encounter this problem again. I already searched up the (probably) relevant code in the kernel here.

In many (many many many!) cases wakelocks are not directly executed by the kernel, they are somehow bad by design and its the reason why they aren't in

any upstream kernel yet. The posted code is pretty old and if we look at the TODO list at the beginning its quite scary motorola build something like this.

Many apps use wakelocks for whatever reason to keep the device awake. In this case you are probably right, its most likely a kernel bug, but in other cases

its just because of a bad coded app.

Btw. the same driver prevents us from using the 3.0 kernel properly. Just some knowledge i wanted to share ;)

If you can, obtain logs while its shutting down or something like that. Could be helpful :)

I am still busy with the app, but fixed #18 temporarily with a workaround.
[Defy Android Development] TJKV:
I had been meaning to ask you how to enable them :p
[Defy Android Development] Blechd0se:
I just revere to myself; here

Furthermore, if enabled and set up correctly you can see the output with cat /sys/kernel/debug/kmemleak

as far as i remember. Always a good way to look something like this up is the official kernel documentation :)