Related
Ok, apologies if this is old news, but didn't see. But I've just updated my O3D OTA in South London, UK. Not that it would make a difference but I'm T-Mobile in case anyone intereted.
Im having random restarts since update. Anyone else having this problem?
Sent from my LG-P920 using XDA App
Yes some people complain about restarts like I. I install bootlog uptime and i discover that phone restart every few days, mostly when i'm not watching
I had that problem in the beginning but after a factory reset it stopped doing that.
otacon888 said:
I had that problem in the beginning but after a factory reset it stopped doing that.
Click to expand...
Click to collapse
I will give it a try and see if it helps
---------- Post added at 07:15 PM ---------- Previous post was at 06:46 PM ----------
Mobile Phone Support: We are expecting the Gingerbread version of Android to be available no later than November. The faults that you have experienced isn't a known issue unfortunately, I can only suggest that you continue to check the support tool for upcoming updates.
from lg phone support
I've not noticed any restarts as yet, though only been few hours. Not sure if it makes any difference but the only people I've seen reporting this prob are those who updated manually.
Would be nice if LG listed a change log, obviously there is the 3D converter, which is cool but I'm not sure it's as good as the native stuff as people suggest, though need to play with more. I was actually getting happy with my battery on V10D, so will see how this compares over a few days,. Other than Flash Player settings not sure if anything else has been added/changed....?
charlo999 said:
Im having random restarts since update. Anyone else having this problem?
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Yes i am having the same problem,i have reinstalled sw twice and its still doing it.
Sent a message to LG about it and they dont want to know about it and blame the problem on the carriers..
I have to say my initial impression of the battery life is negative.
I went to bed with the phone almost fully charged, and as I do every night I disabled internet, wifi, GPS and refreshing and and waking up this morning my battery is 67%, that's really poor considering I was getting about %5 drop before.
Guess I will see what it does during the day, though I'm now worrying it won't last till the work day!
charlo999 said:
Im having random restarts since update. Anyone else having this problem?
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
This firmware has problems with Wifi. On an 'n' network, the phone keeps rebooting. On a 'g' network I get some reboots. Turning Wifi off solves the problem, but sometimes it's impossible to turn it back on unless you reboot...
It's a shame because the battery life with this firmware is finally 'normal' for a smartphone: 24 hours vs 7 hours before that.
My wifi is on all the time but is set to switch off when the screen is locked.
I'm not having problem at all with the phone and to be honest it's much better than before.
It seems to be running more smoothly and I can see that the battery management has improved a lot!
I'd say that I'm having the same number of hours that I had with my iPhone 4 doing the same stuff that I usually do before a recharge. So, at least for me the update has been a good thing.
Hopefully will get GB sooner than later.
I also must add that right after flashing 10k the battery was pretty bad and with the rebot problem.
After a factory reset the reboot problem was solved and the battery became super.
cheers for the tip.
What sort of data gets lost/reset on a factory default?
I presume everything gets wiped with a factory reset. So my question is if its possible to backup application settings WITHOUT rooting my phone?
Everyone seems to recommend Titanium to backup settings but I do not want to run the risk of problems with the Gingerbread update by rooting my phone, but I also do not want to lose my game progress either.
Its a shame there is no option to sync all application settings to Google servers, considering one of the huge advantages to me is that the contacts and calendar do exactly that.
I've downloaded 4 times now over wifi and every time I get an invalid software package notification and it will not proceed.
I'm on stock rom (rooted) with no Rom manager gubbins.
Strange, anyone else have this please?
I'm looking but my phone says i'm upto date on V10D??
My phones on Orange if that makes a difference?
Thanks in advance
bfpt said:
I'm looking but my phone says i'm upto date on V10D??
My phones on Orange if that makes a difference?
Thanks in advance
Click to expand...
Click to collapse
Open LG's Mobile Support and go to "Customer support > Support Model" check for Orange and you will see the version that i available for you.
The last time I saw, Orange was stuck with v10D and T-Mobile with F.
UK and Carphone are on K version.
bfpt said:
I'm looking but my phone says i'm upto date on V10D??
My phones on Orange if that makes a difference?
Thanks in advance
Click to expand...
Click to collapse
Looks like Orange is still V10D
Thanks for the info.
Still new to all this looks like orange are behind as always!!!
I take it i can't just flash another??
bfpt said:
Thanks for the info.
Still new to all this looks like orange are behind as always!!!
I take it i can't just flash another??
Click to expand...
Click to collapse
Yeah you can do it using the KDZ file or rooting and flashing with clockwork recovery.
Sorry for being a Noob I've looked but can't find a guide thats for a real noob. Only been running Android for 6 days? but the 3D convert was the main selling point so if someone could help or link I would say a big thanks.
So I have had my s3 since around the 10th and I've loved it so far. Lately I have been having issues that surly aren't annoying but on the other hand im not exactly sure if a software update would fix anyone of these things. As of now I am not rooted at all and everything is stock. These are my main problems for the phone
1.) While texting on stock messaging app (I just love the stock app) the keyboard constantly freezes up while im texting
2.) Screen flickers yet not too drastically
3.) For some reason when I try to set my custom vibration pattern it only stays as the basic call vibration and only changes when im getting a phone call.
Like I said these issues really aren't drastic and im not sure if it really warrants a replacement phone at all. I talked to the VZW tech support and she said that its up to me really because I am deff able to get one for these issues. The only thing that made me have second thoughts was the fact that she said most likely im getting a "certified like new phone" meaning that its basically been used before and im not sure if I should really trust it. Anyways im really on the fence about this so if anyone can give me some in sight id really appreciate it.
ps: I did factory resets and everything and it still has not fixed these issues
blackguy101 said:
So I have had my s3 since around the 10th and I've loved it so far. Lately I have been having issues that surly aren't annoying but on the other hand im not exactly sure if a software update would fix anyone of these things. As of now I am not rooted at all and everything is stock. These are my main problems for the phone
1.) While texting on stock messaging app (I just love the stock app) the keyboard constantly freezes up while im texting
2.) Screen flickers yet not too drastically
3.) For some reason when I try to set my custom vibration pattern it only stays as the basic call vibration and only changes when im getting a phone call.
Like I said these issues really aren't drastic and im not sure if it really warrants a replacement phone at all. I talked to the VZW tech support and she said that its up to me really because I am deff able to get one for these issues. The only thing that made me have second thoughts was the fact that she said most likely im getting a "certified like new phone" meaning that its basically been used before and im not sure if I should really trust it. Anyways im really on the fence about this so if anyone can give me some in sight id really appreciate it.
ps: I did factory resets and everything and it still has not fixed these issues
Click to expand...
Click to collapse
Sounds like something isn't right and about to go bad to me. I'd call VZW support and see if they will replace it.
Did you reflash stock image from Samsung site? I would try that before taking a chance of getting a CLN phone for the same reasons as you.
Sent from my SCH-I535 using xda premium
HHF2 said:
Did you reflash stock image from Samsung site? I would try that before taking a chance of getting a CLN phone for the same reasons as you.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
How do I go about that? im a noob flasher haha
HHF2 said:
Did you reflash stock image from Samsung site? I would try that before taking a chance of getting a CLN phone for the same reasons as you.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
They already confirmed that they are able to do so
Go-to the development sub forum and read the stickies. If it is your first time, I would even print them out and follow the instructions step by step.
Sent from my SCH-I535 using xda premium
HHF2 said:
Go-to the development sub forum and read the stickies. If it is your first time, I would even print them out and follow the instructions step by step.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Ok thanks ill do just that. My final question now is does this count as rooting my phone? just in case I do end up sending back my phone I dont want there to be any problems with it
Turn off Settings | Display | Auto adjust screen tone to address the flicker problem.
The keyboard is probably searching predictive text; I've only used the stock KB for a few minutes. Wife and I use SwiftKey without any problems (including right now).
I have vibration disabled completely, so I can't even guess on that one (I can't even find the option you're talking about and I know I've seen it before!)
blackguy101 said:
So I have had my s3 since around the 10th and I've loved it so far. Lately I have been having issues that surly aren't annoying but on the other hand im not exactly sure if a software update would fix anyone of these things. As of now I am not rooted at all and everything is stock. These are my main problems for the phone
1.) While texting on stock messaging app (I just love the stock app) the keyboard constantly freezes up while im texting
2.) Screen flickers yet not too drastically
3.) For some reason when I try to set my custom vibration pattern it only stays as the basic call vibration and only changes when im getting a phone call.
Like I said these issues really aren't drastic and im not sure if it really warrants a replacement phone at all. I talked to the VZW tech support and she said that its up to me really because I am deff able to get one for these issues. The only thing that made me have second thoughts was the fact that she said most likely im getting a "certified like new phone" meaning that its basically been used before and im not sure if I should really trust it. Anyways im really on the fence about this so if anyone can give me some in sight id really appreciate it.
ps: I did factory resets and everything and it still has not fixed these issues
Click to expand...
Click to collapse
reason #2 is enough to try and get it swapped.
That is a hardware issue, and will only get worse.
I have had a dozen smartphones, and anything that CONNECTS stuff (headphone jack to the motherboard, cables connecting screens etc) only get worse until they stop working entirely.
Good luck!
blackguy101 said:
Ok thanks ill do just that. My final question now is does this count as rooting my phone? just in case I do end up sending back my phone I dont want there to be any problems with it
Click to expand...
Click to collapse
Flashing the stock image through Odin is not the same as rooting your phone. It would not trip the flash counter so you could still return it if you wish.
stevenjcampbell said:
reason #2 is enough to try and get it swapped.
That is a hardware issue, and will only get worse.
Click to expand...
Click to collapse
If it is a hardware issue and not the setting I mentioned, I agree, definitely return it without hesitation.
Rolo42 said:
If it is a hardware issue and not the setting I mentioned, I agree, definitely return it without hesitation.
Click to expand...
Click to collapse
Ya thanks for the suggestion I tried changing the setting yet the flicker isn't going away. Like I said its nothing big and if you aren't paying attention it isn't really that apparent it is there but your right I think I better exchange it before anything happens thanks for all the advice =)
So as the title states my phone has been doing this lately and i am unsure why. This will happen when my phone is just setting there and i am not playing with it. It will also happen when i am in the middle of something which is frustrating. I want to say this happens 3-5 times a day that i know of.
Phone Info...
Verizon
Rooted with stock ROM
I deleted some bloatware apps that was said to be safe
I also deleted some files so i do not get OTA updates anymore hmmm...
I cant remember when this started happening but i am assuming i brought it upon myself lol
Freezes / Goes to Lock Screen / Status Bar is Wiped Clean / Has No Service / Then back to normal in about 20 seconds???
If anyone is experiencing the same thing i would love to hear a fix or even an explanation of what it is?
Let me know if there is any other information i can give to make this easier to answer.
Thanks!
Yeah, it's a spontaneous hot reboot. Happens to me once in a rare while too but I've yet to figure out a pattern behind it.
x-y-no said:
Yeah, it's a spontaneous hot reboot. Happens to me once in a rare while too but I've yet to figure out a pattern behind it.
Click to expand...
Click to collapse
Awesome!... well not awesome but i am glad you share my pain. May I ask... Are you rooted?
Yes. Running CleanRom 2.5. But I haven't noticed a correlation of the hot reboot issue to any ROM. Had it happen to me in Beans and also even rooted stock. Didn't have unrooted stock long enough to know if it happens there.
I was only stock for like a week or so and i don't remember it happening then but according to this forum i found people say it has happened while completely stock unrooted...
http://forum.xda-developers.com/showthread.php?t=1788211
I have deleted some apps i guess ill just wait and see, no one seems to know what causes this...
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
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