Related
i need to know if this a hardware issue or software. every 2 days or so my camera wont start . i close everything running and it just freezes up on me. i have nothing crazy installed jsut root, tibu, chase, android game, flashlight. thats it ! i will click the camera icon ill see the screen shake for a second and just go back to home screenl. also sometimes i click the multi task button and clear everything out when i press home it has to load all my widgets again.. this phone is werid...
i bought it online at radioshak for 50 bucks do you guys think i can get a new one in store or do they deal with online only
I had this happen to me twice in a week of use. I'm wondering if another app is not releasing the camera from it's use. I haven't been killing the camera app after use, so maybe it has an issue being open for long.
Other apps that use the camera I may have had open are Instagram, Facebook, Gallery.
zaisaroni said:
I had this happen to me twice in a week of use. I'm wondering if another app is not releasing the camera from it's use. I haven't been killing the camera app after use, so maybe it has an issue being open for long.
Other apps that use the camera I may have had open are Instagram, Facebook, Gallery.
Click to expand...
Click to collapse
same. its either gallery or instagram, hmmm
i had this issue since i bought the phone. never figured it out. a couple of days ago, the camera just stopped working altogether. it won't start most of the time. when it does start, the image is dark and very distorted. i tried to upgrade from 1.73 to 1.85 and didnt solve the issue. i did a factory reset and it didn't solve the issue. so earlier today, i ended up just exchanging it with a new phone.
Happening to me as we speak!
Made a quick, nasally sounding video.
http://www.youtube.com/watch?v=X4hDD-hMiF0
- Instagram is still able to use the camera.
- If I close them all in multitasking, it doesn't fix it.
- Force stopping Instagram and/or the Camera app doesn't solve it, I have to reboot the phone.
EDIT:
Fast boot is off on my device.
unsp0ken said:
i had this issue since i bought the phone. never figured it out. a couple of days ago, the camera just stopped working altogether. it won't start most of the time. when it does start, the image is dark and very distorted. i tried to upgrade from 1.73 to 1.85 and didnt solve the issue. i did a factory reset and it didn't solve the issue. so earlier today, i ended up just exchanging it with a new phone.
Click to expand...
Click to collapse
damn so you think it is hardware related ? i bought the phone may 9th it arrived to my house , am i still under warrenty or what is radioshak 30 days hmm
Happens to mine too, about 4 times already. Have to restart the phone to get it to work again. Had the phone for about a month. If the update fixes this and other problems this phone will be perfect.
Crizthakidd said:
damn so you think it is hardware related ? i bought the phone may 9th it arrived to my house , am i still under warrenty or what is radioshak 30 days hmm
Click to expand...
Click to collapse
Try a factory reset. If this doesn't solve the issue, I'd take it back. I've never had any such issues on 1.73, 1.82 or 1.85. I'm inclined to think its either a software issue (like an installed app interfering, as one reply suggested) that a factory reset may clear up, or its a hardware issue.
Crizthakidd said:
damn so you think it is hardware related ? i bought the phone may 9th it arrived to my house , am i still under warrenty or what is radioshak 30 days hmm
Click to expand...
Click to collapse
well, i won't say that your problem was the same as mine but i think mine was definitely a hardware problem. i experienced the problem on 1.73 and 1.85, rooted and unrooted, locked and unlocked, and even after a factory reset. luckily the camera just complete crapped out before my 30-day was up so it was easy to justify the exchange at the at&t store.
zaisaroni said:
Made a quick, nasally sounding video....
Click to expand...
Click to collapse
Video exactly depicts what happens to me. I will try to open the camera app and it just flashes and kicks me out. I've tried all sorts of things to alleviate the problem but the only solution I've found is restarting the phone. Pretty annoying....
The display HOX at the AT&T store had the same issue. I'm assuming this is software related but who knows
this happened the first week I had the phone. When I updated it to 1.82 the issue went away so I'm assuming it was software
Sent from my HTC One X using XDA
Did you ever find a solution to this?
redpoint73 said:
Try a factory reset. If this doesn't solve the issue, I'd take it back. I've never had any such issues on 1.73, 1.82 or 1.85. I'm inclined to think its either a software issue (like an installed app interfering, as one reply suggested) that a factory reset may clear up, or its a hardware issue.
Click to expand...
Click to collapse
Well if it was a software issue, factory reset is worth a try. However if its something that needs to be fixed in a future update (a bug) then going back to factory shouldn't help. And thats why the OP had another thread about how to update.
Crizthakidd, have you tried other camera apps from google play? I know you said you were going to. How did that go, if you did? Obviously if there's a software issue, even if factory reset doesn't fix it, xda can. That is, root, unlock, install a newer custom rom.
I had this problem on 1.72, and other apps were still ok using the camera. I made a quick video of it happening.
https://www.youtube.com/watch?v=X4hDD-hMiF0&feature=youtube_gdata_player
***Ever since the 1.85 OTA it hasn't been happening so I would suggest HTC fixed it. ***
However I am rooted and doing mods so I am restarting more often to check my work.
Sent from my HTC One X using XDA
My wifes Moto G occaisionally crashes and reboots. It hasnt happened very often but I would like to know if it is happening to anyone else and if they know the cause? Maybe it's a bug that will be sorted with a future software upgrade?
The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.
vrsk said:
The same is happening to me right now, I'm running 4.3. Sometimes it becomes very annoying; I already contacted Motorola through, they're supposed to call me later today...
I hope that KitKat solves this issue because I don't want to root yet.
Click to expand...
Click to collapse
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.
ahardie said:
Ah so it's not just us then. I hope that an update will cure it as I doubt that my wife would let me root her phone. Will be interesing to see what Motorola say.
Click to expand...
Click to collapse
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
I'll report with the results later.
vrsk said:
Mine even reboots during the start-up animation, it has become so annoying. A shame since it is a great device
Click to expand...
Click to collapse
That must be really annoying. Luckily ours isn't that bad.
vrsk said:
I'll report with the results later.
Click to expand...
Click to collapse
Cheers.
Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....
llyenn said:
Same issue here. Got the device, (US GSM) on Dec. 14th, and had it happen a couple of times. I didn't think anything of it, because this phone is for my son, and I was trying out parental control stuff on it. I wrapped it, and it sat under the tree till the 25th, which is when I updated it to 4.4, and the crashing has gotten worse. I get random app crashes, and more reboots now than ever. I cleared the partition cache, which didn't work. I am going to try a factory wipe and see if that fixes it, but I honestly doubt it. Moto chat told me to call in the morning to talk to a level 2 tech.
So, there seem to be a few of us, but I didn't see anything on their support forums....
Click to expand...
Click to collapse
So far I've had a single instant reboot in the camera app. Hope it doesn't get worse.
The phone is still rebooting sometimes. Is there any way I can check why it is happening like something that will create an error log? Or does anyone have any tips for stopping it happening? It is a very minor nuisance at the moment but I'm afraid it might get worse. Especially if it is a problem with the hardware rather than the software.
I have a UK moto g and it hasn't rebooted on me yet the past week I have had it
Sent from my XT1032 using xda app-developers app
I've got the International 8 GB version from Koodo and it hasn't rebooted since I started using it full time on Dec 28. It remains powered up 24/7.
Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.
I have same trouble. My device is crashing and rebooting sometimes at day. Is there any solution??
Moto g purchased in mexico, telcel.
Guys, return it to your phone dealer if you can. Waiting for a fix(that may or may not come) will just increase your pain. If the service center spots the restart, they should definitely repair/replace your phone.
gee2012 said:
Often these reboots and crashes are user app related, it may be a good idea to data factory reset the phone and see if the issue remains.
Undervolting the cpu may cause these issues too if you undervolt too much.
I have 120 apps installed and had no crash/reboot so far in the 3 weeks i had the phone.
Click to expand...
Click to collapse
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.
Kit kat seems to have fixed problem.
dankerk said:
Yes it could be but I think it's most likely Android OS or Motorola's own certain app that's causing this. My device resets so frequently that's it become impossible to use, unbelievably it reboots every 5-10min, even when I leave the phone on standby I see it rebooting it self.
It's no just specific app that I use, it has rebooted while I'm browsing (Google Chrome), in Gallery app, on Play Store and also when I was transferring images from pc to the device!
Motorola Chat support are useless, they just game me links to Moto UK Support contact, that's it. Not much of advice.
So I will be taking it back to Phone4u store and possibly get it replaced if they can.
Click to expand...
Click to collapse
My wifes phone seemed to be getting worse. It rebooted four times the day before yesterday. It always seemed to be worst when we were travelling.
Yesterday morning the Kit Kat update became available. The phone hasn't rebooted since. Hope I'm not speaking too soon but fingers crossed it seems to be fixed.
We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?
creambyemute said:
We got 2 Moto G's in our family (one for me, one for my father), both ordered from Amazon.de as 8gb version (XT1032)
I haven't seen any reboots on one of these devices. They both got updated to 4.4.2 yesterday and also no crashes.
Has anyone found out what is causing the crashes? Is it maybe even a hardware failure?
Click to expand...
Click to collapse
If the Kit kat upgrade has cured the problem on my wifes phone then it must have been software related. Possibly an app I had downloaded was causing it. It's worth pointing out as well that most people didn't seem to have this issue.
BTW I spoke to Motorola chat a few days ago using the help app. on the phone. They told me it was probably an app I had downloaded causing it and a factory reset would sort it. Installing the upgrade seems to have done the same thing though.
Happy to hear it's not something hardware related.
I even had reboots with my nexus 5, 4 on random basis (not often). Must be some sort of app I've had installed on all my devices
I received mine in december (from Amazon [Retail.FR]) and experienced some crashes (almost every day).
I installed KitKat on it and did two factor resets to be sure it was not software related issues. Since then, a week ago, I experienced a crash every day and half (screenshot). Crash happened without any reason or specific context.
My serial number is: TA8900B6##
I decided to return my Moto G to Amazon and buy a new one.
I'm experiencing the same and I decided to try to run a constant logcat in the background to see what's going on. Also is there any way to have a constant recording with dmesg? I'm no linux commands expert.
For logcat (in terminal emulator) I used logcat > sdcard/logcat.txt which is growing in size as far as I can see. Hopefully this brings some news.
Good luck everyone.
Cheers
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Software. Have to wait for an official fix
Sent from my A0001 using Tapatalk
sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
The problem is in the touchscreen firmware and the fix have to be released from synaptics and not frome Oneplus.
The fact is that it may take a few or a long time based on the issue and it may be enven never be fixed, who knows.
As now i am really disappointed. They should have never release da device knowing of such a major bug.
ky3bmu4 said:
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
Click to expand...
Click to collapse
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
sjhotwings said:
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
Click to expand...
Click to collapse
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
ky3bmu4 said:
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
Click to expand...
Click to collapse
try slimsaber , it worked very good for me . and hope it work for you too
sjhotwings said:
try slimsaber , it worked very good for me . and hope it work for you too
Click to expand...
Click to collapse
I'm not sure if this is the same issue, but when you run a touch screen test, does it work with more than one touch? IE is multitouch working? I had an issue the other day and I resolved it by turning off the phone, attaching it to the charger and then turning it back on (read it on the oneplus forum). It is a known issue and they are working on bringing us the fix.
Hope this is helpful.
I have this issue too, although it's been mitigated somewhat by the most recent software patches they pushed in 30O and 33R. I'm on a CM nightly at the moment and it's certainly usable. I made the issue a lot better by disabling haptic feedback in the SwiftKey settings - it almost feels like that extra effort to run the vibrating motor causes the screen to respond badly or something.
Is it doing this?
http://youtu.be/XsGPsDP4V0U
If so this is what mine is doing and it's soooo annoying trying to type.
http://www.androidheadlines.com/201...ti-touch-issues-oneplus-one-fix-incoming.html
Some-not me, have been able to mitigate the problem by running a code through terminal emulator.
This has been brought up in CM bug log as Bacon 55.
You don't have to be rooted to do this.
Type: su (if you're rooted)
Type: cat /sys/class/input/input0/baseline_test
Press enter.
Note that you will need to do this every time you reboot your phone.
Credits to a member on jira cm. Forgot to name! Hope it works for you
I've tried everything and everything failed.
Let's hope synaptics pushes out a fix soon. I can't stand this issue. Basically two different touches near each other are recognized as a swype -_-'
i did a test using multitouch test app. i use 1 finger touch on the phone and got a red dot, finger #2 gave me a blue dot . as soon as my 2 fingers get close together 1 of the dot disappear, also test w/ 4 5 fingers same result .thats why if you text really fast , you get alot of missing words and sometime it lag and get stuck.
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Here is a fix I have tried and it has helped me a lotttt.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com
DuckMcQUack said:
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Click to expand...
Click to collapse
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
alhadee12 said:
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
Click to expand...
Click to collapse
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
DuckMcQUack said:
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
Click to expand...
Click to collapse
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
alhadee12 said:
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
Click to expand...
Click to collapse
Definitely. I would stay away from this thing.
And by the way who knows if the ghost touches/swypes problem is not even a software issue just as the multitouch not working when placing the phone on a non-conductive surface...
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
Does anyone have any ideas how to find why my phone is rebooting randomly? I'll check it periodically and then it will have a bar stating it's starting. Then my launcher loads and no icons and I need to wait a minute. I don't know exactly what's going on. It appears the phone is randomly rebooting.
Have you tried a factory reset? Are you rooted?
I just factory resetted it and rooted it a few days ago. I got to thinking I think the rebooting started after I throttled the cpu trying to save battery. I just changed the cpu governor fro ondemand to scheduled. So far it seems to run faster but I'm sure the battery will be worse but we'll see if the crashing ceases.
Crashed and rebooted 15 minutes ago. So, changing cpu back didn't fix.
Flash the 100% stock image and try leaving it that way. If the problem doesn't occur, it's something you're doing/flashing/changing that's the cause of the issue.
Obviously I know it's not a hardware issue.... so I know a 100% stock would fix it. I'm trying to figure out how to fix it without putting it to stock.
dorlow said:
Obviously I know it's not a hardware issue.... so I know a 100% stock would fix it. I'm trying to figure out how to fix it without putting it to stock.
Click to expand...
Click to collapse
Just so you know, mine started freezing/rebooting after the May update on stock everything. I think that update has issues.
rft183 said:
Just so you know, mine started freezing/rebooting after the May update on stock everything. I think that update has issues.
Click to expand...
Click to collapse
never had freezing/rebooting issue with mine.
mngdew said:
never had freezing/rebooting issue with mine.
Click to expand...
Click to collapse
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
rft183 said:
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
Click to expand...
Click to collapse
Is this freezing/rebooting Verizon specific issue?
mngdew said:
Is this freezing/rebooting Verizon specific issue?
Click to expand...
Click to collapse
I don't know. That was the only change that I'd made at the time, though. It's gotten really annoying, so I've flash PureNexus with ElementalX to see if that would make a difference. I haven't been using it long enough to say one way or the other.
rft183 said:
I don't know. That was the only change that I'd made at the time, though. It's gotten really annoying, so I've flash PureNexus with ElementalX to see if that would make a difference. I haven't been using it long enough to say one way or the other.
Click to expand...
Click to collapse
I'm also on Elemental X kernel with slightly overclocked cpu. Does the freezing/rebooting take place while in idle?
mngdew said:
I'm also on Elemental X kernel with slightly overclocked cpu. Does the freezing/rebooting take place while in idle?
Click to expand...
Click to collapse
I flashed PureNexus on Friday and used its default kernel over the weekend without any troubles. I've only now flashed Elemental X this morning. Time will tell, I guess!
Edited to add: When I was on the stock rom and kernel, it was freezing while I was using it, requiring me to restart the phone. I would also go to use it after it had been asleep for a while, only to have it do the "Android is Starting" thing. So yes, it was restarting at idle as well as when I was using it.
rft183 said:
I flashed PureNexus on Friday and used its default kernel over the weekend without any troubles. I've only now flashed Elemental X this morning. Time will tell, I guess!
Edited to add: When I was on the stock rom and kernel, it was freezing while I was using it, requiring me to restart the phone. I would also go to use it after it had been asleep for a while, only to have it do the "Android is Starting" thing. So yes, it was restarting at idle as well as when I was using it.
Click to expand...
Click to collapse
Well, I guess the problem with my phone was unrelated. It completely died yesterday afternoon. I'm doing the RMA thing with Google now.
I started having this issue with Android O
I have unlocked version.maybe an app, I'm going to do a reset
rft183 said:
I seem to be seeing a lot of people complaining about the issue. It's been an issue with the Pixel since the beginning, apparently, but it seems to have gotten worse with the May update.
With that said, I did make another change around the same time... I had switched from Project Fi to a Verizon MVNO, and so I flashed the Verizon system image (from the Google Factory images page) rather than the standard one, since it supposedly had some Verizon-specific fixes.
Click to expand...
Click to collapse
Well, after getting the phone back reloading the stock image and re-rooting it, I went into developer options and turned off ota updates. So, hopefully I don't get that update... even though root doesn't allow to update. Just causes annoying update prompts.