Related
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF
Extreme kudos and awesomeness and gratitude to jcsullins and all the folks involved with developing CM10/Android for the TP. Thank you.
I had been watching the forums to figure out a good time to "jump in" and yesterday I took the moments to install CM10.1 (4/18/13) on my TP. I was amazed at how seamless and flawless the installation was. It seemed it took less time to do the install than it did to download CM10 (download was ~100kb (kB?)/s). CM10 came up running without any problems.
Of course, it wasn't without some issues After confirming CM10 was functional (along w/Wi-Fi, etc.) I installed gapps and that's where the problems began. I first tried gapps-jb-20130409-signed (which did not get installed with CM10). After it was installed, I lost the keyboard app (kept getting messages about the keyboard no longer working). I tried suggestions of default/reset and clearing both caches. Didn't fix the problem. Wasn't sure how to uninstall gapps, so I did a complete CM10 reinstall and tried gapps-jb-20130409-signed again. Still no good. I thought maybe it was a compatibility issue (I could never be absolutely clear which gapps would work with which CM version). So, I went with gapps-jb-20130301-signed. Same problems. I then came across gapps-jb-4.2-Gapps-And-Extras-Signed (I changed the name to be sure it would work with ClockWorksMod) mentioned in a posting. This seemed to do the trick. Keyboard remains fully functional.
I'm curious if there are any log files kept on the TP from the install. Each time I installed CM10, I noticed in the messages rolling up the screen that certain directories couldn't be found. And I think a few of them were related to gapps installation. I'd be interested to see what that was about.
The only problem I've noticed in the short time I've played with it is that the Wi-Fi went inactive (and not temporarily). I went into settings and tried to turn it off and then back on. Once I turned it off, I wasn't allowed to turn it on. There are prob'ly 1/2 a dozen or more Wi-Fi sites nearby, but the TP couldn't see any of them. I ended up doing a power down/reboot and that brought back Wi-Fi.
Anyway, I am very pleased with the new OS. And happy to be independent from WebOS, since its future is unknown.
Cheers....Steph
A two years old device with the latest Android, yeah, its definitively a great work!
Log files are saved in the back up and/or in /cache/recovery/last_log . Also do you have the "Keep Wi-Fi on during sleep" setting set to Never? That might be why your wifi is having issues, because I had the same issue when mine was set to Never. Now I usually keep mine set to Always and it hasn't had that issue and doesnt seem to use the battery too much.
Surge1223
Im curious, were you testing CM10 or CM10.1?
Go and read a guide again, you're installing the wrong gapps. The ones it specifically says not to use.
You need this one:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Hello everybody,
I have been waiting a bit until posting this issue to see if future nightly builds of Cyanogenmod solved the problem but to no avail, I already posted on their forums but so far no one has been able to figure out the problem... not that they tried.
I'm using an international Galaxy note (n7000) and these issues have been popping up since last month.
The main problem comes up when using the android keyboard and listening to music at the same time, the phone just seem to struggle a lot, music begins to stutter and usually the phone just becomes unresponsive and I have to force reboot the whole thing. A pain in the neck. Lately the phone just hangs whenever it feels like it and I have to reboot it, it usually happens twice a day.
Sometimes you're able to come back to normal after a few minutes but rarely.
The problem was even worse while using SwiftKey, now I'm back to just using the normal android keyboard but still the issue pops up almost every day. I already did a wipe data/factory reset, no avail.
Any thoughts on this?
Thank you in advance.
Post a log. Which ROM where you on before flashing CM.
sounds like a memory leak, try newer versions or trace down the issue. Check which apps consume most and cpu when it occurs.
Check as previous poster said logfiles
Sent from my GT-N7000 using Tapatalk 2
CM 10.1.3-N7000 bluetooth issues
Hello,
I'm using CM 10.1.3-N7000 and I really love it, but I'm forced to use another ROM, just because of the carkit compatibility via bluetooth. The sound is extremely bad.
Does anyone know if it's fixed in later versions or earlier versions?
Are there other ROM's, ot based on CM without the bluetooth problem?
I'm really searching since two days now to find a bluetoothfix, but can't find it.
Pairing and so on is no problem at all, it's just the soundquality that is terrible. (it was not the case with my stockROM)
thank you for giving me some advice!
I switched to Omnirom and I think the problem has been solved now.
If I see that the same problem is back as it was with CM, I will come back to that.
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
This is the only and the known problem with droid4 on cm10.1 cm10.2 but I have a very good experience with the latest nightlies using buildprop editor to change only the telephony.lteOnCdmaDevice=0. Don't use the patch and se if it helps for you.
Sent from my XT894 using xda app-developers app
I have that property "zeroed" already, do you mean I should try reverting Tobby's mod?
Try the latest nightlies, there are some changes regarding to apns, it's updatable from cm10.1 and make only that change don't apply any patch.
Sent from my XT894 using xda app-developers app
Joril said:
Hi everyone!
I have a strange problem with my Droid 4: sometimes it stops playing sounds (or music, or ringtones), and I can't figure out if there's something in particular that triggers this. Anyway the only fix I could find is rebooting the phone.
There's another problem though: when this happens, if I try to use the phone app or the contacts app, the app itself hangs before I can do anything. If I kill the hanged app and retry a few times, the phone reboots itself.
Any idea on what could be causing this? What could I try to diagnose the problem?
I'm using a Verizon-branded Droid 4 with CM10.1.3, but I had the problem on 10.1.2 too. If it's relevant, I had to install "Tobby's mod" to enable GSM (I'm in Europe)
Many thanks for your attention!
Click to expand...
Click to collapse
I've seen this on stock, and I think it's related to bluetooth - perhaps it's not releasing the audio properly after a device disconnects?
There's an app in the Play Store called "Earpiece", and I can use that to bring the audio back when that happens by switching it on, and then switching it off again.
HTH.
Steve.
I don't use bluetooth at all, but I'll try Earpiece, thanks
the problem is that it will crash before you realize and you will loose the next call, so I don't think it is of some use.
I tried latest nightly and safestrap 3.65 (from 3.63) and I had lots of black screens, several on one day and then I realize that before, I had it working stable on cm10.1 when I found out that noop was the problem, cfq and deadline was ok (after speaking with hashcode it made the default to cfq) but it was on safestrap 3.11, but then newer versions of safestrap appeared and I updated it and from time to time it started to go bad again.
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
I would ask hascode if safestrap can be a problem, but now he has retired in supporting the d4, of course this can be applied to razr
Regards
lucize said:
I reverted back to 3.11 and I have it working ok since 17.11.2013 (almost 2 days of stable, finger crossed)
Click to expand...
Click to collapse
How is it going?
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Regards.
Sent from my XT894 using xda app-developers app
lucize said:
For me is very good, tried 4.4, now back on cm10.2 nightlies, so
Ss3.11 and only the lteoncdma change, everything else is working fine except tha battery that is shorter than moto default
Click to expand...
Click to collapse
Ok, now I'm on a 10.2 nightly, with just the lteoncdma fix... Let's see how it goes
It took a while to connect to the GSM network, did this happen to you too? (The signal strength icon even changed to a question mark at one point)
I first have no sim, then no signal then I get full bars
Sent from my XT894 using xda app-developers app
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Joril said:
I had it working nicely for 6 full days, but this morning sound went out again Better than before, but still...
I'm on the 28/11 10.2 nightly, I'll try updating again this evening
Click to expand...
Click to collapse
I'm on kitkat, I think that I had it too with 28, try 27 or other, maybe stable, anyway is better than 1 or 2 days
Regards
Definitely better, yes So you're using CM11? Any problems?
Joril said:
Definitely better, yes So you're using CM11? Any problems?
Click to expand...
Click to collapse
the 05 fromm stargo is not so ok, the previous was stable, or at least I didn't had problems.
I'll try the 07, I have problems with deep sleep and I don't know why, because for now wakelocks can't be accessed on 4.4, then again is not a new install, is an upgrade from 10.2
the strange thing is that now I have another error in catlog when it goes out of sound compared to the error when it is on the gsm patch, maybe I'll try a test without changing build.prop at all, in the end it doesn't matter if the signal icon is wrong as long as it's stable.
Regards
Hey! Joril! I posted in your other thread, on another forum, about this same topic, but I figure that I'd get comfy here, since the Droid 4 "scene" has seemingly migrated from DroidForums to this website.
Anyway, I haven't been able to fix the problem. In fact, at one point, when the audio died, I went through the typical steps - I turned off Bluetooth, and reset the phone. However, when the phone was "coming back", so to speak, an "Android is upgrading" box popped up. Odd, I thought, since I didn't do anything different. Anyway, it gets through this, and... I get an UID error. Something about the UID being inconsistent with the system, and that the data partition was terribly unstable.
So, my phone was freaking out. Great. I was missing several apps, and the whole device is incredibly unstable - apps are crashing, left and right, as well as background services. It is at this point that I decide to bite the bullet and restore my phone to stock settings.
I do so. I use the Droid 4 Utility, restore the stock ROM, getting rid of Safestrap 3.11 in the process. Everything's back to normal. Stabilized. I commence to rooting the phone, installing the latest version of Safestrap, and installing CyanogenMod 10.1.3. I get it running, and... the problems remain. I still have the same audio issues. MMS is still iffy. GPS is a hit-or-miss process; every once in a while, if the planets align, a system reboot will "fix" GPS.
Anyway, that's my story. I've been doing some research - or, rather, a lot of research - and it seems to me that the audio problem was, perhaps, fixed in the latest CyanogenMod 11 build. Something about the previous code not playing well with the "Audio HAL", whatever that is, and the Audio HAL issue being consistent with other phones with the same processor, I believe - or something to do with an "MSM8660". I believe that "MSM8660" is a Snapdragon processor, but I could be wrong!
To make a long story short: CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds? I don't know how to code, but it should be relatively simple to patch the few crippling bugs remaining on 10.1.3, using code from future builds and versions.
Jishkah said:
CyanogenMod 10.1.3 seems to be stuck with the audio/crashing issue, but CyanogenMod 11 may fix it. I'm not ready to make the jump to CyanogenMod 11, though, not until it is FULLY stabilized and out of Experimental/Alpha/Nightly status. In that regard, I wonder how open Stargo, Hashcode, or another coder would be to patching up 10.1.3 with the GPS/MMS fixes that have been seen in the later builds?
Click to expand...
Click to collapse
Right now I'm on a CM10.2 nightly and the audio issue appears a bit less than when on 10.1, I'd say once every 5/6 days instead of once every other day... Anyway I'd like to wait a bit more before trying CM11 too
CM11 has this issue also, but the error will not be the same if the build.prop has only lteoncdma modified, for me, if I apply the full gsm patch the error will appear more often and catlog will show the cpu pegged error.
the problem with CM11 (for me) is no deep sleep, the sound issue is not so important anymore