I am so excited about the OnePlus One, but after reading through the threads, I just would like to know if the following issues have been fixed in the official firmware:
- Poor call quality
- GPS lock issue
- keyboard ghost swipe
I am about to place an order, but if these issues still exist, I think I will be looking else where.
1. You mean low call quality? Been fixed for awhile now.
2. Never knew there were GPS problems.
3. Fixed in latest ota. Has been around for awhile in custom kernels.
mbushnaq00 said:
I am so excited about the OnePlus One, but after reading through the threads, I just would like to know if the following issues have been fixed in the official firmware:
- Poor call quality
- GPS lock issue
- keyboard ghost swipe
I am about to place an order, but if these issues still exist, I think I will be looking else where.
Click to expand...
Click to collapse
I'd have a read through the forums and don't forget that people with problems will sound louder than people without problems. The only problem I had was sometimes I had to tap twice for the tap to register and since the 38R update it hasn't happened at all.
I don't have any yellow tint but I did on my other 1+1 but it was very minor.
No issues here since day one. I've been around since the second to last update, 33R. I have been running custom kernels the whole time though so maybe that's why I haven't noticed any touch screen issues. Call quality has always been fine for me as well.
I did have trouble getting a GPS lock one time, but then every phone I've ever owned has had occasional difficulty with that. So long as it only happens once in a blue moon I'm happy.
Mmm bacon
Got my 1+1 a couple of days ago => yellow tint on bottom
Inviato dal mio A0001 utilizzando Tapatalk
Related
Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
drakester09 said:
Sounds like
http://forum.xda-developers.com/showthread.php?t=2832822
Click to expand...
Click to collapse
It is different than ghost-touches.
I noticed there is a topic on xda about this problem already: Click
I hope this can be fixed with a software update.
joeyzbg said:
Hi there guys,
I've been researching on this problem i've got with my Oneplus. It seems that the touchscreen is'nt responsive enough.
Often when i'm scrolling trough (for example) facebook, the phone has a hard time recognizing my swipes, and picks up regular touches instead. Which is causing me to open or like posts when i'm just trying to scroll trough. If i'm scrolling trough my homescreens while just slightly touching the screen, it acts up really hard.
The screen just isn't responsive enough imo.
I'm wondering if other people got the same issue, and if it is hardware or software related.
See this topic for more information: Click here
Click to expand...
Click to collapse
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
DuckMcQUack said:
Funny. I have my oneplus one since a week ago more or less and i also noticed this issue in the very first days of use. Now i've opened facebook app to make some scrolling and see if the problem is still there and i have to say that i don't notice it anymore. Strange, but this is what i feel O_O
Click to expand...
Click to collapse
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
joeyzbg said:
Hmm, maybe you just got used to press a bit harder onto the screen (which helps). Would be great if it's really disapearing after a while
Got mine for 3 days now.
Click to expand...
Click to collapse
It really may be...just get used to New display settings and you will be out of problem too then!
Inviato dal mio One utilizzando Tapatalk
I have the exact same issue with my OnePlus after 3 weeks of use. At first it was the swype issue where the phone wasn't picking up swypes properly on the middle left side of my screen. I use a pattern unlock so it's annoying when the dots don't connect.
The next thing was not picking up my touches properly so when ever I use SwiftKey and they recommend words, I could never properly select it because the touchscreen wasn't registering properly.
I did a factory reset and it solved the problem at first but it's now back after 2 days. It's not as bad as before but still persistent. There are tons of people on Redit, Cyanogen and the OnePlus forums that are reporting the same problem.
The good news is it seems like a software and not hardware issue, hopefully the permanent fix can come soon.
Possible solution to the supposed OnePlus One touch sensitivity problem
Settings→Developer Options→ Scroll About Half Way and UNcheck "block gesture touch events"
Also try and see if unchecking "Adaptive backlight" in Settings→Display & lights→ Adaptive backlight, helps.
Of course none of these are permanent solutions. And this problem is real. But maybe the "solutions" above help.
ive not had these issues just yet. but i do get annoyed by gesture control
This still needs to be addressed. It's almost as bad as an old capacitive touch screen!
I got my phone maybe a month after it was released. After exactly 4 months the touchscreen input died and lost all sensitivity. Typing became impossible. After going back and fourth with support for 2 months they finally sent me another one. The new one was excellent for EXACTLY FOUR MONTHS!! Almost to the DAY! My damn touch is broken again and I can't type. I'm furious! I'm also 1wk outside warranty.
With the first phone I tried every hack, crack, rom, reformat, anything I could find. Nothing would restore the touch. I assume it's a hardware issue. I've been looking around for a solution but haven't found anything. If there is anything, I would appreciate some direction.
Sorry for everyone that ever wasted their money on OnePlus, I won't be getting any more products from them...
When playing around with yamtt on this phone and another, I noticed this phone only had any bugs when:
1. Whenever any 2 touches aligned latitudinally or longitudinally the touches went haywire.
2. Whenever more than 4 or 5 touches were registered at one time, adding any more caused issues fairly often.
Since I have purchased one of the more recent units I'd assume that the so called grounding issue is not a fault but I can't confirm that since I'm not going to crack open my device. These also happen regardless or kernel I am using on 11s, Stock, Franco, and AK.
If anyone can use this info, help yourself. I don't know if it has been reported yet but I've been bored on my day off. Thanks.
bukithd said:
1. Whenever any 2 touches aligned latitudinally or longitudinally the touches went haywire.
Click to expand...
Click to collapse
Had this one too, but it didn't appear in an other touchtester (it should even fail with 3+ touches)
bukithd said:
When playing around with yamtt on this phone and another, I noticed this phone only had any bugs when:
1. Whenever any 2 touches aligned latitudinally or longitudinally the touches went haywire.
2. Whenever more than 4 or 5 touches were registered at one time, adding any more caused issues fairly often.
Since I have purchased one of the more recent units I'd assume that the so called grounding issue is not a fault but I can't confirm that since I'm not going to crack open my device. These also happen regardless or kernel I am using on 11s, Stock, Franco, and AK.
If anyone can use this info, help yourself. I don't know if it has been reported yet but I've been bored on my day off. Thanks.
Click to expand...
Click to collapse
I already reported it a while back but so far there hasn't been a response from cm
sent from my amazingly awesome OnePlus One with Stereo Mod
Don't forget to hit thanks!
I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.
Elvecio said:
I blamed OnePlus for months for not doing anything for the annoying problem related to the touchscreen panel in a lot of models of the OPO. I was sure it was an hardware problem and only a RMA could have done something for me. I couldn't return my phone cause i always need it and i didn't have alternative phones to use. So i just gave up, living with some not-extremely-frustrating-unresponsiveness during fast typing.
But...
After installing the last official CM11S update (the 05Q one), i noticed some strange responsiveness during a chat with a friend. I was curious, so i reinstalled YAMTT for some test. I couldn't believe that all my inputs were perfect even at fast speed. I still don't know if it was a software or hardware issue, but OnePlus seems to have finally fixed my situation.
Looking for your experience after the update.
Click to expand...
Click to collapse
Not yet they aren't. It appears to have affected the functionality of double tap to wake for some people.
Doesn't seem like they're updating us on the investigation either. If they've fixed it using software, at the very least they should tell affected users why all the previous updates didn't work for them.
I've been on the nightly road since mid August, in my experience touch issue improved a lot after the touch firmware update in October, however there are still very rare cases where finicky / unresponsive touch happens, you don't want that when you ask someone for her contact in a bar on Halloween and she can't input the letter 'n'.
After that I think I experienced touch issue twice, I foolishly thought this was fixed sometime ago, however it came back big time the day before yesterday, and I was on the latest nightly... So in short, touch issue is not gone
touch issue
even im having touch issues with double tap and typing.
Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app
anuradha1208 said:
even im having touch issues with double tap and typing.
Click to expand...
Click to collapse
William Haven said:
Touch screen seems less responsive since this update
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?
I'm thinking about downgrading... I'm currently running CM12 nightlies and the touchscreen is annoying me
vantt1 said:
Do you guys have any problems with vertical scrolling (i.e. in lists, webpages etc.)?
Click to expand...
Click to collapse
Everywhere
this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/
st11 said:
this is hopeless, I just went and looked at touch firmware updates, last ones are 1221 at the end of october and 1222 around new years, I remember it working ok during that time, and some time after that, how come I am experience severe touch issue these couple days, touch turned into swipes, swipes registered as touches, unresponsible parts on the screen. I am almost beginning to think it's about the weather/temperature, problems are more frequent when I am out hiking for a long time.
although somebody mentioned that last change was having problems days after http://review.cyanogenmod.org/#/c/83558/
Click to expand...
Click to collapse
There are at least two different touchscreen issues as far as we know:
One is where the touchscreen is semi-terrible all the time regardless of temperature
The other is where the touchscreen becomes unresponsive with the increase in temperature, and subsides if the phone is restarted or cools down
Is there a way of finding out which firmware is being used for colorOS?
I can't take this anymore, I am considering flashing either 44s or color OS
Hi, first of all sorry for my english
I have the one plus for about a year now and never have a problem but since a month ago the phone started to show a yellowness in the top left corner and it gets extremely hot when I'm watching YouTube or even when using Instagram. I'm pretty sure its a hardware issue but I want to know if someone know if there is a way to fix it.
Also I have tried a lot of rooms official, unofficial, sultan, darkobas,omni,slim, COS12/13 and non of them seems to have a differences in my problem
I will add some photos of it later.
Lenox32 said:
Hi, first of all sorry for my english
I have the one plus for about a year now and never have a problem but since a month ago the phone started to show a yellowness in the top left corner and it gets extremely hot when I'm watching YouTube or even when using Instagram. I'm pretty sure its a hardware issue but I want to know if someone know if there is a way to fix it.
Also I have tried a lot of rooms official, unofficial, sultan, darkobas,omni,slim, COS12/13 and non of them seems to have a differences in my problem
I will add some photos of it later.
Click to expand...
Click to collapse
Definitely sounds like hardware issue.
Sent from my A0001 using Tapatalk
Got the same issue..
The yellow thing gets bright with heat
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1
chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems
If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software
That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.
I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.
UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.
chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?
mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse
abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good: