Database Info

DailyRoads Voyager freezes phone with CM10.1 RC2

I have been using DailyRoads Voyager for almost 1 year without any issues. Even CM10.1 nightlies that came out 2 weeks before RC2 didn't give me any problems. Unfortunately, after upgrading to RC2, whenever I put the app in background recording mode, the phone becomes extremely sluggish, and sometimes even freezes completely. Anybody has any suggestions on overcoming this?

Provide a logcat, it will help identify where the issue lies.
Sent from my SAMSUNG-SGH-I727 using xda premium

ctalcant said:
Provide a logcat, it will help identify where the issue lies.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I have uploaded the log (which I got using Eclipse Logcat) here. The log is from the start of the app till its exit. Please let me know if I can do anything else to get this resolved.

unni_kmr said:
I have been using DailyRoads Voyager for almost 1 year without any issues. Even CM10.1 nightlies that came out 2 weeks before RC2 didn't give me any problems. Unfortunately, after upgrading to RC2, whenever I put the app in background recording mode, the phone becomes extremely sluggish, and sometimes even freezes completely. Anybody has any suggestions on overcoming this?
Click to expand...
Click to collapse
Wait for the next release(s) and hope it works again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Did you ever find a solution for this? I've got the same symptoms on a Galaxy SIII, currently running the latest builds of CM10.1.
A build from 3/8 which I used for quite a while worked fine, but sometime in May I updated to a fresh build and found it was broke, all builds since then have also had the issue.

PDXKris said:
Did you ever find a solution for this? I've got the same symptoms on a Galaxy SIII, currently running the latest builds of CM10.1.
A build from 3/8 which I used for quite a while worked fine, but sometime in May I updated to a fresh build and found it was broke, all builds since then have also had the issue.
Click to expand...
Click to collapse
No. I went back to 15 Feb 2013 nightly build.
The app has the problem even with the 10.1 stable build. The developer promptly replied to my initial query with a debug build of DRV (which has some new features also ). The logs it produced didn't indicate any problem with the app. After that I didn't follow up with him. I will do it this Saturday.

Today, I did a factory reset on my phone, wiped everything and installed ‘Cyanogenmod 10.1 stable’ along with ‘DRV 3.0 Beta 2’. Unfortunately, the problem still exists. Given below are the generated logs:
ADB Log
DRV 3.0 Beta 2 Log (this is from a version I got from the developer).
I also captured a video at the same time the logs were being generated. The video can be viewed from the links below:
Low Quality (96 MB)
High Quality (518 MB)
I had this video captured so that the developer can understand clearly what's happening. The phone slowing down can be seen from 5th minute onwards.
I have also written to the developer.

unni_kmr said:
I have also written to the developer.
Click to expand...
Click to collapse
That's the best idea since the problem is most likely the app and not the ROM. The app most likely needs an update to keep up with the constant updates that the ROM receives.
Brought to you by time and relative dimensions in space.

PDXKris said:
Did you ever find a solution for this? I've got the same symptoms on a Galaxy SIII, currently running the latest builds of CM10.1.
A build from 3/8 which I used for quite a while worked fine, but sometime in May I updated to a fresh build and found it was broke, all builds since then have also had the issue.
Click to expand...
Click to collapse
Tried AutoBoy BlackBox app today. It also freezes the phone similar to how it happens with DRV. The main difference is that with DRV, the freeze usually happens from the beginning of recording, where as with AutoBoy, it happens when I try to come out of background mode. The phone freezing/hanging part is quite similar in both apps. Can you confirm if this is happening with you?
Also, please recommend some other background recording apps I can try so that I can help in finding the root cause of this issue?

unni_kmr said:
Tried AutoBoy BlackBox app today. It also freezes the phone similar to how it happens with DRV. The main difference is that with DRV, the freeze usually happens from the beginning of recording, where as with AutoBoy, it happens when I try to come out of background mode. The phone freezing/hanging part is quite similar in both apps. Can you confirm if this is happening with you?
Also, please recommend some other background recording apps I can try so that I can help in finding the root cause of this issue?
Click to expand...
Click to collapse
I'm afraid I won't be very helpful going forward. My phone is provided via my employer, and I was just upgraded to a Galaxy S4 that doesn't have the issue (and I no longer have access to the S3). Sorry!

Just to update:
The developer reviewed my logs and has come to the conclusion that the problem could be with the ROM.
I also tried Autoguard Pro. It also has the exact same issue when put in background mode.

For anybody stumbling into this thread because of this issue:
CaroO works properly in background mode. It also reads from the OBDII sensor (if you have one), and has a map view as well. I used it for 30 minutes without any issues.

I just ran into this same problem. Voyager with 10.1.2 & 10.1.3 caused absurd sluggishness in the phone. I updated to 10.2 9/22 nightly and the sluggishness is gone.

lonesouth said:
I just ran into this same problem. Voyager with 10.1.2 & 10.1.3 caused absurd sluggishness in the phone. I updated to 10.2 9/22 nightly and the sluggishness is gone.
Click to expand...
Click to collapse
I have been using the latest DRV with CM 10.2 20131028 nightly for the last 3 days. I used DRV for approx. 3 hours in total (about 30 mins each time) along with Torque and Navfree. Didn't face any issues. :highfive:

[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..

My S3's sensors won't work. 100% software related.

Greetings XDA gods! I've been a member for a long time and this is my first post with a question, as I am good at searching and answering my own questions in order to allow others time to be dedicated to making our devices better. I will describe the issue now.
I was running CM 10.1 stable since it came out. I resisted my addiction to flashing my phone every other day successfully, for a long time. My phone was functioning fine. I then decided to flash the first stable 10.2 CM version. Here is where problems began. The flash went perfect as usual and I will now describe what happened next.
1. I noticed that my rotation wasn't working.
2. I searched and discovered a handful of people had the same issues with their own GS3s.
3. I downloaded an app which 'forced' rotation. It worked. That indicates my sensor's aren't physically broken. The app was cumbersome and not automatic so I removed it.
4. I full wiped, flashed 10.2 again, same issue.
5. I full wiped, flashed 10.1??? like I had been running before and still had the non rotation problem happening.
6. Searched and discovered that I had no access to the hidden menu (to manually test the sensors) as CM** doesn't include the hidden menu options in their Roms.
7. Searched forums from all websites remotely related to CM 10.2 and discovered a bigger number of people had the issue, but some had the issue fixed with a nightly release.
8. I full wiped and flashed the nightly they described fixed the issue. (I flash, full wipe, flash, wipe cache's, etc., reboot then reboot again.).
9. The non rotation persisted.
10. I found out Verizon was pushing an ota 4.3 update and although I don't ever partake in that devilish activity, in my desperation for a fix, I decided to go 'there' knowing I'd have to life with my decision until a Dev cracked boot loader, etc..
10. I used the files from this forum to 'stock' my phone, including unroot and flash counter.
11. The 1st flash of the stock version still didn't fix the problem.
12. I rewiped and flashed again, this time updating from the Verizon 'check for updates' menu option.
13. I am now unhappily running 4.3 stock, unrooted (for now) and the rotation problem persists.
14. The was a second, literally, in between the updates that the screen rotated! I was already processing the flash, so I couldn't stop it.
15. I downloaded a app to check sensors. I think its called sensorbox. It reports no sensor info from any one of the movement sensors.
16. My GPS navi function works?! Which it shouldn't. Yet another reason it's software related.
So, for the first time, I am asking this awesome community for help, as my wife and kids are tired of my obsession to fix my phone and all said I need to stop. I am not 'in warranty', so I can't return it.
As a side note from not running any TW Roms since I got my phone, the UI is refreshing. All except for the non rotation..
So, any help that's sensible, not "pull battery and then hold left ear and hop up and down", would be greatly appreciated. I have done all the normal fixs for rom flashing issues, to no avail..
Kurt
Sent from my SCH-I535 using XDA Premium 4 mobile app

Sorry bro, no idea.
BTW, shouldn't this be is Q&A and troubleshooting?
Sent from my SCH-I535 using xda app-developers app

Also... Depending on the Rom, there are up to 6 'enable rotate' menu selections to turn on/off the feature. I have tried them all in various patterns and the none work.
Sent from my SCH-I535 using XDA Premium 4 mobile app

Okay. So maybe its posted in the wrong forum. What should I do? @flyestAC. Thanks for your help
Sent from my SCH-I535 using XDA Premium 4 mobile app

did you ever try the calibrating option in developer options(not sure on where this menu is, on 4.1 tw right now) same place you usually turn backlights off at. might have been worth trying but i have no idea how to do that on the new tw update stuff.
you could always just go to a store and tell them the update borked it. raise some hell and dont mention it being rooted and you might get a new one.

Moved from Original Development (which it is not), to the more appropriate Verizon Galaxy S III Q&A, Help & Troubleshooting (where questions and help go... Hence the title)...

Well I enabled Dev options. There isn't any calibration options. I searched and found that it seems that 4.3 doesn't have the old option to set your phone down on a flat surface and hit calibrate anymore. The settings are under motions/sensitivity but they (3diff types) have no effect at all.
Sent from my SCH-I535 using XDA Premium 4 mobile app

Judging by googles search results, this issue is causing many GS3 owners issues.
Sent from my SCH-I535 using XDA Premium 4 mobile app

kurtazz said:
Judging by googles search results, this issue is causing many GS3 owners issues.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just to chime in, the EXACT same thing started happening to me yesterday. Lost all accelerometer readings on my d2vzw.
I'm on CM 10.2. I tried a factory reset but that didn't do anything. Anyone else having this issue?

I posted this very same issue in 3 other sites. I have a total of 21 who commented that 10.2 made their sensors stop working. No one has a fixed.. posted. Which Id figure there would be at least 1 dev/smarter person than us looking into this issue or at least providing suggestions. I am getting discouraged!
Sent from my SCH-I535 using XDA Premium 4 mobile app

kurtazz said:
I posted this very same issue in 3 other sites. I have a total of 21 who commented that 10.2 made their sensors stop working. No one has a fixed.. posted. Which Id figure there would be at least 1 dev/smarter person than us looking into this issue or at least providing suggestions. I am getting discouraged!
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on board if you can find me a willing and able guinea pig. Root and ADB are mandatory, and I'd strongly prefer AOSP ROMs over TW. Some familiarity with the command line for whatever OS they use would be nice, but definitely isn't required. I can't offer much help setting up ADB except on Linux.

I wish I could be the person to help
the fact that I tried to fix it with the OTA update to 4.3 from verizon, the option to reflash is not an option yet. Unless I am mistaken.
Which may be a good thing.
decimalman said:
I'm on board if you can find me a willing and able guinea pig. Root and ADB are mandatory, and I'd strongly prefer AOSP ROMs over TW. Some familiarity with the command line for whatever OS they use would be nice, but definitely isn't required. I can't offer much help setting up ADB except on Linux.
Click to expand...
Click to collapse

kurtazz said:
the fact that I tried to fix it with the OTA update to 4.3 from verizon, the option to reflash is not an option yet. Unless I am mistaken.
Which may be a good thing.
Click to expand...
Click to collapse
Hold the phone firmly on your right hand and smack it to your left hand. Try a few times this should unstuck the G sensor....

I tried this tapping action. First with my hand them with
A hammer. Still doesn't work. After downloading a few sensor apps all the sensors show that they are on the phone but no data is being delivered.
Again to reiterate, everything worked perfect until the cm stable rom was flashed.
About to throw this thru a wall
Kurt
Sent from my SCH-I535 using XDA Premium 4 mobile app

Same issue ! no sensor data :S
I tried CM 10.2 ROM, then i noticed my screen on my phone doesnt rotate.
tried other ROM´s and nothing,
also used Sensorbox app and there is no sensor data ,
and with GPU-z no data from sensors either
my sensors were working but after flashin they stoped.
can find a way to fix this. im shure its software related because my sensors were working...
any help would be apreciated

maxcrown said:
I tried CM 10.2 ROM, then i noticed my screen on my phone doesnt rotate.
tried other ROM´s and nothing,
also used Sensorbox app and there is no sensor data ,
and with GPU-z no data from sensors either
my sensors were working but after flashin they stoped.
can find a way to fix this. im shure its software related because my sensors were working...
any help would be apreciated
Click to expand...
Click to collapse
Go back to what you had before 10.2
Sent from my SCH-I535 using xda app-developers app

I've had this issue ever since I accidentally took the OTA. Right after a battery pull the screen will rotate right up until everything loads and then nothing. Very frustrating!
Sent from my SCH-I535 using Tapatalk

[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

Problem with my OnePlus One's Screen!

Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!

I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.

welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases

I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?

Try going back to cm11s and then check...
Sent from Android (a google product)

Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.

Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!

One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?

naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?

Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.

donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/

vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.

I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.

donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..

vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.

Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!

Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk

anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.

donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk