Related
Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!
Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8
adam_deluxe said:
Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!
Click to expand...
Click to collapse
Hi,
This is a kernel issue.
Try flashing the kernel in my sig using CWM.
Dacoit said:
Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8
Click to expand...
Click to collapse
I did. Thing is, I'm still a Junior Member, so I'm not allowed to post the experience I had or ask questions about it. I know, it's a ROM-specific question which belongs in the thread of the aforementioned ROM, but asking someone out of the to post it for me would have been about just as much annoying. Still, I'm sorry.
Still, it seemed somehow that no one reported the exact situation, as there were different solutions proposed. But - as I said - I couldn't even add anything to the discussion, since I'm not allowed.
I hope, it didn't disturb you too much.
Regards
Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
EDIT: The UI runs pretty smoothly now and my WIFI and mobile data are not lagging anymore. It MUST have been the kernel.
adam_deluxe said:
Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
Click to expand...
Click to collapse
Hi,
It worked for me,and I've had no black screens since.
Yes, reverting to RC Mix 2.3 solves many glitches IMO. Should do the trick while waiting for a better version.
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.
My wifes Moto G occaisionally crashes and reboots. It hasnt happened very often but I would like to know if it is happening to anyone else and if they know the cause? Maybe it's a bug that will be sorted with a future software upgrade?
The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.
vrsk said:
The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.
Click to expand...
Click to collapse
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.
ahardie said:
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.
Click to expand...
Click to collapse
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
I'll report with the results later.
vrsk said:
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
Click to expand...
Click to collapse
That must be really annoying. Luckily ours isn't that bad.
vrsk said:
I'll report with the results later.
Click to expand...
Click to collapse
Cheers.
Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....
llyenn said:
Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....
Click to expand...
Click to collapse
So far I've had a single instant reboot in the camera app. Hope it doesn't get worse.
The phone is still rebooting sometimes. Is there any way I can check why it is happening like something that will create an error log? Or does anyone have any tips for stopping it happening? It is a very minor nuisance at the moment but I'm afraid it might get worse. Especially if it is a problem with the hardware rather than the software.
I have a UK moto g and it hasn't rebooted on me yet the past week I have had it
Sent from my XT1032 using xda app-developers app
I've got the International 8 GB version from Koodo and it hasn't rebooted since I started using it full time on Dec 28. It remains powered up 24/7.
Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.
I have same trouble. My device is crashing and rebooting sometimes at day. Is there any solution??
Moto g purchased in mexico, telcel.
Guys, return it to your phone dealer if you can. Waiting for a fix(that may or may not come) will just increase your pain. If the service center spots the restart, they should definitely repair/replace your phone.
gee2012 said:
Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.
Click to expand...
Click to collapse
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.
Kit kat seems to have fixed problem.
dankerk said:
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.
Click to expand...
Click to collapse
My wifes phone seemed to be getting worse. It rebooted four times the day before yesterday. It always seemed to be worst when we were travelling.
Yesterday morning the Kit Kat update became available. The phone hasn't rebooted since. Hope I'm not speaking too soon but fingers crossed it seems to be fixed.
We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?
creambyemute said:
We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?
Click to expand...
Click to collapse
If the Kit kat upgrade has cured the problem on my wifes phone then it must have been software related. Possibly an app I had downloaded was causing it. It's worth pointing out as well that most people didn't seem to have this issue.
BTW I spoke to Motorola chat a few days ago using the help app. on the phone. They told me it was probably an app I had downloaded causing it and a factory reset would sort it. Installing the upgrade seems to have done the same thing though.
Happy to hear it's not something hardware related.
I even had reboots with my nexus 5, 4 on random basis (not often). Must be some sort of app I've had installed on all my devices
I received mine in december (from Amazon [Retail.FR]) and experienced some crashes (almost every day).
I installed KitKat on it and did two factor resets to be sure it was not software related issues. Since then, a week ago, I experienced a crash every day and half (screenshot). Crash happened without any reason or specific context.
My serial number is: TA8900B6##
I decided to return my Moto G to Amazon and buy a new one.
I'm experiencing the same and I decided to try to run a constant logcat in the background to see what's going on. Also is there any way to have a constant recording with dmesg? I'm no linux commands expert.
For logcat (in terminal emulator) I used logcat > sdcard/logcat.txt which is growing in size as far as I can see. Hopefully this brings some news.
Good luck everyone.
Cheers
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Using my N5 in germany and it's the best phone I've ever held in my hands Running CM12 (based on Lollipop) for now. Have also been using stock Lollipop for a few months. Both run extremely stable. To be honest: I never heard about your issues. I'm not that big of a fanboy. Never owned a Nexus device before, but I guess I'll never move away from Nexus
Just my honest opinion about the device
By the way: I've got a moto 360, too. And the connection is great - up to 10 meters at least and no random disconnects
I have zero issues with mine, but I'm on stock 4.4.4 so that may have something to do with it. I'm not a fan of Lollipop at all. Too many bugs, and I don't like the look of it.
After one year with my Nexus 5, running stock no root, never a problem. I'm a former owner of HTC flagships phones, never a problem with them.
Sent from my Nexus 5 using Tapatalk
Using Stock 5.0.1 rooted and with ElementalX kernel is good for me and have been using that setup for over a month now. No issues like what you're describing at all. :S
No problems here like that. Bug report issue is normally a poorly fitting case
Hmm... So it seems that the only people that are having these bugs live in my area... Do you think its possible we all got a bad batch of n5s at the rogers store here?
Edit: everyone experiencing these issues has bought their phones from rogers stores here in my city.
OFWGKTADGAF said:
Hmm... So it seems that the only people that are having these bugs live in my area... Do you think its possible we all got a bad batch of n5s at the rogers store here?
Edit: everyone experiencing these issues has bought their phones from rogers stores here in my city.
Click to expand...
Click to collapse
Yeah the devices purchased at the play store seem to be fine now. At first, me personally, I had tons of bugs at release. But those issues have been fixed with updates. Mainly concerning the signal and camera speed.
Thread cleaned.
If you think a report is breaking the rules or shouldn't be there for any other reason please report it and move on, antagonizing them adds nothing to the forum but makes our job harder. Thanks, Tijmen.
No issues here besides the occasional Mobile Radio active wakelock, which I did also see occasionally on KK. I did have some memory leak issues on 5.0.0 but either 5.0.1 fixed it or me removing some 3rd party background services did.
OFWGKTADGAF said:
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Click to expand...
Click to collapse
A reboot a day keeps the android bugs away
kevtrysmoddin said:
A reboot a day keeps the android bugs away
Click to expand...
Click to collapse
Rebooting is normally my go-to solution for problems but it doesn't seem to help these bugs. I installed CM Security and it constantly warns me about my CPU usage/RAM and battery Temperature. The culprit almost always seems to be the Facebook app (sometimes using 250+ mb of RAM just for background services) Could this be a bug with the Facebook app making my phone perform poorly... Does anyone know of any solid alternatives to the official Facebook app?
OFWGKTADGAF said:
Rebooting is normally my go-to solution for problems but it doesn't seem to help these bugs. I installed CM Security and it constantly warns me about my CPU usage/RAM and battery Temperature. The culprit almost always seems to be the Facebook app (sometimes using 250+ mb of RAM just for background services) Could this be a bug with the Facebook app making my phone perform poorly... Does anyone know of any solid alternatives to the official Facebook app?
Click to expand...
Click to collapse
Fast for Facebook I'd a good alternative
I've been without issues since the factory images were first released, running CM12 CAF builds without issues (besides cm12 bugs)
So call me crazy but I deleted the Facebook and Messenger apps about 6 hours ago and have had 0 problems since... I'm using the official Facebook "Lite" apk I found online and while it is very ugly, things are running much smoother, just hoping that maybe this will solve the bugs I've been experiencing and I'll be able to help my friends get there phones back to a usable state.
OFWGKTADGAF said:
I'm not sure if people are just really downplaying the bugs their experiencing, or maybe Canada just got a big batch of bad phones but it seems nobody online is having the problems me and a few friends are having with our phones. When 5.0 first arrived I was shocked to find I experienced none of the bugs that everyone was complaining about, 2 weeks later and my phone in unusable. A factory reset seems to clean things up but within another week my phone will become unusable again. I thought maybe my phone had broken until I spoke to some friends and found out that multiple (5+) are having the exact same issues. So my question is what's going on with the n5? How is yours working? I'm extremely disappointed this time around after the great experience I had with the galaxy nexus and n4 and would even say I was a nexus fanboy. After having the n5 since launch I have decided that I will no longer be buying nexus phones, as I have has nothing but problems with the 2 n5s I have owned.
A quick list of some of the bugs I've been experiencing are:
Terrible Battery
Immense lag / lack of response in general.
Facebook Messenger chat heads seem to close themselves about 75% of the time.
Getting the keyboard to come up is a game of hit and miss.
The Wallpaper changes itself to black (my indicator things are about to get crazy)
Data/WiFi often just stop working, while icons in the status bar appear normal
About 1 in every 4 notifications I get fails to actually send a notification.
I get a constant "attempting to reconnect in x seconds" while connected to my moto 360.
My navbar/status bar often disappear.
And the annoying "bug report captured" bug that has been persistent since I got the phone.
I've had these problems on stock 5.0, 5.0.1 as well as all custom Roms up to 5.0.2
I've even tried going back to KK, while greatly improved, I still experience much of the same problems.
Does anyone else have these or similar problems? Has anyone found anything that runs stable? Or is it just time I move on and get myself an HTC?
Click to expand...
Click to collapse
I know it's really late in the game now, but have you tried starting in safe mode to see if you have the same issues? It could be an app causing all the grief.
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