Database Info

Reboot issue with JB 4.1.2 vzw newest update on Razr HD

Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!

xgshortbus25 said:
Hey so after a few days of the new update running OK I started having random reboots! I noticed on a few other sites people complaining about the same issue of reboots multiple times of the day! Just wanted to let everyone know a possible solution to the issue! I have went through multiple FDR's and did come to the conclusion that the random reboots for my phone were associated with a new update to the chrome browser and were easily fixed by uninstalling new update and telling it not to automatically update so hope this helps anyone who may be having the same issues!!!
Well so much for that after trying everything its back to rebooting again? I love my phone but seriously considering putting it against a wall!!!
Click to expand...
Click to collapse
Never had that issue with the new update. Try doing a factory reset or try the new fast boot files to start fresh. Not sure why chrome would be an issue.try the chrome beta version but I suspect chrome had nothing to do with the reboot just a bad initial update.
Sent from my DROID RAZR HD using Tapatalk 2

Fixed!! I hope!!!
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!

xgshortbus25 said:
Finally broke down done a fast boot to the new files all is working seems OK anyway know in a day or 2!!!
Click to expand...
Click to collapse
My Wife's phone is doing the Random Reboot thing since the 4.1.2 update as well. I did a Factory Reset on it and it still does the same thing.
I suspect an application is doing it? Because I put the phone in Safe Mode and it never rebooted while in Safe Mode.
But I have No Idea of how to tell which app is doing it, other than to uninstall a random app after every reboot to find out which one it is.
But I would like to try this fast boot option? I know how to get the phone into fastboot, but which files are you redoing? What exactly are your doing ?

Have the same problem. I have done:
SBF 4.1.2
FDR
WIPE
Even tried running a parallel rom with safestrap (bakatang)
The chrome thing did not work
Keeps freezing. Seems the problem is way worse when having the phone play some music.
I am just about unlocking the thing and SBFing back to 4.1.1 but not really interested into unlocking the bootloader. That would be the last choice for me.
If someone knows of some way to fix this, please help, this used to be a great phone...

No problem here with the sfr rom... used for over 1 month now and no problem and my system is always fast...
Sent from my XT925 using xda premium

I've been running some tests for about a week now since I got my RAZR and the results are interesting... I've had lockups and reboots multiple times a day, most often while doing something involving sound i.e. listening to music or playing a game or video. I've tried stock and custom 4.1.2 ROMs and custom 4.2.2 ROMs and it persists so I'm inclined to say its either bad audio software or faulty audio chips. This is everything I've done:
1. turning off sounds (keeping phone on vibrate/silent) pretty much eliminates the random lockups/reboots I got from receiving multiple texts or calls at once. I noticed if I bombarded the phone and made it ring a lot it gave the same results as listening to music but if its just a text or email or call here and there during regular use it the phone works fine.
2. Listening to music, either streamed or local from phone/SD storage and through headphones or speaker, would cause skips and audio cutting out. After a few minutes of this the phone will lock up completely and reboot itself. Strangely enough it happened only rarely or not at all while streaming music via bluetooth to a stereo.
3. I don't think its anything kernel related or if it is its not causing visible errors or wake locks. My battery seems to be just fine through all this.
4. I have tried multiple music/video players, put my SD card with music in another phone and the music plays fine, stock ROMs with nothing disabled/removed still has the issue, custom ROMs debloated and modified also have the issue. I think I've just about covered every base I can as an end user to track down what's causing it but I'm open to suggestions.
I have a replacement scheduled so I will see if that fixes it, I have seen this problem reported quite a few times all over the interwebz but there are also a lot of people not having the issue either so idk. If there are any Devs or anyone skilled in android-fu that can read logcats I will be more than willing to get those for you. Sorry for the essay everyone lol
tl;dr Like others I have freezes and reboots from what seems to me to be an audio software/hardware problem, either built in or from the 4.1.2 update
Sent from my DROID RAZR HD using Tapatalk 2

I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.

barbaroja said:
I am almost sure is kernel related bc I did not have problems in the 4.1.1 sw.
If someone that has an unlocked bootloader could install 4.1.1 from an sbf and tell if the problems are gone, would be great!
here is the sbfs: http://sbf.droid-developers.org/vanquish/list.php
here is the bl unlocker: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
u have to be rooted here: http://www.droidrzr.com/index.php/t...roid-root-exploit-412/?pid=244281#entry244281
I am not doing that bc I do not use custom roms so dont want to unlock BL. If someone has, this could help much. It is different from using safestrap, because safestrap uses the same kernel, from what I read.
Click to expand...
Click to collapse
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2

anoninja118 said:
I have seen reports that the problem persists even on 4.1.1 but I am unlocked and rooted on stock 4.1.2 so if I get time I can give it a try
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!

barbaroja said:
When I was at 4.1.1 phone was near perfect.
If you are unlocked, please do check. I am debating whether to unlock or not just bc of this. Today it has resetted at least a good 20 times or so.
Thanks for helping!!! Waiting for your results!!!!
Click to expand...
Click to collapse
one solution that has worked for me is silencing the phone or putting it on vibrate and I haven't had a freeze or reboot in almost 2 days... the problem seems to me to be related to audio/sound and not listening to music or watching videos along with silencing ringtones has put a stop to it which kind of confirms my suspicions... I will try and flash back when I can but it'll need a day or 2 of field testing to confirm if its a solution
Sent from my DROID RAZR HD using Tapatalk 2

I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.

barbaroja said:
I can confirm that audio stuff just does worse to the phone. However, I have not had your luck when silencing. Keeps rebooting no matter what. Please let us know when you do.
Click to expand...
Click to collapse
looks like a negative on the SBF, tried to restore 4.1.1 and it failed halfway through the flash, now won't turn on... working on reviving it... I really need to replace this thing as its been nothing but a PITA since I got it
old school post from my Thunderbolt via Tapatalk

wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it

barbaroja said:
wow that sucks. I recall reading somewhere that you could actually downgrade your software version if you have an unlocked bootloader.what is the error you are getting? Tried using RAZR utility 1.1? Won't it turn on at all? Maybe a discharged battery? Hope we can solve it
Click to expand...
Click to collapse
got it revived with Mattlgroff's new 1.2 utility, was able to force it to fastboot mode... the problem seemed to be some kind of partition error, I tried redownloading the sbf files thinking it was a bad file and got the same error so idk what it is since I'm on stock unrooted 4.1.2. My bootloader is already irreversibly unlocked so that won't be a problem lol but I am a n00b to RSD Lite and Moto devices so I'll tinker with it more when I get some free time
edit: I did have a Maxx HD way back at launch for a month or so running stock 4.1.1 and it ran perfectly, so my idea is its kernel/codec/software related. Hopefully a custom ROM (or hell even stock) with Hashcodes Qcom kernel will fix the issue we're having
Sent from my DROID RAZR HD using Tapatalk 2

I talked with vzw service, the assistant said that 2% of the phones were having this issue, wich for this kind of technology is a pretty big number of phones. Suuggested to send it to Motorola but since its rooted its almost sure not to be replaced by them. What is strange is that not everyone is having this issue. I would be almost sure Motorola is going to release a fix for this, but would not count days. Getting kind of frustrated with this phone I used to like so much. Thinking of going the htc route bc this is getting unbearable.

Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...

barbaroja said:
Any news in this? Anyone tried a new ROM that could solve this? Or even a fix?
... or just everyone had another phone lying aroud...
Click to expand...
Click to collapse
My wife & I both have this phone and still are constantly being rebooted. This is even after the software update. I have been wiped, factory reset, and everything possible, but I've not called for a replacement yet. Normally I havea worse luck with those.
Wife used to love this phone, now she hates it and hates we changed from AT&T to Verizon since we have no backup Verizon phones. At least we could take the sim out and go to the iPhone that's floating around the house when the phone went to pot before. Makes me really hate suggesting that we go back to Moto phones since that's all that I've used on Verizon.
Wonder if big red will get the new HTC One....

Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2

barbaroja said:
Tried flashing the MR-4 sbf, but did not solve the issue.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
If an sbf didn't solve it then it's a hardware problem.you guys are definitely in the minority with this reboot issue.go get a warranty replacement.this phone and moto in general are solid phones.
sent from my xt926 RAZR maxx hd

Question for devs about bug reports...

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Q] Updating to 4.4 bootloader

I've had my XT926 rooted/unlocked since the original exploits surfaced. I'm now trying to update my CM11 nightly to the latest one, and I can't because "this package is for devices with 4.4 bootloader". Is there a way to update my bootloader to the 4.4 version without installing stock KK? Is it worth it? The CM11 nightly I'm trying to install is the one that I download through the CM updater through settings.
Sorry if this has been answered, I really did search here and the razr forums and couldn't find a specific answer for my device.

Raikalo said:
Is there a way to update my bootloader to the 4.4 version without installing stock KK?
Click to expand...
Click to collapse
Unfortunately, no. It involves flashing the latest Moto firmware for your device, followed by flashing a KK ROM (such as CM11).
Raikalo said:
Is it worth it?
Click to expand...
Click to collapse
In my opinion, absolutely not. Assuming you have an XT926, this device runs so much better on a JB bootloader, as I have regretfully found out. I'm not running CM11, rather another ROM, but all the problems that I've been battling (battery, GPS, WiFi, speakerphone issue, various system FCs) ever since I upgraded to a KK bootloader have completely changed my device for the worse. ymmv

Not_A_Dev said:
Unfortunately, no. It involves flashing the latest Moto firmware for your device, followed by flashing a KK ROM (such as CM11).
In my opinion, absolutely not. Assuming you have an XT926, this device runs so much better on a JB bootloader, as I have regretfully found out. I'm not running CM11, rather another ROM, but all the problems that I've been battling (battery, GPS, WiFi, speakerphone issue, various system FCs) ever since I upgraded to a KK bootloader have completely changed my device for the worse. ymmv
Click to expand...
Click to collapse
Fantastic, that pretty much answers that. I'll probably just sit tight on the JB bootloader then and avoid the hassle. Thanks for the help. Sorry to hear about your issues with the new bootloader :/

Battery life appears worse because it's more than likely poorly written apps. The API for KK had improvements made, and apps that were written before KK may have worked fine under JB, but were still poorly written but could get away with it. Once KK came out, the poorly written code was finally exposed for what it is: code that should be fixed.
Depending on how the apps are releasing resources, it could cause drain on the battery.
I myself have found my battery life to be the same as it was under JB.
One thing to really look at it is your battery stats to see if there is something waking up your phone while it's asleep. Go to Settings->Battery. Select the graph and then look at the lines below it (see attached jpg for an example).
In the screenshot attachment I've provided, compare the "Wake" line with the "Screen on" line. What you really want to see is that when the screen was off (no blue lines in the "Screen on" area), you should hopefully see minimal blue lines in in the "Awake" line in the same positions. If not, it means something is waking up your phone. In the screenshot above. you can see that there are definitely some times where my phone woke up while the screen was off. WiFi was on all the time as well. Of course, you'll probably still see some lines if you have syncing turned on, or other background processes. You might never be able to completely ensure there are no lines when the screen is not on, but you want to minimize them as best as possible. In the picture above, I was having my phone do other things (update apps, etc), but usually, I can get it minimized pretty well.
To better help determine what might be causing this issue, you can download an app from Playstore called "Wakelock Detector". Basically, charge your phone up completely, install Wakelock Detector and allow your phone to sit for about two hours without being charged and then run Wakelock Detector and see what it says. You might find you either have a lot of syncing going on (I've turned a lot of that off including gmail sync, photo sync, play books, play magazines, play movies/tvs, soundsearch, etc). Syncing is usually the #1 culprit for most people after setting up their Google accounts because they just go with whatever was set up. Or, you might find an app that seems to stay on a lot and will warrant more investigation, but it could definitely help in determining what the issue is.
I also am rooted (which does NOT affect battery life) and I run the Xposed framework with the Greenify module which helps. With this, you can "Greenify" apps - in otherwords, prevent them from causing a wakelock. Many games these days will just wakeup to give you notifications. In many, you can just go to the App Info for the app and uncheck the "Notifications" checkbox. Greenify is different from task killers. It doesn't "kill" the task (which can cause even MORE battery drain), but instead, prevents it from "waking up". The donate version allows you greenify system apps as well, but that could cause more issues. Usually, greenifying user installed apps is usually sufficient. So, if you have a misbehaving app, you can use Greenify to discipline it until it gets fixed (if ever). Or, remove the app and see if you can find a replacement.
Also, having GPS on all the time drains. Most of the time, you can either live with the battery saving mode or turn it off altogether until you need it.
On my Razr HD (non-Maxx), I can get about 72 hours before I'm down to under 10%. This is on stock or CM11.

One of the questions in the OP was (I'm paraphrasing) "Is upgrading an XT926's JB Bootloader to a KK Bootloader worth it". I answered "In my opinion, absolutely not", and I provided examples for my statement. It doesn't matter whether the apps that are available today are poorly written or not. Fact is, on my XT926, they seemed to run light years better on the JB bootloader than on the KK bootloader, as evidenced by the fact that I never had any problems with them under JB.
I am not disputing that other smartphone brands or models may run KK just fine with a KK bootloader. But my XT926 does not. Yes, I do run Greenify, and battery apps and whatnot on my device. The problems that I mentioned are still there. Granted, it is a MAXX variant, so when I say battery problems, I'm talking about having only 30% left in the tank, after putting the device through a grueling daily workload. But I used to get 2 to 3 days out of it without charging it, so it is a problem.

Not_A_Dev said:
One of the questions in the OP was (I'm paraphrasing) "Is upgrading an XT926's JB Bootloader to a KK Bootloader worth it". I answered "In my opinion, absolutely not", and I provided examples for my statement. It doesn't matter whether the apps that are available today are poorly written or not. Fact is, on my XT926, they seemed to run light years better on the JB bootloader than on the KK bootloader, as evidenced by the fact that I never had any problems with them under JB.
I am not disputing that other smartphone brands or models may run KK just fine with a KK bootloader. But my XT926 does not. Yes, I do run Greenify, and battery apps and whatnot on my device. The problems that I mentioned are still there. Granted, it is a MAXX variant, so when I say battery problems, I'm talking about having only 30% left in the tank, after putting the device through a grueling daily workload. But I used to get 2 to 3 days out of it without charging it, so it is a problem.
Click to expand...
Click to collapse
I understand and again, those are probably apps that need to be recompiled under the new KK API. Developers should always ensure their apps compile under the latest compiler to ensure they aren't doing something wrong. That is not a fault of KK, but of the app itself.
I myself have found the phone to work better for me under KK than JB, albeit there are issues with Wifi and such, but those are firmware issues, not issues with KK itself and Moto needs to address those issues.
In any case, whatever works for everyone, but I just wanted to give an explanation as to why people see battery issues. It's something that myself and other developers understand that most of your normal users (non-dev) probably don't know, and there isn't any reason as to why they would, unless they investigated it further and such.
I'm not trying to say the OP, nor you, are incorrect in your assessment of KK. I just wanted to give an explanation as to why some people do not have an issue, while others do. It would definitely be more of an issue if everyone complained of this issue.
I was part of the KK soak tests, and it was split 50/50 (possibly favored more towards those who found better battery life) on good/bad battery life after KK. That alone pretty much states it's poorly-written apps. Believe me when I say, writing an android app is completely different than it is with say a Windows app. In Windows, you don't have to worry about battery life, etc. Your windows program can run constantly. However, with phones, you have to take into account that at any time, your app can be stopped when it's no longer in the foreground. It's put into a suspended mode that could then result in it being completely removed/killed when resources (which are limited on phones) are very low and another process needs it.
Also, keeping resources locked drains batteries, or calling an out-dated API function in the kernel/system can also cause performance issues.
And in the end, it's always good to do a Factory Data Reset (FDR) whenever the upgrade is major, such as going from JB to KK. There were a lot of improvements and enhancements done within the Android framework that leaving stale cache/apps around can result in a lot of garbage that causes performance issues.
But, if JB is working better for you, then that's what counts in the end.
Just wanted to let people know that there are ways to get it working better under KK.

The only reason I am still on KK is because I am waiting to see what Moto's upcoming (presumably final) OTA KK update will do for the progress of this device. And I certainly hope that my ROM's devs would then bake those changes into the ROM. If I don't like what I see, I may consider using nobe1976's flashback script to go back to JB, seeing that I still have 7 months left on my contract for this device. But I'm not really holding my breath hoping that Moto's final soak software will fix the problems.

Not_A_Dev said:
The only reason I am still on KK is because I am waiting to see what Moto's upcoming (presumably final) OTA KK update will do for the progress of this device. And I certainly hope that my ROM's devs would then bake those changes into the ROM. If I don't like what I see, I may consider using nobe1976's flashback script to go back to JB, seeing that I still have 7 months left on my contract for this device. But I'm not really holding my breath hoping that Moto's final soak software will fix the problems.
Click to expand...
Click to collapse
Apparently, dhacker has fixed the WiFi issue with the 08/19 build of Gummy ROM. I'm currently flashing to that right now, so we'll see how that works.
There are still mic issues. Apparently, going to speaker phone when talking with someone turns off the mic for the next call and doesn't turn back on without you rebooting the phone.
I'm not sure how much Moto will fix as it appears to be now all firmware based (wifi, blue-tooth, 4g). Everything else seems to be fine, so I'm not sure what Moto will do.

iBolski said:
Apparently, dhacker has fixed the WiFi issue with the 08/19 build of Gummy ROM. I'm currently flashing to that right now, so we'll see how that works.
Click to expand...
Click to collapse
It's only a minor issue on my device right now. Occasionally (very seldom), WiFi drops off, and inexplicably reconnects by itself after a second or so. But WiFi does consume relatively large amounts of battery. That's a problem.
iBolski said:
There are still mic issues. Apparently, going to speaker phone when talking with someone turns off the mic for the next call and doesn't turn back on without you rebooting the phone.
Click to expand...
Click to collapse
That's a huge problem, and I'm experiencing this on my XT926 right now. Actually, I've had it where in the same call (not the next call), the party on the other end couldn't hear me after I switched from speaker to normal. Gets "solved" only by rebooting. That right there jeopardizes the whole concept of calling while driving.
But there's more: Navigation (which I depend on a lot) does not work correctly (loses GPS signal). Bluetooth works sometimes, and sometimes it doesn't (also bad for calling while driving). Random FCs of Playstore apps that I never experienced under JB.

Yeah these issues are exactly why I was afraid to jump ship and update the bootloader. Will it be possible to update CM11 any further without the new bootloader? I don't really need to, as my current nightly is recentish and stable, but I'm just curious.

Use the jbbl version http://download.cyanogenmod.org/?device=moto_msm8960_jbbl

DorianX said:
Use the jbbl version http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
Click to expand...
Click to collapse
Thank you, I missed that addition to the website.
I think I know the answer, but just to verify: is it possible to downgrade the bootloader from KK to JB if I made the jump?

[Q][H]Touchscreen issue

Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.

Nikouy said:
Hi All,
During the last couple of weeks, with different ROMs I've been experiencing some touch screen issues. I feel like there is a 0.5s delay/lag on the touches which makes using the phone annoying. I can barely type and touches are not really accurate.
Not sure if there is any good app for testing the touchscreen, but I tried one (Test Touch) and as far as I can see, touches are not registered or are intermittently registered when fast touching the screen. (See Video). When I slowly drag the finger, a continuous line is traced.
I couldn't find anyone else having the same issue hence I'm posting this. Thanks for the help.
Current ROM: Temasek's UNOFFICIAL Build, 10.1, CM 12.1 .
Stock kernel.
Edit: Ram use is always lower than 50% and CPU usage is low.
Click to expand...
Click to collapse
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.

You_got_owned123 said:
You're not the only one- I opened a thread about this. Seems as something happened as people updated to android 5.x as did with me.
Hopefully someone can figure something out!
Seems more like an input lag- like you mentioned. Really annoying and makes it hard to type fast or use swype function.
Click to expand...
Click to collapse
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated

guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Happy to know I am not the only one having this issue , good that we are on the same boat.
I'm travelling in a few days and can't go abroad with the phone in this "working" conditions so I will have to downgrade for sure. Any 5.0 ROM to recommend? A solution for 5.1 would be better

haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!

guih said:
haha I was on Blisspop for a long time before moving to 5.1, it's a fantastic ROM!
Click to expand...
Click to collapse
I flashed Slim ROM, touches delay improved a bit but I was experiencing some lag on the hardware keys.
I just flashed last bacon firmware (from April 09) and RobbieL811 ROM and seems to be running smoothly, I wonder if it was a firmware issue. Thoughts?

Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..

Infinityyy said:
Right, I have the same bloody problem, and I'm seriously thinking of going back to kit kat. What the hell happened, it worked perfectly. Does everybody have an unlocked bootloader? COS12 worked ok, lagged when hot, only after I unlocked the bootloader did it all go to ****. I just hope it'll go back to normal on KK and it isn't a permanent thing now..
Click to expand...
Click to collapse
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?

gsmyth said:
I have an unlocked bootloader and have moved from 11S to 12S and find its a lot better. I've seen people say they find the update better and some who have issues but your boot loader shouldnt really come into it. How did you update, what did you do since unlocking your bootloader?
Click to expand...
Click to collapse
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.

guih said:
I've been having this issue too! I thought it was the ROM, but I am on my second one now with the same touch lag . I didn't have the issue in 5.0, though. I might consider downgrading and hope that that fixes my issue. Any help on this would be much appreciated
Click to expand...
Click to collapse
Infinityyy said:
Went with COS12 for a while, then tried a 5.1 rom and it started going down from there. COS12 lagged a lot when the phone was charging, it got very hot for a while, and then cooled down. I don't know why touchscreen issues started happening, it worked ok for some time after installing 5.1, then for instance the settings app started scrolling slowly, the notification panel as well, some touches stopped being registered.. It's a weird issue, because it's not lagging, like skipping or so, but mostly it feels like the phone is in slow motion.
Click to expand...
Click to collapse
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.

Nikouy said:
Same happens to mine.
I flashed 3 different ROMs today, 5.1 and 5.0, it was working fine for a few hours with one of them but after that It started with serious problems, to the point of nearly not registering any touch. After a reboot it improved a bit but it makes the phone unusable. I'm flying abroad in less than 12hrs and really need the phone.
Flashing a stock ROM or going to kit kat are the only options I see now.
Edit: Here I found some useful post, they state it's hardware not software.
Click to expand...
Click to collapse
we're not alone man, multiple threads are popping up with people suffering from similar issues, including on reddit: http://www.reddit.com/r/oneplus/comments/33ky0u/open_post_to_oneplus_with_all_our_love_and/

I am having the same severe issues as well.
The nightmare begun after the 05Q update.
Ever since that update, no matter what I've tried, the touch problem is here.
I've tried numerous Roms + kernels combinations with no use.
OP support was trying twice to reset my phone to full factory reset to both Oxygen & CM11s with no use.
That is so frustrating.

i have the same problem, but only when i go outside and the weather is nice

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