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
Related
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
It's happened several times in the past three weeks, seemingly at random. I'll either be texting or playing a game, and boom. Phone goes unresponsive for about 4 seconds and the boot animation pops up. Sure enough, it's reset.
I have no idea how to get logs or I'd post them. Googling around at the time of this post.
Nexus 5, black, 16g, AT&T and (rooted) stock ROM.
Sonic Offline said:
It's happened several times in the past three weeks, seemingly at random. I'll either be texting or playing a game, and boom. Phone goes unresponsive for about 4 seconds and the boot animation pops up. Sure enough, it's reset.
I have no idea how to get logs or I'd post them. Googling around at the time of this post.
Nexus 5, black, 16g, AT&T and (rooted) stock ROM.
Click to expand...
Click to collapse
you are undervolting?
simms22 said:
you are undervolting?
Click to expand...
Click to collapse
Not to my knowledge. If I am it's because an app I installed did it.
How can I check to be sure?
Sonic Offline said:
Not to my knowledge. If I am it's because an app I installed did it.
How can I check to be sure?
Click to expand...
Click to collapse
if you didnt personally undervolt, than you are not. does it hapoen when using a certain game or app?
simms22 said:
if you didnt personally undervolt, than you are not. does it hapoen when using a certain game or app?
Click to expand...
Click to collapse
It's happened 4 or 5 times with Hangouts, at least once with Chrome and I don't recall what I was doing for the rest, I just made note of it resetting when I didn't intentionally turn it off myself.
What kernel are you using?
Try factory reset fixes 98% of problems
mistahseller said:
What kernel are you using?
Try factory reset fixes 98% of problems
Click to expand...
Click to collapse
Would there be a quick way to restore my phone to the condition it's in (preferably without the hangups)? Because I'd like to avoid that option if possible.
I pulled a logcat off my phone (and let it run for quite some time, 77k lines. Eesh) and there's a few warnings that kept popping up that I don't know how to decipher since I'm not an Android developer.
-[edit]-
Sorry, stock kernel. Only non-stock thing I've done is root it and installed few apps that either need or work better with root permissions.
I find it odd that the phone would do this randomly considering you are running stock ROM and kernel and all you did was root. With that being said a factory reset is your best option. Use titanium backup or helium.
What method did you use to root?
mistahseller said:
I find it odd that the phone would do this randomly considering you are running stock ROM and kernel and all you did was root. With that being said a factory reset is your best option. Use titanium backup or helium.
What method did you use to root?
Click to expand...
Click to collapse
I honestly don't remember which method I used. lul.
This is a problem I've had persistently, I'm only just now getting annoyed enough to make a post about it.
When I first got my Nexus, everything was fine and dandy. Around the end of December though, I had this weird problem where Data turns itself off after about three seconds. I can turn it back on and let it turn off again and fight with it to solve the issue, and eventually it will stop and stay on. I figured I'd give the Cyanogenmod build (at the time) a try, and that fixed it, but had it's own problems (namely bluetooth being very horribad) so I swapped back to stock and sure enough, the problem returned. I don't recall if I did a nandroid restore or a fresh install and a titanium backup of my apps at first because I did try both, neither fixing the problem.
Nexus 5 16gig black on AT&T, stock ROM, only rooted. Any extra information can be posted upon request.
-[edit]-
I installed Paranoid Android, I'll update if I still have the issue.
-[edit+]-
Yes, the issue persists. New info is Paranoid Android v 4.2-BETA1. Obviously, hardware info stayed the same.
-[edit++]-
It appears it was an issue with Juice Defender. Will update if issue persists.
Sonic Offline said:
This is a problem I've had persistently, I'm only just now getting annoyed enough to make a post about it.
When I first got my Nexus, everything was fine and dandy. Around the end of December though, I had this weird problem where Data turns itself off after about three seconds. I can turn it back on and let it turn off again and fight with it to solve the issue, and eventually it will stop and stay on. I figured I'd give the Cyanogenmod build (at the time) a try, and that fixed it, but had it's own problems (namely bluetooth being very horribad) so I swapped back to stock and sure enough, the problem returned. I don't recall if I did a nandroid restore or a fresh install and a titanium backup of my apps at first because I did try both, neither fixing the problem.
Nexus 5 16gig black on AT&T, stock ROM, only rooted. Any extra information can be posted upon request.
-[edit]-
I installed Paranoid Android, I'll update if I still have the issue.
-[edit+]-
Yes, the issue persists. New info is Paranoid Android v 4.2-BETA1. Obviously, hardware info stayed the same.
Click to expand...
Click to collapse
Try another ROM that maybe AOSP source built, see if problem is persisting. If so, is data weak in your area for ATT and it sounds very possible your device has a hardware issue if other ROMs don't fix this. I'm running Carbon, no issues ATM. I can guarantee the CM issues and your issue are not present. If you try the ROM, problem persists, then device needs to be fixed for hardware I'd suggest.
RevelationOmega said:
Try another ROM that maybe AOSP source built, see if problem is persisting. If so, is data weak in your area for ATT and it sounds very possible your device has a hardware issue if other ROMs don't fix this. I'm running Carbon, no issues ATM. I can guarantee the CM issues and your issue are not present. If you try the ROM, problem persists, then device needs to be fixed for hardware I'd suggest.
Click to expand...
Click to collapse
It looks like it was an issue with Juice Defender.
Sorry I know I didn't mention that in the OP. :v
I'll post back if the issue continues now that Juice Defender is gone.
Sonic Offline said:
It looks like it was an issue with Juice Defender.
Sorry I know I didn't mention that in the OP. :v
I'll post back if the issue continues now that Juice Defender is gone.
Click to expand...
Click to collapse
Yes, saving battery by turning it off. Keep updated.
RevelationOmega said:
Yes, saving battery by turning it off. Keep updated.
Click to expand...
Click to collapse
It appears that was what it was. I have had zero issues since uninstalling it, which makes me sad. I liked Juice Defender, and have been using it on my phones for several years. :c
Got my 32gb unlocked A9 a few days ago. Wondering, without modifying anything (unlocking bootloader, custom recovery, rooting, ect) is it possible to run this phone without encryption? My 3rd Gen Moto G feels faster than this. I find the general lag, and sometimes even freezing, a nuisance (especially during read/write), and have no need for the encryption. Is there an option somewhere to disable it? Maybe some different steps during factory setup (i.e. opting out of pin/fingerprint)? I'd like to have the phone decrypted, but would still like to use the fingerprint to wake/unlock the phone.
My phone is on the latest firmware, and I've already tried a factory reset, this is why I'm assuming the performance hit is the encryption.
Example of one of the stutters I notice is going between the home screen and the recents screen. Anyone else get this? Maybe something got screwy during the 20 (/s) firmware updates when I got it?
Edit: Also thought I'd mention that I'm also getting random reboots.
rouyal said:
Got my 32gb unlocked A9 a few days ago. Wondering, without modifying anything (unlocking bootloader, custom recovery, rooting, ect) is it possible to run this phone without encryption? My 3rd Gen Moto G feels faster than this. I find the general lag, and sometimes even freezing, a nuisance (especially during read/write), and have no need for the encryption. Is there an option somewhere to disable it? Maybe some different steps during factory setup (i.e. opting out of pin/fingerprint)? I'd like to have the phone decrypted, but would still like to use the fingerprint to wake/unlock the phone.
My phone is on the latest firmware, and I've already tried a factory reset, this is why I'm assuming the performance hit is the encryption.
Example of one of the stutters I notice is going between the home screen and the recents screen. Anyone else get this? Maybe something got screwy during the 20 (/s) firmware updates when I got it?
Edit: Also thought I'd mention that I'm also getting random reboots.
Click to expand...
Click to collapse
AFAIK it is not possible without TWRP. I have reflashed the whole system and tried if it stays decrypted without setting up fingerprint, but it does not.
I have had some lags as you described, it got better with usage, there are some micro lags, but I got used to it. It is smooth in general. I have also had one reboot in the first few days, but not ever since. Give it a little time.
Sent from my HTC One A9 using XDA Free mobile app
I downloaded the 1.7gb file from HTC and used that to reflash(?) the phone. I can tell some things are different in the UI than when it went through the chain of updates, and seems faster too. Might be placebo. I'm still waiting to see if I get a reboot. Reboots were happening about every 12 hrs.
rouyal said:
I downloaded the 1.7gb file from HTC and used that to reflash(?) the phone. I can tell some things are different in the UI than when it went through the chain of updates, and seems faster too. Might be placebo. I'm still waiting to see if I get a reboot. Reboots were happening about every 12 hrs.
Click to expand...
Click to collapse
Yeah, I did the same too. I felt the phone became more laggy, after updating OTA, so I thought reinstalling the latest firmware might be the best idea. I'm not saying it is perfect, as it is not, multitasking can be really sh*tty sometimes (I have the 2Gb version though), but it is usable, and generally fast and smooth.
Does anyone have any ideas how to find why my phone is rebooting randomly? I'll check it periodically and then it will have a bar stating it's starting. Then my launcher loads and no icons and I need to wait a minute. I don't know exactly what's going on. It appears the phone is randomly rebooting.
Have you tried a factory reset? Are you rooted?
I just factory resetted it and rooted it a few days ago. I got to thinking I think the rebooting started after I throttled the cpu trying to save battery. I just changed the cpu governor fro ondemand to scheduled. So far it seems to run faster but I'm sure the battery will be worse but we'll see if the crashing ceases.
Crashed and rebooted 15 minutes ago. So, changing cpu back didn't fix.
Flash the 100% stock image and try leaving it that way. If the problem doesn't occur, it's something you're doing/flashing/changing that's the cause of the issue.
Obviously I know it's not a hardware issue.... so I know a 100% stock would fix it. I'm trying to figure out how to fix it without putting it to stock.
dorlow said:
Obviously I know it's not a hardware issue.... so I know a 100% stock would fix it. I'm trying to figure out how to fix it without putting it to stock.
Click to expand...
Click to collapse
Just so you know, mine started freezing/rebooting after the May update on stock everything. I think that update has issues.
rft183 said:
Just so you know, mine started freezing/rebooting after the May update on stock everything. I think that update has issues.
Click to expand...
Click to collapse
never had freezing/rebooting issue with mine.
mngdew said:
never had freezing/rebooting issue with mine.
Click to expand...
Click to collapse
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
rft183 said:
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
Click to expand...
Click to collapse
Is this freezing/rebooting Verizon specific issue?
mngdew said:
Is this freezing/rebooting Verizon specific issue?
Click to expand...
Click to collapse
I don't know. That was the only change that I'd made at the time, though. It's gotten really annoying, so I've flash PureNexus with ElementalX to see if that would make a difference. I haven't been using it long enough to say one way or the other.
rft183 said:
I don't know. That was the only change that I'd made at the time, though. It's gotten really annoying, so I've flash PureNexus with ElementalX to see if that would make a difference. I haven't been using it long enough to say one way or the other.
Click to expand...
Click to collapse
I'm also on Elemental X kernel with slightly overclocked cpu. Does the freezing/rebooting take place while in idle?
mngdew said:
I'm also on Elemental X kernel with slightly overclocked cpu. Does the freezing/rebooting take place while in idle?
Click to expand...
Click to collapse
I flashed PureNexus on Friday and used its default kernel over the weekend without any troubles. I've only now flashed Elemental X this morning. Time will tell, I guess!
Edited to add: When I was on the stock rom and kernel, it was freezing while I was using it, requiring me to restart the phone. I would also go to use it after it had been asleep for a while, only to have it do the "Android is Starting" thing. So yes, it was restarting at idle as well as when I was using it.
rft183 said:
I flashed PureNexus on Friday and used its default kernel over the weekend without any troubles. I've only now flashed Elemental X this morning. Time will tell, I guess!
Edited to add: When I was on the stock rom and kernel, it was freezing while I was using it, requiring me to restart the phone. I would also go to use it after it had been asleep for a while, only to have it do the "Android is Starting" thing. So yes, it was restarting at idle as well as when I was using it.
Click to expand...
Click to collapse
Well, I guess the problem with my phone was unrelated. It completely died yesterday afternoon. I'm doing the RMA thing with Google now.
I started having this issue with Android O
I have unlocked version.maybe an app, I'm going to do a reset
rft183 said:
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
Click to expand...
Click to collapse
Well, after getting the phone back reloading the stock image and re-rooting it, I went into developer options and turned off ota updates. So, hopefully I don't get that update... even though root doesn't allow to update. Just causes annoying update prompts.