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 guys,
I'm new to this forum but I have read all rules before posting. I hope I got everything right. If not, please let me know and I'll make changes ASAP.
I have installed Paranoid Android 3.68 last week and have been experiencing this problem (couldn't post it in that thread because I am still a newbie).
My phone crashes into Safe Mode at least once daily without me doing anything. Every time I reboot to normal mode, I would have to restore my 3D Background, Swiftkey, and NiLS apps. So I'm guessing that the crash happened due to (one of) these apps. Could this be an incompatibility issue? Is there any way I can prevent this from happening because it gets quite troublesome to restore these apps so often...
Thanks a lot!
mycxmei said:
Hi guys,
I'm new to this forum but I have read all rules before posting. I hope I got everything right. If not, please let me know and I'll make changes ASAP.
I have installed Paranoid Android 3.68 last week and have been experiencing this problem (couldn't post it in that thread because I am still a newbie).
My phone crashes into Safe Mode at least once daily without me doing anything. Every time I reboot to normal mode, I would have to restore my 3D Background, Swiftkey, and NiLS apps. So I'm guessing that the crash happened due to (one of) these apps. Could this be an incompatibility issue? Is there any way I can prevent this from happening because it gets quite troublesome to restore these apps so often...
Thanks a lot!
Click to expand...
Click to collapse
Hi there;
Try removing one app at a time and observe and good luck
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
I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Cellulario said:
I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Click to expand...
Click to collapse
It did start lagging after a few weeks and for me the recent button took forever (3 secs ! thats a lot since it never took that much long) to open recent menu. So I reinstalled it not knowing whether it was my fault or CM and to my surprise after a few weeks it did it again and I switched to PAC rom. Never looked back. IMO pac rom is the best experience of kitkat on sp.
Hey all, got a problem which needs solving - haven't been able to figure this one out myself.
Okay, here's the dealio:
I'm running CM 12.1 nightly on my HTC One (m7) device and haven't really had any problems which proved to be as hard to solve as this one. My launcher - i use ADWLauncher -constantly crashes no matter what I do (Trebuchet is acting no differently).
Also noteworthy, many areas of my settings are unreachable (such as settings->apps) as they immediately crash upon attempting to access them as well. I've tried numerous methods to fix this annoyance to no avail.
This has been ongoing for over a week now although yesterday my launcher worked flawlessly for a good 8 hours (just the launcher, the other crashables within 'settings' were still crashing. And now for some reason a selection of my apps are crashing as well.
kayohbe said:
Hey all, got a problem which needs solving - haven't been able to figure this one out myself.
Okay, here's the dealio:
I'm running CM 12.1 nightly on my HTC One (m7) device and haven't really had any problems which proved to be as hard to solve as this one. My launcher - i use ADWLauncher -constantly crashes no matter what I do (Trebuchet is acting no differently).
Also noteworthy, many areas of my settings are unreachable (such as settings->apps) as they immediately crash upon attempting to access them as well. I've tried numerous methods to fix this annoyance to no avail.
This has been ongoing for over a week now although yesterday my launcher worked flawlessly for a good 8 hours (just the launcher, the other crashables within 'settings' were still crashing. And now for some reason a selection of my apps are crashing as well.
Click to expand...
Click to collapse
Do not expect nightly builds of CM to be stable and bug free. You should only flash a nightly build if you are ready to deal with various bugs. I would try the latest stable or at least snapshot build (if available) and see if you have the same problems.
I hadn't upgraded for a few days when this started which leads me to believe it's not cm's fault but I'll take your advice and give a go with a stable then post my results. Thank you for your time [:=
Got it
Turns out it was an application I had installed causing some sort of confliction. Managed to uninstall it (after a whole lot of messing around due to being unable to access most of my system) and everything has been working just fine ever since.
The app was SD Maid.......