Related
The symptoms: SOMETIMES during incoming phonecalls Raphael rings (plays sound) but when I pick up the call, suddenly the phone sort of "mutes itself". I can't hear the person talking, nor can they hear me, even if I hang up and try later. The only thing that helps is a soft reset.
It's difficult to count the occurence, but I'd say like once a day at least.
I have already tried Hard reset, the phone is acting funny with only Advanced Config 3.1 and PHM RegEdit installed and a few tweaks applied (just Boost TFL3D performance tweaks and SMS conversation disabled)
I'm running stock 1.90.401.1 WWE FW, I have flashed a new radio version (1.02.25.31 Cingular) though.
Any advice/suggestion is appreciated.
Unless the new radio is giving you 3G, I'd go back to the stock ROM/radio combination and see if that works. I'm currently using the Cingular ROM/radio as well and I've never run into these problems, but that may be due to different hardware.
Thank you very much for a quick reply.
I'll try flashing the stock radio and will report back...
So, I flashed the original radio and it seemed for a while that the problem was gone.
Sadly, I must report that the problem is persistant as I had to restart my phone right now. When the "sound mute" thing happens I don't hear anything while answering phone calls (even though the phone rings normally!) and also when I try calling any number from my contacts including the operator hotline.
I really don't want to return the phone because I like it very much but having a phone which has problems with phone calls is kind of silly.
I'm at my wit's end.
Will anyone help me please?
I have a small update - today I was so desperate, that I tried flashing a custom ROM (namely DCS-TouchPro-v1.0 Hybrid) and the phone went bonkers right at the first incoming call. However, something IS different - now the phone is not silent but starts "buzzing" - making a long uninterruptible sound that lasts until reset.
Do you think I could have a HW problem?
I HAVE EXACTLY THE SAME PROBLEM!!!
I already posted a message in the "Issues" post of the Raphael Forum, but apparently no one had the same issue so far.
I did many hard resets (and installing gradually less things), it still bugs.
Currently the only tweak installed is the scorpion one to have 4 rows of icons in a menu.
My Raphael is behaving like this since 1 week. The bug occurs once or twice a day as well.
Anybody with some good IT experience has got an idea of what could be wrong with it?
Do you think it is more software related or hardware related?
Today it also crashed badly (grey doted screen and noway to make it work again by turning off. Had to soft reset).
PLEASE DO HELP US, because I'm using the phone for professional reasons and I'll really have to send it back if it keeps on bugging this badely!!!
I just sent a message to HTC Support.
Let's see what they say.
I'll post their response so those who have the same problem will know what to do.
Oh boy, I must say I'm glad not to be the only one with this problem, even though I never wish bad things to anyone.
While googling the problem, I found a few Diamond users with exactly the same symptoms, however most of them solved this by exchanging the device for a new one, so this won't help us much...
Me too, I was wondering if it was because I did something wrong with the phone...
But if I'm not the only it means that there is a problem with the phone itself.
Anyway I'll wait for the official answer from HTC...
I'll post their answer as soon as I receive it.
I'm actually quite curious what their answer will be.
But I wouldn't hold my breath for any miracle, so I'm preparing to send my phone to the service center to have them look at it...
Well.. that makes 3 of us then
at first i thought my symptoms are different, but Flippy confirmed they're identical.
http://forum.xda-developers.com/showthread.php?p=2611523#post2611523
I have to correct myself - I wrote that when the thing happens, the phone still rings, which is not true. It rings just the first time before the problem occurs, but then it's dead silent.
So it seems our symptoms really are exactly the same.
Told ya AntiProxy!
So we are indeed only 3. It is still ok, it means that there is only a very small proportion of of Touch Pro that have this problem.
Now let's only wait HTC's answer...
spoke to HTC support today.
not that i expected them to figure it out or have a solution at hand, but i figured what the heck.. give it a shot.
their solution?
hard reset.. the guy would swear by his daughter that a hard reset will solve it.
i just thanked him and hung up.. *sigh*
don't you just hate it when techsupport's solution to everything is a reboot or reformat.. when you know that's not the solution anyway!
Well, I tried already doing the "Clear Storage" through the settings -> system panel, but it still has got the same problem.
I'll give them a call aswell to see if by any chance I can get on the phone 1 person who will be able to provide us a better technical advice
Hard reset won't help, I've already done it like dozen times and it makes no difference...
I tried flashing the phone to the stock 1.90.405.1 ROM and so far (a day and half) I have NOT encountered the problem. It is too early to start hoping, but I wanted to let you know - if you don't mind flashing your phone, give it a try.
Zillator, can you keep us posted for like 1 week?
If in 1 week the phone doesn't present again that problem I'll flash it as well (I didn't want to flash it because I wasn't sure if it could void the warranty). If during 1 week you don't have the problem again it'll mean that out initial ROM was defective...
Thank you Zillator and please let us know. (by the way when I'll call them tomorrow I'll ask them if flashing the ROM to a newer stock version voids the warranty).
Zillator said:
I tried flashing the phone to the stock 1.90.405.1 ROM and so far (a day and half) I have NOT encountered the problem.
Click to expand...
Click to collapse
only thing is.. my phone is still running the stock ROM as it is!
AntiProxy said:
only thing is.. my phone is still running the stock ROM as it is!
Click to expand...
Click to collapse
AntiProxy, it might be a bug in the ROM we have in our machines. That's why maybe flash it could be the solution. Nevertheless I'll ask about the warranty tomorrow when I call them and let's see how it goes to Zillator.
If his phone doesn't bug for 1 week, there might be a big probability that the problem came indeed from our ROMs.
Guys, don't worry, I WILL keep you updated. I know how much the problem bothers me, so if there's anything I can do to help you, I will definitely do it.
In the end, that's why we are here - to help each other...
AntiProxy: is your stock ROM 1.90.405.1 WWE? Because mine was different (1.90.401.1 WWE) and I had the problem. Maybe Flippy_TK is right and the problem only exists in the 401 ROM.
I'll continue testing and we'll see...
this problem has been bugging the heck out of me. I only noticed it once I flashed custom ROMs. I may go back to the ATT rom or chadsters stripped ATT rom if need be.
it happened on all versions of EnergyROM I have used over the last few months and on hergs new wm6.5 rom as well.
my talk and end buttons just seem to stop working sometimes and act as the home and back buttons respectively when they fail. Sometimes even the back and home buttons stop responding and the whole area aside from the dpad is useless. This only happens after a while and a soft reset temporarily fixes the issue...until something triggers them to stop working again.
this is causing me extreme frustration with my Fuze that I otherwise love...
is anyone else having this issue? is there a fix? if not, I will try just moving back to a stock ROM and see if it happens.
Yes, I have the exact same problem on the same roms.
Turning the screen off and on again seems to fix it for me.
I am using the stock ROM and have this issue.
Moved to the Raphael subforum
same problem
i have same problem..yesterday i flash new EnergyRom Genesis and 1.14.25.05 radio..and all my buttons except hw keyboard stop working (volume up,down,back,home,answer call,end call button stop working)..so i falshed back older EnergyRom and its still not working (older EnergRom was ok, everything worked fine for me), some people have same problem and solve it by flashing back stock rom, but i tried so many original stock rom and cooked rom with combination with many radio and soft resets and hardresets..and its still not working...i dont have warranty now-so i dont know what to do...but iam sure-that it is software problem..but dont know what to do..please help me..
I had the same problem, twice. I don't know if it is EnergyROM that causes this or that its just because so many people flash EnergyROM that they notice it and think it is what causes it.
My first time also started shortly after flashing my first EnergyROM, when my FUZE was about 5 months old. No matter what I tried flashing, hard resetting, anything I couldn't fix it. So I reverted it to stock and had AT&T replace it. The second time this happened was also about 4 months after I got my replacement. I was also running EnergyROM, but I had been running the same ROM and hadn't flashed for over 2 months when it started again. Once again, I had to get it replaced under warranty.
I assume this problem isn't very widespread and don't know if it is a hardware fault or if flashing ROMs someway changes something that isn't always changed when flashing ROMs. This may even be an AT&T specific issue. I would recommend just calling and having it replaced, everyone who bought it new still has warranty, and hopefully if you bought it refurbished it isn't over 3 months old.
Since I have had this issue twice and they sent me DOA replacements 2 times, they offered to give me another phone last time I asked for a replacement. They offered the Epix and the Incite, which I declined and took another FUZE instead. I told them to note it on my account. I am going to try getting my FUZE replaced with a Touch Pro 2 once that is at least 1 month old.
thanks very much for your reply...iam from czech republic..every from my last five WM phones i bought in czech republic was new from T-Mobile..but i lost my first touch pro (it cost me 600euro)..so i decided to buy second touch pro in england, when i was there on holiday (prize only 200euro- but second hand)..now iam back in czech republic, buttons on my touch pro dont work and i dont have warranty i loved energy rom..but i think, that it is reason, why my touch pro dont work
I have the same problem with my Fuze (using NATF 4.5 ROM). I don't think it's a software issue. I think it's a malfunction of the capacitive touch sensor (NAV sensor) that controls the entire bottom panel of the phone (HOME/BACK/TALK/END and Smart Touch wheel). Search for a tool called navdbgtool.exe. It lets you see what inputs are registered by the panel (e.g. where it detects a touch or which buttons are pressed). Mine sometimes works fine but randomly malfunctions (zoom functionality is broken, buttons do not perform the proper commands).
Same here!
I only have flashed Shep's and Timolol's ROM.
what is wrong?
i'v seen somewhere on forum for blackstone, that hard spl can cause weird problems like that, maybe touch pro needs 'bios' update?
it's just a thought, as i've got same problem... really annoying ####!
I have the same problem!!!! I thinked that was a hardware problem but now that I have read all your post I think is a software problem, because I'm using ENERGYROM with sense 2.5 and zoom function is broken and I have the same problems with all keys......I don't now waht to do.....Any ROM fix this problem??? I open a new post, please check:
http://forum.xda-developers.com/showthread.php?t=596314
Glad to know that others are having similar problems. Just flashed to the latest version of the EnergyROM and having trouble with the Talk key.
A soft-reset seems to fix it for awhile, then it randomly stops working. Haven't had time yet to either hard-reset or flash back to the previous version. Will try that when I get time.
I do suspect it is a software issue. The key press is registered, something is making it do something else. So the solution for me is using Tarkim's Keyboard Config, having it map that key to Talk. Works like a charm!
Okay, finally had a chance to do a hard-reset. The buttons now work like a charm and overall, things work much faster. Not sure what the deal was, originally went through the proper steps to flash, including a hard-reset afterward...
I'm glad that you solved your problem....but please where I can get the Tarkim's Keyboard Config?? I did a hard reset and nothing happened!!! Thanks for your help.
Sorry, didn't have the link handy at the time. Here's the thread about it: http://forum.xda-developers.com/showthread.php?t=521786
to resolve my issue on this thread...
I took my phone in for warranty replacement due to this issue. I got a new phone, flashed the ROM I was having issue with at the time and have not had a problem since on any ROMs
I have the latest "stock" rom installed and I am having the same problem. Hard reset or soft rest doesn't permanently fix my problem. Also my navigation "wheel" in the middle will sometimes go bizerk while typing texts, in the form of zooming all the way out and zooming all the way in...very fast. Never understood that button. I don't use the bloatware. Seems like a hardware problem to me?
Another feature that has stopped working as of lately was is the selecting of multiple email msgs with one finger swipe... I have to use the shift button to select multiple msgs.
Seems that HTC has stopped supporting the fuze, as there is no support on their website?
Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.
Probably a sticky power button. Although the camera flash is weird. It's a common problem. Search stuck power button
Sent from the short bus
Ya I figured that thought I'd ask thx I'll have to grab a #0 phillups tomarrow
I had this exact same issue on the UCLL3 leak for AT&T. I got out whenever I would flash gs2user's mods on top of the odexed stock version. It required me to reflash my ROM.
Sent from my SGH-I727 using xda app-developers app
Well I've reflashed stock rogers and wiped 3 times before and after flash so I hope that fixes it skyrockets not my daily driver but my friendwants to borrow it so I hope I fixed it up
xstokerx said:
Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.
Click to expand...
Click to collapse
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure
phone reboots and vibrates
tobesedated said:
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure
Click to expand...
Click to collapse
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)
as-ny said:
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)
Click to expand...
Click to collapse
Seems odd to me that it would be a sticky power button for one ROM and not another, but then I can't figure for the life of me why mine worked fine and his didn't. Twilight phone zone lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Ya so I cleaned mine and still it does it I odined back to stock still dose it I'm at my wits end its pissing me off
OK so I odined back to stock factory reset stock then flashed twrp in odin then updated twrp and flashed the super light cm10 with gapps haven't had a reboot yet fingers crossed that it worked must be a software thing I got no clue.
OK update my phone started doing this again to day did it like 6 or 7 times FML its defently a hardware problem.
I'd have to agree that it's a hardware problem
I wiped my phone shortly after my post and did a clean install of seanscreamz newer ROM as well as TWRP. Problem continued to happen...actually worse than before. But at that point I had yet to put a single app on it, so an issue of incompatibility of my apps and ROM did not seem to be the case. I then wiped my phone AGAIN, and di a clean install of CWMR and CM10 (I went from ICS to JB), figuring maybe a TOTAL change would do the trick. Not the case.
The phone still randomly reboots, but now that I am certain it is a problem with the power button, I know how to deal with it, and can minimize te recurrence and my frustration levels. I read a post that said someone else had the same problem, and smacked his phone on his desk repeatedly on the power button, and the problem stopped. I didn't do that, but when the problem occurs, I will repeatedly hit the bower button, or if my otterbox case if off, I will stick my nail into the button to pull it out.
It's too bad, 'cause it's a great phone otherwise!
I got an app called tap tap tap and it uses the proxy sensor to unlock the phone and adds a widget in the notification bar to lock the phone works great then my power button does not get stuck Cuz I don't need to push it.
hi everyone - not a new issue, but seems like most ppls phone has this figured out now after 44s.
Getting ghost touches and very slow/laggy scroll/swipe response...basically have to press and drag the finger to get anything working.
Currently running stock CM11s 44s with a locked bootloader, completely flashed back to stock using the zip file from cyanogens website. but i have tried CM, Omni, paranoid, and have tried diff kernels including franco, but it doesnt seem to wanna work.
here is a link to my screencast - kinda hard to see but i tried to record what happns when i imitate typing.
https://drive.google.com/file/d/0B1quWiDbFcajdkdTaGhwZzc4M1k/view?usp=sharing
any help would be appreciated! i have seen other posts on this, but nothing seems to be working! what am i missing!?!? :crying:
I have seen other people complain about this and it seems to be a bug, there is no fix at the moment. Wipe the screen clean with a microfiber/lint free cloth while the phone is off. If you think it's hardware damage then use your warranty and send it in.
hmm. I have contacted one plus and have submitted a ticket a while ago, but they are extremely slow in responding. its been over 20days now. Since the touchscreen works fine for the first 15 20mins, i thought it would be a software issue that i could somehow fix....
There will be a new Touchscreen firmware soon
nice!! where did u hear/read this? any ideas when?
hassan3216 said:
nice!! where did u hear/read this? any ideas when?
Click to expand...
Click to collapse
it's a known problem. I have it too. I don't think a firmware update is going to fix it.
http://gadgets.ndtv.com/mobiles/new...defect-affecting-touchscreen-digitiser-625211
https://forums.oneplus.net/threads/touch-screen-issues-were-listening.186829/
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