Database Info

Question for devs about bug reports...

If you were doing nightlys of a rom. In this case CM10.1. You have like 8 or 9 good nightlys with minor issues (nothing that isnt livable) Than you release a new nightly based on your own kernel. In this case it was a minor update. But it totally screws the rom to make it unlivable. Ive never seen random reboots when the phone hangs up phone calls before but yes this one does it ALOT plus all kinds of other freezes.
At that point would you just stop working on the rom you have been doing nightlys and blame it on hashcode coming out with a 3.4 kernel? Rom worked before they changed up the kernel the last time so its not like its a unfixable bug.
Im not sitting here *****ing about the dev taking a long time neither. If they came out and said they were working on it that would be fine. But nope, the whole thing gets ignored...

radzer0 said:
If you were doing nightlys of a rom. In this case CM10.1. You have like 8 or 9 good nightlys with minor issues (nothing that isnt livable) Than you release a new nightly based on your own kernel. In this case it was a minor update. But it totally screws the rom to make it unlivable. Ive never seen random reboots when the phone hangs up phone calls before but yes this one does it ALOT plus all kinds of other freezes.
At that point would you just stop working on the rom you have been doing nightlys and blame it on hashcode coming out with a 3.4 kernel? Rom worked before they changed up the kernel the last time so its not like its a unfixable bug.
Im not sitting here *****ing about the dev taking a long time neither. If they came out and said they were working on it that would be fine. But nope, the whole thing gets ignored...
Click to expand...
Click to collapse
You are forgetting that people like dh are actively working on the kernel, fixing bugs, and adding features.if that happens to break something else then so be it. These are nightlies and it's the price you pay for moving between them.when we're official with cm there with be stable builds available that people can stick to.
sent from my xt926 RAZR maxx hd

koftheworld said:
You are forgetting that people like dh are actively working on the kernel, fixing bugs, and adding features.if that happens to break something else then so be it. These are nightlies and it's the price you pay for moving between them.when we're official with cm there with be stable builds available that people can stick to.
sent from my xt926 RAZR maxx hd
Click to expand...
Click to collapse
But he will not admit there is any issues or anything being fixed. Also he hasnt released anything since the broken july 8th release.
Fixing issues and releasing nightlys that may have different broken things is one thing. But not fixing the current issues is a different story.

radzer0 said:
But he will not admit there is any issues or anything being fixed. Also he hasnt released anything since the broken july 8th release.
Fixing issues and releasing nightlys that may have different broken things is one thing. But not fixing the current issues is a different story.
Click to expand...
Click to collapse
i'll let him speak for himself, but he does know that there are issues. one of them is the bluetooth issue, but he doesn't have a device to stream to to test out a solution. that's why i put up a post for people to donate a headset to him. you're right about him not releasing anything since the 8th, but have you checked github to see if he's done any commits? i would say he has. all of those changes get incorporated into other people's releases such as sks or epinters so really he doesn't need to build himself unless he feels like it. it's not his obligation to tell you which nightlies are better than others. nightlies aren't always better than the night beforehand. i'm personally on a build from the beginning of the month and am very happy with it. identify a nightly that satisfies you and then stick with it until the new issues are fixed.

What's the bt issue? I have none.. I'd think the rebooting when hanging up the phone would be a more important fix than bt.
Sent from my XT926 using Tapatalk 2

radzer0 said:
What's the bt issue? I have none.. I'd think the rebooting when hanging up the phone would be a more important fix than bt.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
No idea about that bug.You realize that dh and others do a lot of the coding for themselves so if they don't experience an issue it may not get fixed right away. If there is a bug make a logcat and send it up the chain.
sent from my xt926 RAZR maxx hd

Easiest way to tell if a dev is working on anything is follow the commit logs -- which they are. And I would suggest posting a logcat especially if no one else has reported similar problems. I've not had any issues with the phone rebooting after a call. Only these pesky bluetooth audio issues and screen glitches with maps in landscape orientation. But of course I can't post anything to the dev board on account of my account status...

Can you do a log cat without being plugged into usb? It never gives a problem on the charger or connected to pc other than I've woken up in the morning and it's frozen on the boot screen. That's with it on the charger but sitting there idle.
Also whenever it would reboot it would hang every time and I would have to force a second reboot.
I don't see how they can't see this second forced reboot needed.. It happens anytime the phone reboots on its own.
Sent from my XT926 using Tapatalk 2

radzer0 said:
Can you do a log cat without being plugged into usb? It never gives a problem on the charger or connected to pc other than I've woken up in the morning and it's frozen on the boot screen. That's with it on the charger but sitting there idle.
Click to expand...
Click to collapse
I use the catlog app. May not catch everything since a rebooting phone would kill the app but it would at least give the dev some info. You could also look at ADB over network located under developer options (in CM).
Also whenever it would reboot it would hang every time and I would have to force a second reboot.
I don't see how they can't see this second forced reboot needed.. It happens anytime the phone reboots on its own.
Click to expand...
Click to collapse
Sounds like the same reboot cycle caused by the bluetooth bug. Might be the nature of the phone in that these (kernel) bugs cause the phone to hang in the bootloader. I'd be more concerned with capturing the initial fault. No need to troubleshoot the forced reboot if it never causes a panic to begin with...

There is a update.. Still having the rebooting issues. Haven't had any issues with the bt tho.
Sent from my Nexus 7 using Tapatalk HD

I've never been satisfied with blue tooth. Even on my OG Droid. I always had issues with it, especially headsets. My motorola razr flip phone never did anything like that. I remember being able to talk on my phone via bt in my kitchen with the actual handset left in the car. Lol. Maybe this new more efficient bt technology will improve all of the issues...
Sent from my DROID RAZR MAXX HD

I'm not having any complaints about bt.. I just keep hearing about all these so called bugs.. Maybe it has to do with certain headsets but my sync system in my truck has no problems.. I want these random lockups fixed. I've had it lockup mid typing on a text message.. Wakeup in the morning with it on the charger and it's stuck on the boot screen.. I've even seen it when a fb notification pops up into the status bar the whole thing locks... The bt bug they all speak of shouldn't make the kernel lock after a reboot having to force another reboot on the lock screen. Bt isn't the first thing on the phone to load... It don't even get to the boot animation before it screws up
Sent from my Nexus 7 using Tapatalk HD

And now I just looked this morning. New version out with selinux.. I'm seeing posts around that at this point it's a buggy bastard and has a long ways to go.. Yet the previous bugs haven't been fixed.. Just added more.. I'll never understand some people..
Sent from my Nexus 7 using Tapatalk HD

jfriend33 said:
I've never been satisfied with blue tooth. Even on my OG Droid. I always had issues with it, especially headsets. My motorola razr flip phone never did anything like that. I remember being able to talk on my phone via bt in my kitchen with the actual handset left in the car. Lol. Maybe this new more efficient bt technology will improve all of the issues...
Click to expand...
Click to collapse
I have had better luck with name-brand and higher cost devices. Cheaper, no-name brands tend to be a roll of the dice. But BT is developed by a SIG so it falls back to their qualification testing. Bad testing or manf that release devices that have not been qualified will lead to problems.
radzer0 said:
And now I just looked this morning. New version out with selinux.. I'm seeing posts around that at this point it's a buggy bastard and has a long ways to go.. Yet the previous bugs haven't been fixed.. Just added more.. I'll never understand some people..
...
I'm not having any complaints about bt.. I just keep hearing about all these so called bugs.. Maybe it has to do with certain headsets but my sync system in my truck has no problems.. I want these random lockups fixed. I've had it lockup mid typing on a text message.. Wakeup in the morning with it on the charger and it's stuck on the boot screen.. I've even seen it when a fb notification pops up into the status bar the whole thing locks... The bt bug they all speak of shouldn't make the kernel lock after a reboot having to force another reboot on the lock screen. Bt isn't the first thing on the phone to load... It don't even get to the boot animation before it screws up
Click to expand...
Click to collapse
You sure it is not caused by bluetooth? Your descriptions sound an awful lot like what happens when my BT stack panics the kernel. The later kernels (.86 & .87) seems to alleviate the problem but after a while it ends up crashing the phone. Make sure the BT radio is off and see if it stops rebooting. Now the later kernels seem to add a lag under certain conditions, but it doesn't reboot if I leave the BT radio off.
SELinux is a security feature that will ultimately help avoid exploits (like the APK one). Problem is cm10.1 repo is still being developed on (vs using a tagged branch that only receives bug fixes). So when the razrqcom devs sync with the CM repo's they pull in the features still being worked on. SELinux can be a nightmare until it is completely configured. In the meantime expect breakage -- a side effect of running nightlies BTW...

Well a stable doesnt ever seem to come along. It gets close than it gets hosed by adding features.
I know the point of selinux. But being that stuff has just started to come out wouldnt one think a dev to actually fix the current issues vs adding something that is already known to be buggy and everything.
Also like ive commented before, if the kernel crashes for one reason or another and reboots. WHY does it have a panic AGAIN before even starting to load the boot animation?
Whatever happened scared the **** out of it before so bad it doesnt want to try again? Thats more a joke but it seems that way.

[Q] New Google Maps flickers on CM10.1

Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.

emi.bu said:
Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
Click to expand...
Click to collapse
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?

PsychoPhreak said:
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
Click to expand...
Click to collapse
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.

emi.bu said:
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
Click to expand...
Click to collapse
Sorry, saw someone mention it, thought it was you! Glad to hear it was sorted, I'll be sure to avoid a map update if I see one pop, but I haven't yet. Maybe it was causing issues outside of custom roms and google stopped pushing it until they got it sorted.

interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..

Tampoon said:
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Click to expand...
Click to collapse
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.

PsychoPhreak said:
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
Click to expand...
Click to collapse
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.

Tampoon said:
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Click to expand...
Click to collapse
Unfortunately it seems to me to be an issue with all of the 10.1's at least, and from my googling before, it seems likely specific to our device, just not sure why
Anywho, I'm pretty OK with maps 6, it works, and still has separate navi app, and is what anyone with earlier than android 4.0 is stuck with anyway.
UPDATE: So I tried the 7/22 update that I got hit with, and it's weird. Initially it seemed OK, aside from the menu button still being half off screen. After fooling around for a bit with menus and settings, it got all flickery again. It seems like it heavily had to do with overlays/prompt dialogues showing up. The box would kind of disappear aside from the outline, but still respond. After fooling around quite a bit and disabling boxes from asking again, eventually everything seems to have evened out. Now I haven't actually done any kind of navigation or heavy use, but I've been using v 7.0.2 now on and off for a few days, and the stutter hasn't come back. Wish I had a more definitive way of what I did to get rid of it, or if it eventually just smoothes out on it's own, but for now it seems like I'm good with the new maps on a CM10.1 rom.

Bump for update, anyone else experiences with new maps?

PsychoPhreak said:
Bump for update, anyone else experiences with new maps?
Click to expand...
Click to collapse
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!

greiland said:
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
Click to expand...
Click to collapse
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story

j1232 said:
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
Click to expand...
Click to collapse
Im running PACman ROM v22.4.0, same issue as you guys with the new maps, and navigation is a stutterfest.

I'm on jellykang 1.8 and that's definitely happening to me. especially in the navigation app

Since others are now finding this thread outside of just us DS users, I figure I'll share this idea from a dev thread:
Originally Posted by pyro9219
"Have you tried Settings > Developer Options > Disable HW Overlays?
I had to do that for several games that were causing screen tearing / artifacts."
I hadn't, but that's a wonderful suggestion, wonder if anyone else has?
Edit: So after learning how to re-enable dev options, I just tried this, and it definitely seems to WAY help. Is there any downside to leaving this checked all the time?
So something for others to try/chime in on?

Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.

anitgandhi said:
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
Click to expand...
Click to collapse
Hrm, I'll try it. Just loaded maps now, it was sketchy, disabled and seemed fine. Turned back on, and it was still fine, this one seems to be crazy inconsistent.

It wotk fine on my device
Gesendet von meinem GT-I9505 mit Tapatalk 2

possible workaround?
I found another workaround that seems to work for me:
Turn on the "Extended Desktop" (or "Expanded"? I'm on German here). And it's gone. Strangely the flickers don't return when I turn it off again.
Extended Desktop Option has to be activated in the settings, if it's not available in the power switch menu.

Counter perspective
I've just been working with the newest CM builds for the MT4GS, and I don't encounter any flickering. This is with a complete wipe prior to installing however.

same issue with HTC G2 on CM10.1
Hello,
I experienced the same issue on my HTC G2 with CM10.1. I had to revert to Maps v6...the v7 would sometime work fine, but most of the time I had some part of the screen flickering and the navigation feature was not usable at all (the animation would not work). I first thought it might be because of the overclocking. but I tried with stock frequency and the issue persisted.
My wife's Sony Ericsson Mk16a also has the same issue but on a custom stock rom..

{Q}to follow the cm 10.2 updates

Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.

Of course you can. Head over to the thread Nardholio started in the Development section.
http://forum.xda-developers.com/showthread.php?t=2405310
The first post has links to: the official CM site and to the Apex Github. The CM site has a changelog for nightlies. On the Apex Github, they maintain a list of known issues.
It's all there.
I caution you on expectations here. Android 4.4 was just announced with a very unfortunate name. I think Jelly Bean 4.3 has about 60 days to live. It would be silly to expect 10.2 to be stable by then. After 4.4 hits Nexus devices, I bet the Apex guys will shift their focus to 4.4 and we will repeat some of this process...

NavarroCol said:
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Click to expand...
Click to collapse
it will probably never happen.
android 4.4 is just around the corner, so i guess the focus will be swapped on that, as it was for 4.3 and 4.2 before

CyanogenMod will do a final "release" build when 10.2 is EOL which will be the most stable we can make it. We also have a last 10.1 build we consider mostly stable, although it is unofficial. Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)

Nardholio said:
Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Click to expand...
Click to collapse
I have random freezes/reboots all the time on the official nightlies -- even the ones people claim are stable. The lockscreen freezes quite often too. Are these known issues or am I just a lucky one? I am running CWM and followed the installation instructions on the Cyanogenmod wiki.
I just installed alogerec and hopefully something will show up to troubleshoot my issue.

Problem with 10.2 nightly as well
I have a problem with the 10.2 nightlies I have tried (all from this week) that I emailed Narholio as he requested.
But since I am a n00b and cannot post to development threads yet I could not post details there. I have not done extensive testing because the screen stays black even though the buttons light up when I try to unlock the phone. I can usually get it to display by pressing the lock button again to lock it, then pressing it again to unlock it right away. This also seems to happen only after the phone has been locked for greater than 20 seconds. If the screen timeout happens, or if press the lock button to lock it, the display almost always works if I unlock it again before 20 seconds is up.
I have not noticed any reboots or other problems, but have not used it extensively because of the black screen problem.

Try http://ls.infernix.net/jenkins/job/apexq-staging/ build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app

I flashed build 336 last night and still have my phone lock up when trying to unlock it. This doesn't happen every time but when it does it either shows the back and menu buttons illuminated with a black screen or an unresponsive lock screen. In either case it will eventually reboot.
Sent from my SGH-T699 using xda app-developers app

Same problem
Nardholio said:
Try build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it

I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.

Good idea
DOMF said:
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Click to expand...
Click to collapse
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?

computerinfo21 said:
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
Click to expand...
Click to collapse
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1

computerinfo21 said:
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
Click to expand...
Click to collapse
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running

Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.

Plenty of free memory
croogrog said:
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
Click to expand...
Click to collapse
Yep, did wipe each time I tried multiple recent nightly versions which all do the same thing. The only one I've tried that works correctly is the 20130309 version.
DOMF said:
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Click to expand...
Click to collapse
I generally keep a tab open to this Relay forum so I can watch what's happening, but not many tabs. Also happens immediately after flashing, without even running any apps, much less installing any.
orange808 said:
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Click to expand...
Click to collapse
I really haven't installed any. And when testing different nightlies I just flashed and it happens right away, didn't install a thing on them.
I decided to stay on a version for a while, so have had 20130920 since Friday, and I've used it long enough to know it is consistent. I have found another way to make it happen: incoming phone calls. When phone wakes that way it almost always happens as well. Today it finally showed the screen when I received a call, but 3 or 4 other calls the screen has just been black so I can't tell who's calling.
I discovered another thing since using this ROM for 6 days. Sometimes I get lines/bars/tearing on screen that won't go away until I lock and unlock the phone again.
I have some other phones that are broken, if I can fix one of them I might consider sending this one to a dev to temporarily play with since it seems to be the perfect test case for this problem. The screen is cracked (I got it used in this condition), which I would normally suspect to be the cause of the problem, however since it does not have either problem with stock ICS, stock JB, or the 20130309 CM I'm pretty sure it's related to something in CM10.2. Just new enough to Android I'm not sure how to track it down.
Thank you all for your help!

I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app

I also have a rev0 cpu phone, and I had a few lockup/reboots since I finally dove in last Monday (9/30) with Staging build 341. However, without me changing anything (still on the same build), they seem to have stopped. Last one I got was 10/2.
Edit: until just now. *facepalm*
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse

I got sick of stock so I tried CM again. After flashing the 10.2-20131014-NIGHTLY-apexqtmo nightly I have not had one reboot or lockup in days. YMMV
Edit: Still haven't had a lockup on wake or reboot.
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse

Hmm... I'll have to try again
Hmm... Sounds like I need to try again then. I tried one released after that and still had issues, but I will try to make some time later to try it. It is fantastic other than that problem.

newer nightlies
Anyone else having issues with the newer nightlies? I have been flashing one a week for a while now and I'm coming from the 14th. tried flashing the 21,22,and 23 all of them are giving me a boot loop at the samsung screen. I have dirty flashed, cleared cache and dalvik, updated recovery. none of them are working for me. Am I missing something? they don't work so i reflash the 14th and everything is good again.
tried in
CWM 6.0.3.7
CWM 6.0.3.8
CWM Touch 6.0.3.8
all with the same errors any help would be appreciated

[Q] Cyanogenmod 11-M9 crashy as hell on Hammerhead?

Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?

starslab said:
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Try without encryption. It's hardly useful and only causes issues on Android.

Lethargy said:
Try without encryption. It's hardly useful and only causes issues on Android.
Click to expand...
Click to collapse
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.

starslab said:
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
Click to expand...
Click to collapse
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.

Lethargy said:
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Click to expand...
Click to collapse
CyanogenMod has Privacy Guard, which is another feature I'm using, mostly with the aforementioned WhatsApp!, which has a list of permissions longer than my arm. I don't like it, but I need it for work.
I'll grant that the custom Recovery and ROM may slightly weaken the encryption (specifically an attacker could alter the ROM from Recovery), but even so having the encryption makes the phone a million times more resistant to data theft and tampering than not having it. It's worth noting that tweaking the ROM is the _worst_ an attacker could do. If I suspected such a thing had happened I could re-unlock the bootloader (which would wipe my data), and re-flash a known good Recovery and ROM. I'd lose my data, but even if the attacker had dumped the partition they still wouldn't have my key, and my data would still be private.

And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
its more then likely the encryption. Disable it, re-flash and see what happens

No encryption. Wiped and trimmed the phone yesterday, now 4 crashes.

Try another ROM, see if it crashes. If it still does, flash factory images and see if it still does.
If so, RMA.

Nothing but trouble for me since upgrading to m9. I have been using the various M builds since March with no problems. M8 was fine. No device encryption for me. I tried turning it on and instead got stuck redoing the whole phone.
Now I get frequent crashing. I switched to the most recent nightly yesterday. Apps stopped crashing. However the os itself still crashes. Several times the screen wouldn't turn on after removing it from my pocket. The light was blinking so it definitely didn't just turn off. It also has stayed black after a few (but not all) phone calls. I've had to hard reset every time to recover.
Thinking about reverting to m8 backup. Willing to give it a few more nightie and see if it works out.

Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Got it from the OTA update. Unfortunately I'm not experienced enough to know how to debug it or use proper logs. It could be that its an app I'm using combined with the most recent update...

Im using M9 snapshot too and i have not had 1 problem its been excellent

No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
+1. I installed another kernel (Chaos) for that reason and it's way faster.
OP: Maybe a bad flash? I would download M8 latest stable snapshot, and do OTA upgrade to M9. That's how I got mine.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
Thanks for the suggestion. I actually have been using elemental and forgot to install it after the OTA. Will put that on now and see if it helps.

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.

simms22 said:
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
Click to expand...
Click to collapse
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Sent from Tapatalk on Nexus 5

last four hours have been fine since adding elemental. Hopefully works in the long run. 8/18 nightly.
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Click to expand...
Click to collapse
What roms do you think are more stable than CM at this time?

trobbs said:
What roms do you think are more stable than CM at this time?
Click to expand...
Click to collapse
Just about any

[Q&A] [ROM][4.4] Official OmniROM Nightlies for N8000/N8010/N8013

Q&A for [ROM][4.4] Official OmniROM Nightlies for N8000/N8010/N8013
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Great Work
At first great work with the fix for Video-Codecs on N8010
I only have an Problem with WiFi Password.
Everytime i rebbot i have to renter the WiiFi Password.
Its not a big thing but how can i fix that?
Thanks again for your great work

Dyoga said:
At first great work with the fix for Video-Codecs on N8010
I only have an Problem with WiFi Password.
Everytime i rebbot i have to renter the WiiFi Password.
Its not a big thing but how can i fix that?
Thanks again for your great work
Click to expand...
Click to collapse
Quite strange I've never had this problem. Try to delete the connection and re-add it
Sent from my Nexus 5 using XDA Free mobile app

I have the same issue. There is nothing to delete since on reboot the connection is not there already.

FlyingDutchman said:
I have the same issue. There is nothing to delete since on reboot the connection is not there already.
Click to expand...
Click to collapse
Try to clean data of settings and settings storage...(you'll loose your settings but not you data) If still not working I recommend a full wipe
Sent from my Nexus 5 using XDA Free mobile app

Did not help me. After full wipe (Factory reset in TWM) it keeps forgetting WiFi settings on reboot. /data/misc/wifi/wpa_supplicant.conf does not save wifi creds. Looks like las nightly build is buggy.
Best,

FlyingDutchman said:
Did not help me. After full wipe (Factory reset in TWM) it keeps forgetting WiFi settings on reboot. /data/misc/wifi/wpa_supplicant.conf does not save wifi creds. Looks like las nightly build is buggy.
Best,
Click to expand...
Click to collapse
I've read about a new file from new note.. Maybe it's causing problems... The change was reverted yesterday, if I remember correctly... Try the new nightly. I haven't got any control over those changes
Sent from my Nexus 5 using XDA Free mobile app

Both versions from 19 and 20.10.2014 do not work. I rollbacked to the version from 20140803, the last backup I have. This one doesn't have mentioned issue.

FlyingDutchman said:
Both versions from 19 and 20.10.2014 do not work. I rollbacked to the version from 20140803, the last backup I have. This one doesn't have mentioned issue.
Click to expand...
Click to collapse
I've found this https://gerrit.omnirom.org/#/c/9804/ . This is the only commit that could have created the problem. Maybe if you revert the file wpa_supplicant.conf on your device as it was on the left of https://gerrit.omnirom.org/#/c/9804/1/configs/wpa_supplicant.conf wifi will start to memorize netwok again.... Can you try this? If you confirm that it starts to work again I'll make a commit and merge it, if you can't I (might) check this on next weekend

Lost of Blue Tooth function N8000
I installed the Kitkat to my Galaxy N8000. However, the Blue Tooth can not detect my Plantronics Backbeat earphone. Can you help?

KK Chan said:
I installed the Kitkat to my Galaxy N8000. However, the Blue Tooth can not detect my Plantronics Backbeat earphone. Can you help?
Click to expand...
Click to collapse
I need a log and a complete description. What do you mean that you installed THE kitkat ? Are you using omnirom or another rom? Or have you flashed samsung stock kitkat and then omnirom? Have you tested with other devices? The bluetooth switch on or not? Can you find other phones?

youtube and video fix by marco9333
Hey the fix works fine on my N8010 (coming from Firmware N8010XXUDNE4)
Thank you marco9333 for your hard work.

Omnirom video issues
I still seem to be having issues with the latest omnirom nightly with xfinity tv not playing very well and taking a long time to buffer with occasional choppy video.
Is this probably still an existing issue with the video codecs in omnirom? I know there were issues that are supposedly fixed a day or two ago, but it seems not fixed perfectly.
CM11 rom plays video fine with xfinity tv. At least the version in android devel unofficial does. It is probably a month or so old version.
Just thought I'd let the omnirom dev know

mo1991 said:
I still seem to be having issues with the latest omnirom nightly with xfinity tv not playing very well and taking a long time to buffer with occasional choppy video.
Is this probably still an existing issue with the video codecs in omnirom? I know there were issues that are supposedly fixed a day or two ago, but it seems not fixed perfectly.
CM11 rom plays video fine with xfinity tv. At least the version in android devel unofficial does. It is probably a month or so old version.
Just thought I'd let the omnirom dev know
Click to expand...
Click to collapse
Are you playing a 1080p video? Try to switch to 720p and report (1080p is useless on our tablet because of screen resolution). I can't use xfinity in my country so I've no way to check it

Video Issues
I posted yesterday that I was having issues with the Xfinity Tv Go app not working well and having issues with playback. After further testing, it does work fine with omnirom. It seems that the buffering issues I had were related to the connection / possibly not working at 100 percent due to battery being low? This doesn't make much sense to me but once I plugged it all worked as expected.
Just thought I'd respond back to my yesterday's post so that it is known I did get this working. Cheers,
I'm very glad to see active developement on this somewhat old tablet. It may be old but it still has great specs and plenty of speed / ram to be a daily workhorse for many years to come imo - as long as the software / security keeps up to date.

After flashing the latest nightly, I have no root and can't get into recovery. How do I re-root?
Sent from my GT-N8013 using Tapatalk

IR Blaster
Just flashed the latest nightly. 25th of Jan 2015.
After trying to use the IR blaster to turn on a Sony TV and a Samsung Smart TV using the peel smart remote (Galaxy Tab) with no success I was wondering if the IR blaster worked? and if so what app is working most successfully?

A serious problem with nighly updates
First of all. I am not receiving any nightly updates. I reflashed the ROM and then I got one update. Its dormant again. I am not getting any update that available for the last 3 weeks.
2nd. My WiFi seems to be disconnecting/reconnecting every now and then, rather every two minutes or so.
I need some solutions for both of these. This the best ROM by far.
Thank you.

yp191198 said:
First of all. I am not receiving any nightly updates. I reflashed the ROM and then I got one update. Its dormant again. I am not getting any update that available for the last 3 weeks.
2nd. My WiFi seems to be disconnecting/reconnecting every now and then, rather every two minutes or so.
I need some solutions for both of these. This the best ROM by far.
Thank you.
Click to expand...
Click to collapse
Dont quote me on this: I think you only get an update to new nightlies when there are changes... Like when the MD5 changes - e.g. there are bits different in the file - I dont think filename counts as a change because that is managed by the file system the file resides-on as opposed to tacked-onto the file...
So even though there may be new nightlies everyday, if nothing is changing in the code they are in effect the same file, bit-wise - so no update.
If anyone knows exactly how the update deltas work can you verify this?
Sent from my Nexus 5 using Tapatalk

GApps wont be updating again, now what?
I was downloading the ROM and the Gapps, but it seems that the developer (of the Gapps) is leaving the thread and not updating anymore... are there other alternatives? thanks!