Database Users

trackball colors *Post 108*

Can you change the trackball colors on the nexus one?
Mod Edit:
Per lilHermit:
OK I've moved the initial su request to before the main screen is drawn to see if that helps.
lilHermit
Click to expand...
Click to collapse
Apk:
TrackballColoursConcept.zip

Yup, this, too, was one of the big surprises for me today when I got mine. I use and love several apps that flash the notification LED different/custom colours, but on the Nex1, the only colour I get is white.
I'm really, really, hoping that OS2.1 just changed the API and that updated apps will be able to do colours. I'm really, really scared that they cheaped out and put a white LED behind the trackball. >.<
][

People are saying that when Bluetooth is paired is flashes blue.

I heard when you have voicemail it flashes red. I haven't tried any of them yet though so I wouldn't know.

its a tri color led so it CAN do any color its just a matter of the third party apps adapting to be able to control it, cant wait

White, red, blue....
Anyone else wish they had green?
Though it was very patriotic of HTC.

AndroTMO said:
Anyone else wish they had green?
Click to expand...
Click to collapse
all colors can be reproduced... just depends on the software that lights up the ball.

indeed it can be changed
unfortunately it stops working after a notification is fired...
Install NotifyLight from XDA:
http://forum.xda-developers.com/showthread.php?t=575024
then set up the pulselight on and change the values in:
/sys/devices/platform/i2c-adapter/i2c-0/0-0066/leds/jogball-backlight/color
ie:
Code:
adb shell echo "255 0 0" > /sys/devices/platform/i2c-adapter/i2c-0/0-0066/leds/jogball-backlight/color
this will give you a nice red jogball.
"255 0 0" is in RGB format.
And off course you need root for this to work...

AndroTMO said:
White, red, blue....
Click to expand...
Click to collapse
When white, it is actually the red, green, and blue all on at the same time.

Would love to see an app to configure all sorts of different notification colors for missed calls, texts, emails, etc, and the blink frequency.
Btw.. MissedCall works, but it can't change the colors.

Once the SDK drops for 2.1 and Nexus One codes and such are released, we should have notifications fixed and custom notifications.

http://twitter.com/missed_Call
I have to say that Google disabled multicolor LED notifications on the Nexus One! (the hardware can do them) #missedCall #NexusOne #fail

xManMythLegend said:
http://twitter.com/missed_Call
I have to say that Google disabled multicolor LED notifications on the Nexus One! (the hardware can do them) #missedCall #NexusOne #fail
Click to expand...
Click to collapse
I can't even to express how disappointed I am at this news. Multicolored notifications was one of the most useful features for me...

cliffy15 said:
I can't even to express how disappointed I am at this news. Multicolored notifications was one of the most useful features for me...
Click to expand...
Click to collapse
As are others. Seriously pissed.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=0493493845dff4e4&hl=en

From all this drama going on, I'm gonna assume this guy has noooo idea what he is talking about:
Or what o_0

... and seriously over reacting.

Eclair~ said:
From all this drama going on, I'm gonna assume this guy has no idea what he is talking about:
Or what o_0
Click to expand...
Click to collapse
Well, it's unlikely that there are 3 led's in there, just one tri-colour.
I've just installed the NotifyLight application and echo'd values to is and it works fine.
People are seriously over reacting, suggesting that this is a deliberate move by google - get a grip, it's probably an oversight. I agree that it's very useful to have but I'm not throwing my toys out of my pram over it.
SC

ScaredyCat said:
Well, it's unlikely that there are 3 led's in there, just one tri-colour.
I've just installed the NotifyLight application and echo'd values to is and it works fine.
People are seriously over reacting, suggesting that this is a deliberate move by google - get a grip, it's probably an oversight. I agree that it's very useful to have but I'm not throwing my toys out of my pram over it.
SC
Click to expand...
Click to collapse
Every sign including feedback from one of the most popular notification apps Devs points to it not working.
If all of a sudden custom ringtones and contact pictures were removed you'd see the same reaction.
Google already closes off the ability to add codecs or EQ bands.
Considering how many apps took advantage of this I dont see why peoples reactions arent justified. You dont pay 500+ for something to lose functionality.

xManMythLegend said:
Every sign including feedback from one of the most popular notification apps Devs points to it not working.
If all of a sudden custom ringtones and contact pictures were removed you'd see the same reaction.
Google already closes off the ability to add codecs or EQ bands.
Considering how many apps took advantage of this I dont see why peoples reactions arent justified. You dont pay 500+ for something to lose functionality.
Click to expand...
Click to collapse
I'm not saying it's not, not working (without rooting). I'm suggesting that the mechanism (API and underlying implementation) has simply changed and it's an oversight. Looking at the link you provided earlier there was mention that the notification API hasn't changed in a long time.
"The SDK hasn't change in terms of Notifications since SDK version 1."
Perhaps that's the reason it's not working, perhaps the API needs an update rather that being deliberately disabled as that poster went on to say.
"Google just disabled that feature in Android 2.1."
That's simply an unsubstantiated claim by someone on the internet.
People are suggesting that this was a deliberate move by google to close off Android bit by bit. Perhaps waiting until we get some sort of response rather than flying off at the deep end is the best course of action.
2.1 is a new release and the Nexus One is a new device. That's what you paid for. You're an early adopter and really should understand that things might not be perfect in the first instance.
Since you're a senior member of the forum and by implication have been in here for a while and have obviously had more than one android phone, I'm a little surprised and your outrage.
SC

ScaredyCat said:
I'm not saying it's not, not working (without rooting). I'm suggesting that the mechanism (API and underlying implementation) has simply changed and it's an oversight. Looking at the link you provided earlier there was mention that the notification API hasn't changed in a long time.
"The SDK hasn't change in terms of Notifications since SDK version 1."
Perhaps that's the reason it's not working, perhaps the API needs an update rather that being deliberately disabled as that poster went on to say.
"Google just disabled that feature in Android 2.1."
That's simply an unsubstantiated claim by someone on the internet.
People are suggesting that this was a deliberate move by google to close off Android bit by bit. Perhaps waiting until we get some sort of response rather than flying off at the deep end is the best course of action.
2.1 is a new release and the Nexus One is a new device. That's what you paid for. You're an early adopter and really should understand that things might not be perfect in the first instance.
Since you're a senior member of the forum and by implication have been in here for a while and have obviously had more than one android phone, I'm a little surprised and your outrage.
SC
Click to expand...
Click to collapse
In and of itself youre 100% right.
But in context with every thing that has been coming out in the last week there could be much more to it.
For all I know there could be something N1 isnt capable of long term that these types of notifications may exploit.
Via Twitter and another via Email Ive seen 2 devs of notification apps confirm that the LED lights and patterns cant be manipulated.
Sure it can be an oversight or just some hitch. Perhaps Im giving these devs too much credit.But its the sqeauky hinge that gets the oil. While it may annoy other posters theres simply no better means than to continually raise a ruckus. Im not up in arms saying screw google F the nexus. Just being adamant about displeasure.
The only way any of us can expect a response is by having these conversations.
The 3g/edge issue doesnt seem to effect me but if its there a stink should be raised.
Frankly if a fix came out tomorrow for the rooted community and never by google Id be just as annoyed. I want the OS to move forward not backwards.

Possible Nexus Camera "Issue"

So I like most everything about my nexus but the way it takes pictures. Its not so much a real issue because it doesn't prevent the camera from working.. but it seems the chip/sensor they used for the camera gives a red spot in all pictures in the center of the image, most noticeably in pictures with a white or light background/image. I'll attach a picture so everyone else can confirm what I mean... I was hoping we could get HTC to replace the phones that have this issue via the warranty as this seems to be an issue with many nexus ones (based on a couple of reviews and the pictures they provided there). Here's my sample picture. You can also see it on screen when looking at what you're going to take a picture of.
Also I do research in a lab and its a procedure for an experiment I'm doing... just realized what I was posting might seem odd... didn't really read it before posting.

It is a software issue, so they are not going to do a warranty replacement. Droid had the same deal with it, seems to be something with the base 2.0/1 Android framework, I am sure it will be fixed when google releases their bug fix update(don't ask when, no legit idea beyond guessing sometime around the start of February, since that seems to be the typical timeline with phone bug updates, about 30 days after launch the first update is released).

Correction. It's a HARDWARE issue. Dont believe me? leave your cammera on for a couple minutes.. Goes away right? Its cuz droid camera was the same.. or similar? They had a bad batch. Mine has no pink eye(N1) =>

The Droid's issue was partially a software problem...
http://www.engadget.com/2009/11/17/motorola-droid-camera-autofocus-fixed-in-secrecy/
As well, it is a "who really knows?"
http://wmpoweruser.com/?p=10749
It seems many phones, with different camera's and so forth are having this issue... CCD seems to be the manufacturer of all the sensors, though, so perhaps there is a problem with the firmware from CCD causing this?
I highly doubt that every single camera sensor ever made by this company happens to have this sort of issue due to hardware. That would be pretty insane! However, if it was a firmware issue, then it would be present in every handset that uses a CCD manufactured/firmware supported camera, and this seems to be the case.
As well, it has already been stated the HD2 will get an update that fixes it. Hopefully the Nexus One is in the same boat. I didn't notice it on the test unit I used, but I asked the current tester if it was happening, and on all 3 it is present. It isn't noticeable in most pictures, though, especially with the flash on, FXcamera set to the proper white balance, and so forth.

EVERY Nexus One you get will have this issue. IT IS SOFTWARE. My N1 has it, the replacement I got has it too.

I've just taken a load of pictures and no pink from what I can see with both flash on and off.
Took pictures of a white surface and no pink. Must be hardware.
EDIT: http://picasaweb.google.com/lh/phot...authkey=Gv1sRgCNKM3fOF452TyQE&feat=directlink
http://picasaweb.google.com/lh/phot...authkey=Gv1sRgCNKM3fOF452TyQE&feat=directlink

Do you have any camera apps installed? FXcamera with proper white balance settings(sometimes auto is perfect, sometimes you have to do it manually) makes it go away a lot of the time too.

Eh Hem.. Guys are you all forgetting that my N1 DOES NOT HAVE PINK EYE

From what I understand this is a hardware issue. This was also present in an earlier HTC phone (I think the HD2) running a different OS altogether.

yes this was a widespread issue on the HD2... and it was completley fixed by a SOFTWARE UPDATE! >.<

A cursory search of the words "hd2 pink camera issue" on Google seems to imply that this is actually a hardware issue.
Edit: The source of the confusion http://www.redmondpie.com/fix-pink-camera-problem-on-htc-hd2-9140202/:
HTC first confirmed it as an hardware issue but then later they found out that it was infact a software issue, rather than a hardware one.
Click to expand...
Click to collapse

http://www.gsmarena.com/a_hardware_fault_causes_htc_hd2_*pink*_camera_issues_confirmed-news-1276.php
I believe the SOFTWARE update is just overcorrecting the blue/green settings on the center of the camera (Guess...) to cancel out the HARDWARE problem with YOUR camera. But again.. It is a Hardware issue for sure. Sorry guys xD I win!
I wouldnt trust htc if you ask them though.. I dont think they are certain what planet they are on half the time.. I asked about how they know that I unlocked my bootloader and his answer was basically.. voodoo. Soooo yaaahhhh... Notice that the cameras are the same for droid HD2 and Nexus one? and those are the only 3 with the issue? Not the G1 with ported software? => hardware folks

flamerider88 said:
I wouldnt trust htc if you ask them though.. I dont think they are certain what planet they are on half the time.. I asked about how they know that I unlocked my bootloader and his answer was basically.. voodoo.
Click to expand...
Click to collapse
You asked someone in support; customer support for any company is always uninformed. These aren't the people making press releases or even official forum posts.

flamerider88 said:
I believe the SOFTWARE update is just overcorrecting the blue/green settings on the center of the camera...
Click to expand...
Click to collapse
I agree, just because the manufacturer releases a software fix doesn't mean its a software problem to begin with.
The first day I had the phone, I really noticed the pink spot. Yesterday I took 30 pictures, I didn't notice it at all. Today If I look hard enough I think I see a little tiny pink, viewing the image of a white piece of paper in the same place (office) I first tested the camera.

Yeah I noticed this too. It only really shows up if I take pictures of white paper or a white wall. Every other normal pic I take turns out fine but I do hope they can fix it with a software update... wouldn't be too hard.

dinan said:
Yeah I noticed this too. It only really shows up if I take pictures of white paper or a white wall. Every other normal pic I take turns out fine but I do hope they can fix it with a software update... wouldn't be too hard.
Click to expand...
Click to collapse
My n1 has it too. Ive tried it now in room with room light and it gives this violett spot when i tak a picture with automatic colorbalance, if i put room light as colorbalance there is no spot...

google already knows about that issue and a fix will be released!
"I have great news! The issue has been fixed and should be included in the next update to Android. I say "should" because things can change at the last minute. Keep an eye on your notification bar for a system update."
source: http://www.google.com/support/forum/p/android/thread?tid=7a22ebb69da2b253&hl=en#all

navahoo said:
google already knows about that issue and a fix will be released!
"I have great news! The issue has been fixed and should be included in the next update to Android. I say "should" because things can change at the last minute. Keep an eye on your notification bar for a system update."
source: http://www.google.com/support/forum/p/android/thread?tid=7a22ebb69da2b253&hl=en#all
Click to expand...
Click to collapse
I followed the link, but didn't see the response you quoted...?

flarbear said:
I followed the link, but didn't see the response you quoted...?
Click to expand...
Click to collapse
That's because it was removed by Google. I read it this afternoon. Is not there any longer. The Google employee was "Tommy" and you can't find his posts any more.
You can read other people's response to his post but his don't show up any longer.

well, that post is very hopeful. i suppose all we can do is hope for the best. i dont know if google deleting the post is good or bad though

I am so done with Android

I have been using Android since cupcake and it's going to end with my Nexus One. Reasons:
These are problems I've had with various roms, most stock roms, some MIUI:
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
- My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
- To fix the above I got Better Keyboard. It force closes often, and sometimes when I try to type with it what I'm typing doesn't get inserted into the selected input box.
- I got five hours of STANDBY (not using phone at all) battery life on Gingerbread. I had to downgrade back to froyo to get normal battery life back.
- After ten seconds or so if you don't use your screen it's supposed to DIM. Regardless of whether or not I'm using my phone it still dims after ten seconds.
So as far as Android goes come October when my three year Bell contract expires I'll be selecting an iPhone. I am done with Android problems of all kinds. That's not to say there's not a lot of things I like about Android but I can't just keep on going with it whilst experiencing these annoying problems, when I've never experienced any problems of any sort on my jailbroken iPad.

Did you ever try using your warranty? Really sounds like you had a dodgy handset.

Sounds like your phone is a lemon. I experience none of that....don't think anything you mentioned is a problem of android itself, you just got unlucky with your phone
Sent from my Nexus One using XDA App

Sounds like some bad flashing you been doing to your phone
Sent from my Nexus One using XDA App

lemons
.

You must be holding it wrong, those are some crazy problems you are experiencing ... I've never had any of those.

Macmee said:
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
Click to expand...
Click to collapse
Not related to Android in the slightest. You're having a HARDWARE problem.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
Click to expand...
Click to collapse
Not related to Android in the slightest. You're having a HARDWARE problem.
My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
Click to expand...
Click to collapse
In all of my time with Android, on multiple devices, I have NEVER once seen this issue. Something is wrong with the custom rom you're running... which btw, YOU flashed on your phone.
To fix the above I got Better Keyboard. It force closes often, and sometimes when I try to type with it what I'm typing doesn't get inserted into the selected input box.
Click to expand...
Click to collapse
So some janky app YOU installed is causing a problem? Uninstall it and find something better.
I got five hours of STANDBY (not using phone at all) battery life on Gingerbread. I had to downgrade back to froyo to get normal battery life back.
Click to expand...
Click to collapse
Did you try and diagnose this at all? Were you having a wake lock issue? Was some app freezing?
I go all day on Gingerbread, especially if I don't even use it...
After ten seconds or so if you don't use your screen it's supposed to DIM. Regardless of whether or not I'm using my phone it still dims after ten seconds.
Click to expand...
Click to collapse
Again, this sounds like either something wrong with your rom or a hardware issue. I have never seen this issue.
Yeah, you're an idiot. Sorry, but you're blaming problems that either you have created or hardware problems on Android, the operating system.
But go ahead and leave Android. It sounds like you're not really technology capable of much more than an iPhone (and really, this is probably going to be pushing your technological limits it seems), so that is probably what you should stick to.

I won't be as harsh as the others
The only problem you mentioned that is N1 related is the screen, rest are probably rom related. If your flahsing all those roms you already know they are not guaranteed to work on all phones.
If you want to try another phone, try the new Sensation or equivalent. Android is still much better than Apple. IMHO. That said, my son and his wife have been Apple users for 20 years or as long as I can remember. They have used nothing else. So, I think the iphone is a good phone, just not for everyone. As android is not for everyone. I once thought Blackberry was unbeatable, I was wrong bigtime. When I first started using them, they may have been. But, not any more.
You are probably like me and get an itch to try something different. I am currently running RCADSmix Sense rom with a number of issues. But, I like it so much, I will put up with the issues. Probably means my next phone will be the Sensation or it's future quadcore brother.
Enjoy whatever you get, I still remember when a six transistor am radio was an upgrade. These are great tech times--
Ken

If you really can't realize that the problems you are experiencing are hardware related...it's probably better you get an iphone. Bye and don't let the door hit you on the way out

So as far as Android goes come October when my three year Bell contract expires I'll be selecting an iPhone. I am done with Android problems of all kinds. That's not to say there's not a lot of things I like about Android but I can't just keep on going with it whilst experiencing these annoying problems, when I've never experienced any problems of any sort on my jailbroken iPad.
Click to expand...
Click to collapse
Im just guessing here but your in Canada with bell? bell doesn't offer the nexus one. how are you on a contract? Ill also agree with everyone else your problems are not android related. Sounds like a hardware issue. Good luck with the iPhone my brother loves his. I like the design but that's it.

Just flashed cyanogen latest version. New problems:
1. Sometimes when turning on the phone the lock screen doesn't show up, just my background displays and nothing else. Reboot required by pulling battery out in order to fix.
2. Display menus don't show up sometimes.
3. Already experienced this one, but the keyboard is yet again going completely white.
Anyone want to point me towards an actual working rom without any problems or does such a thing exist
wsrider said:
Im just guessing here but your in Canada with bell? bell doesn't offer the nexus one. how are you on a contract? Ill also agree with everyone else your problems are not android related. Sounds like a hardware issue. Good luck with the iPhone my brother loves his. I like the design but that's it.
Click to expand...
Click to collapse
I bought it outright two years into my contract when I had a vogue.
Babydoll25 said:
If you really can't realize that the problems you are experiencing are hardware related...it's probably better you get an iphone. Bye and don't let the door hit you on the way out
Click to expand...
Click to collapse
Because not all of these problems are with the hardware and you, or myself are incapable of diagnosing them without more extensive investigation to the handset.

Roms work fine. Your phone doesn't

Most people have no or little problems with these roms
Most if not all issues are improper flashing or incomplete wipes--like not wiping system and data and caches multiple times
Check md5s
Or, not properly partitioning sdcard
If still issues then the phone has too many bad blocks for the rom and kernal
Ken

After reading your first post again, I think it is your phone and not common issues. I have never had a bad camera unless specifically noted on the OP page of an alpha type rom.
I can tell you how I do my sdcard and prepare for a new rom if you like. If my procedure doesn't work you will never have any better luck flashing with that particular phone.
Sorry
Ken

I'm with Telus on my N1 and i've never ever seen any of the problems you mentioned. I've also flashed alot of different roms/kernels/apps/etc and nothing like you had mentioned.
I did however have an issue that resembles your camera issue. Mine was the GPS causing my phone to reboot every time i used it. I didn't really notice it much until i started using it for GPS nav and such. Tried flashing different roms, going back to stock and issue still came up. Called HTC and sent my phone back under warranty. They told me they replaced the board and i have not seen the problem ever since.
I strongly recommend giving HTC a call and see if you can send your phone in for repairs.

That's what iPhone is for. To protect incompetents like yourself from themselves.
You should be nowhere near a rooted phone.

I have the exact same camera issue. The reason is a date of my beloved Nexus and my washing mashine. So it might be a hardware problem for you as well. Sometimes with some roms the camera seems to work 1 out of 10 times.
Bluetooth, fm radio died as well but everthing else is just fine. Some roms seem to check/use camera, radio or bluetooth during a reboot. Then the rom won't start at all or it makes random problems.
This phone is a beast. 20 minutes in the washing mashine at 60°C couldn't really destroy it. Even between screen and digitizer there was water and I had to disamble the phone three times and dry the parts for one week in a rice bowl to get it to work again.

xManMythLegend said:
That's what iPhone is for. To protect incompetents like yourself from themselves.
You should be nowhere near a rooted phone.
Click to expand...
Click to collapse
+1
sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch

- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
- My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
Click to expand...
Click to collapse
Got this also, annoying but I'm quite sure it goes along with flashes. Pretty sure it will be normal on stock rom.

Actually mate I think you should upgrade your radio...
I used to have this issue with the camera before, get the latest radio and ur camera issue will be solved.
and the battery as well i guess
as for the keyboard and all the other problems just go to rom manager and flash cm 7.1 rc1 from there, make sure you wipe cache, and dalvik cache
it should solve ur issues
Android is a more technical platform, it is by default that the user likes going technical before getting an android

Touch screen sensitivity issue still in 38R

I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Edit: here you have the prove (bad scrolling and multitouch problem) i think i am going to RMA
Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Edit:
Suddenly the issue has been gone for a week, no problems at all since 15 October... I am so confused
Edit 2:
The sensibility issue is back on 24/10/2014 without changing anything

QuBeX said:
I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Click to expand...
Click to collapse
Yes, I also still have troubles with it. I especially notice it when typing.

gr4nchio said:
Yes, I also still have troubles with it. I especially notice it when typing.
Click to expand...
Click to collapse
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time

QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?

gr4nchio said:
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?
Click to expand...
Click to collapse
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...

QuBeX said:
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...
Click to expand...
Click to collapse
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.

Touch screen is still going to be an issue. You can check the original bug which was reported here (still says in progress) https://jira.cyanogenmod.org/browse/BACON-55

gr4nchio said:
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.
Click to expand...
Click to collapse
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src

QuBeX said:
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Click to expand...
Click to collapse
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.

jlevy73 said:
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.
Click to expand...
Click to collapse
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.

dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
Not sure since I just requested a new phone.

dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
They will, at least, replace your phone. I did and am waiting for my new one to arrive. If multitouch issues remain (and most likely will) i'll ask for a refund. I don't really care if the phone is "cheap for specs", this flaw is unacceptable.
My S3 is much worse hardware wise and feels SO much better while typing or anything else touch related. I did have to open a ticket and later show up a few videos of multitouch malfunctioning to oneplus. They decided it was a malfunctioning unit and i was eligible for a replacement. They never mentioned bacon 55 or a "known issue" common to every phone that would be solved at some point later on.
It's taking forever too. It's been over a month and it's mainly their fault because they take so long to reply to every single email. They did ask my VAT number before hand so they could send an invoice with it to my customs that would facilitate the returning process. Despite that, my phone got stuck on my country's customs precisely because they sent them an invoice without it and was up to me to ask it to oneplus. I waited about a week for what seems an poorly excel made document (compared to my country's invoices this is a joke of a document ). I sent it to the courier who picked up and they forwarded it to customs. Stuff went smooth from that point on. Oh yea, i'm from Portugal and even though my phone was sent to me from the UK the first time, to return a phone, you're going to send it to Hong Kong. All free of charge. I did have to print loads of pre made documents (about 10 pages?), because apparently sending anything with a battery is a big deal safety wise.
Even though they are, like someone said, polite, they do take a good while to reply to anything and aren't very keen to answer to anything that falls a bit out of their "process". For example, I've asked them several times if they would send me a new phone before or after a return mine. They never really cared enough to answer. Their English also seems translated by google sometimes. Several different people may take care of the same case. I've had about 5 or 6 different names reply to me and they all just use their first name like "Wilona". It made me stop to think i was sending my already paid phone to some place across the world because this randomly named guy told me so by email - in any other different scenario this would scream of a scam. But I've placed my RMA through an official ticket on their website, they actually made a new order request from their store on their website, they use very well known couriers with tracking numbers and it's the only way i'm ever getting a chance of having a properly working phone.
I did warn them before sending my "faulty" unit back they can expect me asking for a full refund if this new one isn't working any better.

I have been on liquidsmooth rom since I got the phone, no problems with touchscreen whatsoever, Installed new 38 CMS today and started to experience that problem. Also, cms lags compare to AOSP, this is pretty weird

QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
Flashing ColorOS for me gave a much better touchscreen experience, things worked flawlessly in all apps for me(Amazon is my biggest issue, any scrolling over a description/review would select it and move you to that section to read it, does not happen at all in ColorOS), so im thinking its software

This issue is so exaggerated...
Sent from my A0001 using Tapatalk

What is the touchscreen issue that people are referring to? Mine seems perfect? The only issue is the slight yellow at the bottom but you only notice it if you actually go looking for it.

jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Not really. It's bothersome.
Sent from my OnePlus One using Tapatalk

Mines slightly yellow at the bottom, appears to be getting a bit better though, unless thats just my eyes playing tricks on me. I haven't noticed touchscreen issues except i can't seem to press the spacebar properly

My touchscreen seems to be very picky as to where I touch. Sometimes it takes a few attempts. Since 38 I have had random reboots. I m stock rooted without anything else flashed.

jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If you can say that you're a lucky one. It can render your phone completely unusable. Imagine your phone randomly assuming touches when you're not even touching it, non stop (stuff opening, key input, etc). You can't do anything else while it happens and the only way to stop is by rebooting. 5 to 10 times a day, everyday. Also, just about anything multitouch like simply zooming on a webpage has a 50% chance of working or send your phone spazing on a zooming in/out frenzy. So I'd say it isn't exaggerating, you just aren't experiencing the worse of it.

Weird camera effects

Anyone else have had their camera vibrate like crazy with audible sounds and the display for the camera shot showing sorta like a motion blur effect or like water waves?
Any fix for this if its a software issue? or hardware issue and i should get it sent back?
It seemed to be fine a few months back when i just got it and it was on B02, seems to have begun since B05 or B08 if i recall correctly, currently on Nougat 7.0 (2017G Version)

I think it's the OIS going crazy. I have the same issue, I think this is hardware caused. It doesn't bother me much because restarting the camera usually helps for me

Restarting camera is a temp fix, I would like a software patch from ZTE though
Here are my experiences with it:

Any updates or fixes on this issue?

|Furō| said:
Any updates or fixes on this issue?
Click to expand...
Click to collapse
There are like ten threads about this, and the only solution is an RMA. Or change the module by itself

I'm running in to the same problem with my device recently. It seems like the problem is occurring increasingly more often..

pringlet said:
I'm running in to the same problem with my device recently. It seems like the problem is occurring increasingly more often..
Click to expand...
Click to collapse
Was / is the same for me! But then again if OIS was completely broken, wouldn't it occure every time? But as I stated before this seems to mostly happen to me, when my phone is used in very hot conditions (hot day and out in direct sunlight for some time). I've tried using it in "cooler" circumstances and did not have this issue there so far.... So I don't know if I'm going to send my phone in right now... honestly I'd rather not. :/

Consider it to be faulty and return it. There isn't any amount of software that can fix it. I talked with ZTE and they said it was hardware related. RMA is the only way. My OIS slowly started to die. It would only happen 1/10 times and by the time I sent it in, it was happening 9.9/10 times.