Related
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
When taking pictures in low light situations with flash (it seems low battery enhances the probability) sometimes the pictures get artifacts (white lines close to the top/bottom of the picture).
And sometimes the phone gets stuck and reboots. The camera tends to make clicking noises right before it reboots that are louder than when usually focusing.
Look at the screenshot and at the end you can see the reboot. You can see a sudden battery level drop after the reboot.
I don't know if this is hardware or software related but a user suggested this to be a problem with the stock camera app.
I had this problem on two devices already and it seems to be on all devices, maybe just rarer for some people? Not sure.
If you have this problem vote for the following issue and hope google fixes it:
http://code.google.com/p/android/issues/detail?id=49702&#makechanges
I had something similar happen to me once last week. I was viewing my photos in the stratosphere mode and would hit the back button. I had to repeatedly do this to scroll to the next images after viewing them. When hitting the back button it would take me back to take a picture, but one time, it took me to a blank screen with the camera buttons still working. I ended up needing to restart my phone. Not sure what happened there.
I have only seen this once. It didn't occur again, so I haven't chased it down
Ditto only happened once in the first week of using and has never happened again
Sent from my Nexus 4 using Tapatalk 2
AW: Reboot while in camera
Kinda sucks when it happens randomly, today it happened twice to me and that in 4.2.2!
Sent from my Nexus 4 using xda app-developers app
I also have it, but less frequent, about one or two times per month. It happened on 4.2.1 and no one could solve it in my thread about this .
Facing the same issue more frequently
ruzkay said:
While taking pictures my phone suddenly got stuck and rebooted. This is the second time now. My camera makes strange click noises sonetimes wheb focusing but that seems to be normal.
The device was a little hot but not as hot as when in gaming and in gaming it never reboots.
Look at the screen shot and at the end you can see the reboot. What I'm worried about is the sudden battery level drop after the reboot.
Are these reboots hardware or software related? Should I get a replacement?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I seem to have the same issue. So far, it has only occurred when I am trying to take a photo with the flash on. One more observation: seems to happen more often if the battery is low. However, both of us might be having defective devices, as it doesn't seem to be a common issue looking the forums here.
No solution found so far. Tried a factory reset. Tried using another camera app. Nothing helped. Might try flashing a custom ROM.
AW: Reboot while in camera
sumit29 said:
I seem to have the same issue. So far, it has only occurred when I am trying to take a photo with the flash on. One more observation: seems to happen more often if the battery is low. However, both of us might be having defective devices, as it doesn't seem to be a common issue looking the forums here.
No solution found so far. Tried a factory reset. Tried using another camera app. Nothing helped. Might try flashing a custom ROM.
Click to expand...
Click to collapse
All oft the things you described apply to my situation too. Also I noticed that pictures tend to have artifacts (white stripes close to the top/bottom). They always have the same distance from top/bottom but their length differs.
Also after the forced reboot there sometimes appears an extra picture in the gallery that is fully grey.
Sent from my Nexus 4 using xda app-developers app
I don't seem to have the artifact problem that you described. Also there is a creaking sound sometimes just before it restarts.
Have you tried flashing a custom ROM? Did it help? Otherwise RMA is possibly the way to go.
I ordered the phone from US using a mail forwarding service, so an rma will cost me another $100 or so. If you or anyone else can confirm that it is definitely a hardware issue which can be resolved by getting a replacement, i might go for it.
Sent from my Nexus 4 using xda app-developers app
sumit29 said:
I don't seem to have the artifact problem that you described. Also there is a creaking sound sometimes just before it restarts.
Have you tried flashing a custom ROM? Did it help? Otherwise RMA is possibly the way to go.
I ordered the phone from US using a mail forwarding service, so an rma will cost me another $100 or so. If you or anyone else can confirm that it is definitely a hardware issue which can be resolved by getting a replacement, i might go for it.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I was on AOKP PUB Krait 05/02 by Stevespear and Harsh Kernel and I did have a reboot there once too. Also this is already my third Nexus 4 since I had to replace it 2 times due to issues (bottom side creaking 1st device / yellow blotches 2nd device) and this one really looks good only this camera reboot issue is left.
But my first phone did have the issue too, I didn't have the 2nd phone long enough so didn't see it happen there. I have no idea if it is a hardware or software issue but my bet is that all Nexus 4's have that issue.
It just seems that it appears rather rarely and most people don't notice it. Or it could be that the voltage is too low and that would explain why it happens on some phones more than on others since not all chips are equal. I was wondering if somehow setting the flash to be weaker so it draws less power would solve this. But I am just a user and don't really have an idea.
PS: I won't get my phone replaced since I can live with this issue (it happens rather rarely) and I went through 2 replacements to get this device which is close to perfect but I wouldn't mind if someone came up with a solution.
That makes me feel really lucky to have gotten a nearly perfect device. Anyway, guess we just have to live with it then. Lowering the flash intensity sounds like a good idea. Will check if some rom/kernel/app can do it for me.
Sent from my Nexus 4 using xda app-developers app
Just added issue 49702 on code.google.com. whoever is facing this problem, add your comments.
Sent from my Nexus 4 using xda app-developers app
Having the same problem here on 4.2.1 and 4.2.2. I think it might be the buggy stock camera/gallery app because I can't replicate the problem on the Camera Zoom FX app.
Edit: I remember having this problem on 4.2.1 and then clearing the gallery app data and not ever seeing the issue happen again. I will try the same on 4.2.2 and see if it fixes it too.
I added a link to the issue on OP guess that is all I can do.
sierratango88 said:
Having the same problem here on 4.2.1 and 4.2.2. I think it might be the buggy stock camera/gallery app because I can't replicate the problem on the Camera Zoom FX app.
Edit: I remember having this problem on 4.2.1 and then clearing the gallery app data and not ever seeing the issue happen again. I will try the same on 4.2.2 and see if it fixes it too.
Click to expand...
Click to collapse
I have had this issue with the Camera FX Zoom app also. So, at least in my case, I guess it's a hardware/camera driver issue. Anyway, I also cleared the gallery app data a few days back and haven't faced this issue since then, but haven't taken enough pics with flash to confirm that the issue is truly gone.
sumit29 said:
I have had this issue with the Camera FX Zoom app also. So, at least in my case, I guess it's a hardware/camera driver issue. Anyway, I also cleared the gallery app data a few days back and haven't faced this issue since then, but haven't taken enough pics with flash to confirm that the issue is truly gone.
Click to expand...
Click to collapse
Has the issue disappeared after clearing the app data for you? I certainly have not faced any reboots since doing it.
Hey guys, I was wondering if anyone may know if the new 4.4 Kit Kat will fix all of the Nexus 7 2013 touch screen problems.
Maybe Asus and Google knows it fixes the issue. That's why they didn't rush to help us in the last few months.
Cross your fingers people and hope this fixes all of our issues. That would be sweet.
Oct 28 4.4 I'm thinking.
I hope that... it's been a headache, and that's the only flaw mine has, the fix here fixes it just temporally.
Can't say whether it will or won't but I can say I really doubt they have the fix already in hand and are holding it back waiting for kit kat.
They've never been shy about putting out releases to fix things and a touchscreen fix is very contained and isolated, not something that touches many areas requiring long code reviews.
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
I don't know, maybe I use the device too much? But I can definitely say ghost touchs and some multi-touch issues are there and persistent. In fact right now as I was writting this the keyboard went crazy, it's really annoying and I don't even want to start with the horrible experience I'm getting with PS Touch(which I use a lot) thanks to this problem. Sometimes I have to reboot the device when it goes crazy zooming while navigating the internet.
For you guys that your tablet is "perfect", fascinating, good for you, but that doesn't mean the problem doesn't exists anymore, you just got lucky.
I personally have no more touchscreen issues since JSS15Q, but if there is another touchscreen fix in KitKat that would be good to the few unlucky ones still having issue with theirs..
neo5468 said:
Can I just ask what kinde of problems you are reffering to? Multitouch problem has been fixed with the latest update. At least mine was. With a multitouch program I placed all 10 fingers on screen and was moving it arround, and it registrated all fingers and arrows were moving very very smoothly. 60fps+. Also, there is no problem with GPS anymore. The only problem which is actually not a problem, is smal buzz from speakers when watching of listening to something at very low volume, but that is reported for all nexus 7 devices because that is how the speakers are made.
You are saying like nexus 7 2013 is forgotten and this 4.4 is our last hope for the device otherwise its useless to use. Which is far from truth. I have absolutely no problems with it.
Click to expand...
Click to collapse
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Google will have to detect each variance and patch accordingly. Probably why it hasn't been released yet because it probably will take a larger testing period then previously mentioned. Even using the XDA fix, some versions can cause several FCs and bugs. Similar to the specific pattern freakout.
With 4.4 on the horizon, it would be best to include it in that. Google probably isn't going to create an OTA and then another one in a few weeks.
Just cross your fingers and hope for an official fix.
GPS was fixed though. I'm not sure about the kernel reboots though. I haven't used the stock kernel nor had reboots since I flashed CM Kanged.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
player911 said:
The few that had touchscreen problems initially were fixed. 75% of working units were broken in the process. Its a big issue. We have a fix but nothing from Google. There are several screen variances which make it impossible for a single 1 fix all solution.
Click to expand...
Click to collapse
Any source for that 75% number? Without a proper source it is hard to not consider that as a case of the loud minority.
If it were that serve of a problem we would hear the tech press clamoring about it by now. But nothing was said about N7 touchscreen by the tech press since JSS15Q.
I can't tell you what the real percentages are, but the touchscreen issue is definitely a much bigger problem than your standard problems.
Standard run-of-the-mill issues get a thread with maybe 20 posts. Touchscreen is producing 1000 post threads. So relative to normal problems it is a big problem, but whether that is a 5% vs 1% problem or a 75% vs 1% problem I could not tell you.
There are at least 3 huge threads on Google support forums about this problem:
Multi-touch - reports of improvement, no improvement, and some worse
Multi-touch (continued) - more reports of fixed / not fixed for JSS15R
Multi-touch (continued 2) - more reports of touchscreen issues
BTW I created the xda fix for touchscreen so I'm very familiar with the fixes Google put out and whether they have fixed the issue. JSS15R fixed it for some screens but made it much worse for others.
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
NekroWolfen said:
That's the main reason I haven't sent my Nexus for repair, is not hardware related, or at least that's what I think, please someone correct me if I'm wrong.
Click to expand...
Click to collapse
Well, actually it is hardware related, but you can't tell if your hardware is one type or another without using Sfhub's process.
Well, thanks for confirming
I personally don't think that all of the touchscreen issues will be fixed with Kit Kat. I feel that Google will he focusing more on a fully operational OS, and that we'll need a dedicated fix to solve our problems.
But I surely hope that I'm wrong.
______________________________
HTC Evo 4G LTE
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Lockeskidney said:
any word of usb audio coming via kitkat. ive been waiting for this feature to come to the nexus 7 forever because its keepingme outof my car
Click to expand...
Click to collapse
At this point, questions to me are almost meaningless to ask. We night as well wait for tomorrow. It took long enough to arrive.
It just sucks that I don't have my tablet. I went back to Radio Shack and ordered the 32gb through them, since none of their stores had that version on their shelves, and 16gb was not working out for me. At least I'll get to download it as soon as I get my new device!
______________________________
HTC Evo 4G LTE
GPS isn't solved to me.
diogobuique said:
GPS isn't solved to me.
Click to expand...
Click to collapse
That's a hardware issue, I suggest you to send it back to Google.
Kitkat gave me phantom touch issues, have none before kitkat. :-\
Sent from my SM-N900P via TapaTalk PRO
Elite Tester
This process doesn’t wipe the tablet, so your settings, apps and everything else should stay in tact whenever you get back to the system. Remember that you will have lost root at this point, but it’s easy enough to get that back.. Cool resource!
But before kitkat my GPS worked very well
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.
My fiance bought one of these for us, and she said shes noticed the longer its used the pseakers go bassy and fuzzy. only corrected with a restart. ive searched and cant seem to see a mention of it
anyone had this issue
-PiLoT- said:
My fiance bought one of these for us, and she said shes noticed the longer its used the pseakers go bassy and fuzzy. only corrected with a restart. ive searched and cant seem to see a mention of it
anyone had this issue
Click to expand...
Click to collapse
Yes, I've had this as well.
I don't know what causes it, but during a film, about an hour in, it started going fuzzy, as if someone added a "static" track in there. It becomes all static-y...
It's resolved by rebooting.
Anyone have insight on this?
AjunNg said:
Yes, I've had this as well.
I don't know what causes it, but during a film, about an hour in, it started going fuzzy, as if someone added a "static" track in there. It becomes all static-y...
It's resolved by rebooting.
Anyone have insight on this?
Click to expand...
Click to collapse
A ROM bug maybe?
No, I have stock and the same problem after a long gaming session. Closing and re-open the app sometimes works, but sometimes indeed only a restart works.
Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk
If rebooting fixes it, it sounds like it may be a software issue. Have you tried doing a factory reset?
Mine has done something similar a few times, only while playing Adventure Express. I assumed its just a bug with that game, but it affects all audio running on the tablet until I clear the game from Recents. Stock 5.0.1 rooted
Sounds like your devices are haunted
Anyway, never experienced anything like it
I get playback issues with the Comedy central app that are fixed by a restart I have a feeling it has to do with some of the lollipop memory leaks.
I have had no issues yet but for this to be a HTC tablet I would think it would have better sound like on the M7 and M8. Still sounds good and love the speakers on the front
Sent from my Nexus 9 using Tapatalk
I've had it happen straight out of the box. Then a couple time times later on, completely stock. Have yet to experience this on SimpleAOSP, but I'm sure the bug is still present, just haven't noticed it yet.
Edit: This is not a speaker issue, but more a software issue. It happens with headphones as well. http://forum.xda-developers.com/nex...e-sound-using-earphones-t3032098#post58898735
Reboot
I have experienced it one time only. A reboot fixed it. It looks like a SW/driver issue to me. Not a huge problem, but taking the price of the Nexus 9 into consideration, it would be nice to have it fixed