Touch screen sensitivity issue still in 38R - ONE General

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.

Related

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

Does anybody have this issue on their tablets?

Hi does anybody reading this have the similar issue? If so do you know the solution or how to fix this issue?
1. Adobe Flash. A small little issue I've been also having that Adobe flash on my Android gives me issues, when I play a video on the browser it usually takes a couple of seconds for the video to show, sometimes it doesn't so I have to reload the page
2. Ever since I've flashed and rooted my device, on the screen I've been getting a little bit of this wavy thing at the bottom of my screen, almost as if it's loosing power down at the bottom of the screen....If that makes sense.
If you know a solution or is facing this problem, please let me know. Or post the solution?
It'll be a great big help! Thanks and thanks for your time! Much appreciate!
my opinion is:
the flash player, it playing streaming software player flash.....it may lag just a little but its not that big a deal is it really?
the wavy lines, i would say look into of a its a defective tab and if you have receipt take it back for a replacement
i wouldnt say defective tab, have had mine for a year, and after flashing over to tabonney's ICS i get an odd flicker too, as for flash, its trying to render what computers play, with just much less hardware resources to use. Its slow and thats the way its going to be.
My video issues aren't like yours Mkami... But if I might suggest making a full backup, then reflash your rom. Maybe you'll get lucky and the issue will go away.
BrianDigital said:
i wouldnt say defective tab, have had mine for a year, and after flashing over to tabonney's ICS i get an odd flicker too,
Click to expand...
Click to collapse
You know, I've been waiting on someone to mention the odd flicker. Does your tab do it when either, a 3d game or app is running, or maybe on a home screen that has an email widget? And does the tablet seem to still be reacting normally to touch input other than the fact that the screen doesn't show any change? I am thinking about sending my tab in over this for warranty work. I got mine over a year ago too. Sure am glad I paid with plastic, got an extra year warranty for doing it. I just wonder what they are gonna say about the bent corner where it hit the pavement...
JdgM3NT4L said:
My video issues aren't like yours Mkami... But if I might suggest making a full backup, then reflash your rom. Maybe you'll get lucky and the issue will go away.
You know, I've been waiting on someone to mention the odd flicker. Does your tab do it when either, a 3d game or app is running, or maybe on a home screen that has an email widget? And does the tablet seem to still be reacting normally to touch input other than the fact that the screen doesn't show any change? I am thinking about sending my tab in over this for warranty work. I got mine over a year ago too. Sure am glad I paid with plastic, got an extra year warranty for doing it. I just wonder what they are gonna say about the bent corner where it hit the pavement...
Click to expand...
Click to collapse
oh flickering? i think thats a ics problem as most of the ics based roms have the flickering plus stock,. but the guy said he had wavy lines at the bottom of the screen. never heard of that before.
chismay said:
oh flickering? i think thats a ics problem as most of the ics based roms have the flickering plus stock,. but the guy said he had wavy lines at the bottom of the screen. never heard of that before.
Click to expand...
Click to collapse
With pached bootloader and any rom on this site and stock I got
screen flicker, very poor battery, not so smooth scrolling and host of other gliches. (all compared to ota). Flashed back to stock ota and not looked back. No problems. It seemed to me that the problems are not in the roms because stock had the same problems, it the act of changing the bootloader. Just what I have seen, try it just to get rid of the screen problem, go to ota stock no mods and it will be gone.
shaun298 said:
With pached bootloader and any rom on this site and stock I got
screen flicker, very poor battery, not so smooth scrolling and host of other gliches. (all compared to ota). Flashed back to stock ota and not looked back. No problems. It seemed to me that the problems are not in the roms because stock had the same problems, it the act of changing the bootloader. Just what I have seen, try it just to get rid of the screen problem, go to ota stock no mods and it will be gone.
Click to expand...
Click to collapse
You know, that's kind of what I've been thinking. I've been testing by going back and forth between bootloaders. So far that is the best explaination. I'll likely go back to stock again soon. But it seems like I remember it doing it at least once on the stock bl...
When I first updated to ICS, all was well. Within a couple weeks, Flash video got laggy, the browsers got laggy, and I got the occasional screen flickers. I backed everything up and did a hard reset and it's been great ever since.
I haven't heard a really good explanation for all this, but a good theory is leftover files remaining on the system, or possibly file fragments, are interfering with the OS. A hard reset purges the old crap out... regardless of the explanation, it's known to fix these problems.
sRDennyCrane said:
A hard reset purges the old crap out... regardless of the explanation, it's known to fix these problems.
Click to expand...
Click to collapse
Awesome, glad that you were able to get to normal. It didn't help me tho... I might start a different thread for this if it keeps up. I don't want to hijack Mkami's thread with a different problem. Thank you for the help.
Hey everyone thanks for the advices and different problems you guys are facing.
Sorry for my poor explanation... When I mean screen "wave" what I really meant is screen flicker
I found a semi cure for this...Though I don't know about other peoples tablets, all I did was raise the brightness of the screen and the flicker seemed to not show, I must say though that flicker doesn't really much bother me as it does with the flash, but I guess I have to live with it, just a heads up, my tab isn't defective. Truthfully when I do go to stock ROM everything on the device including the flicker goes away, it's only when I flash my device that I notice that, but I am pretty sure there might be a solution for that one or another, because a buddy of mine has the same tablet, which is why I got that a500. I love it and I love android way much more than any other.
Anyways, I hope Flexreaper releases a new rom soon, really am excited with anticipation. Can't wait to see what he has in store for us.
I am going to try that hard reset and fully restoring the device after a nandroid backup and test and reflash and check if anything works with a good
result I shall post up the steps and how to fix this little issue.
I thank you all! Please post if anybody else has this issue or solution down! Much appreciated! Thanks! :laugh:

[Q] Nexus 4 Random Power Off

As the title states. Nexus 4 random power offs. Has anyone seen anything like this?
Here is the background info:
My parents have Nexus 4 phones as do I. All of our phones were ordered at the same time about 2 months or so ago when they became available again. All phones are the 16GB version. All phones bone stock with just OTA updates, not unlocked or rooted other than how they are shipped. All using T-Mobile prepaid plans.
My phone and my father's seem fine. My mom's however seems to shutdown on its own. It is random. Initially I thought that it may be an issue where she isn't used to a smart phone and isn't charging it enough. It happens though at times while it is connected to the charger. It also has happened while carrying it off the charger.
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
I have been around android since the G1 days and run the same phone. I can't think of a setting on the phone that would power it down at a certain time or period of time. She really doesn't have much for apps and is a very light user.
Not sure what to try but I was thinking about doing a wipe of the phone to see if it helps.
Anyone else have any ideas? If the wipe doesn't help the only other thing I can think of is that there is a physical issue with the phone.
I haven't seen this on my phone but there was a period of time where HD Widgets on my N7 would cause a reboot. That was fixed with an app update. This isn't a case where the device reboots. It is a complete shutdown which I find odd. So I have seen an app cause issues kind of like this. For the most part the apps that she has on her phone, I also have on mine. Well I have way more but there really isn't anything on her phone that I am not also running.
I should add that she has the phone in a TPU case. As we all do. My case design is a little different than theirs but they have cutouts for the buttons. So it isn't a case where the case is pressing on the power button. That could be an issue with my case as it covers the power button but I haven't had that issue.
Thanks
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
BigDig said:
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is what I am kind of thinking. Either the battery or the smart battery chips. I think I will try a wipe first but like I said but it is odd.
sennister said:
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
Thanks
Click to expand...
Click to collapse
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
I don't want to root and have my mom run a modified ROM. They live about a half hour from me so I haven't tried a wipe of the phone yet and because of the distance I don't want to deal with the issues that sometimes come up when you go with modified ROMs when I am not there. She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things. I have to get some time to run over there and take a look at it. Maybe later next week.
I was just wondering if anyone else has had this issue. I think if a wipe doesn't help I will talk to Google. A search really didn't show much other than some people that were seeing a random reboot issue. I have seen apps doing that.
I have been through their warranty replacement process and it is a bit of a PITA. I am on my 3rd Nexus 7 due to hardware issues with the first 2. My N4 and my fathers have been rock solid.
While I have run custom ROMs in the past, I usually run stock until I find a need that requires me to root. Eventually I will probably root and go with a custom ROM on my N4 but
sennister said:
She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things.
Click to expand...
Click to collapse
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
amartolos said:
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
Click to expand...
Click to collapse
Hmm. That is a good idea. The PITA part would be to get everything loaded from my phone to hers. I really wish I could run Titanium backup without root as it would make it super easy to move the apps over. Though I don't have that much loaded on my phone. Things that are a pain to set up have configuration export methods like Tasker. It would rule out the end user being the source of the issue. I don't think that is it though. If we swap and it goes away, then I can consider the wipe as the solution. If the problem moves to me then it is a physical issue and call Google. If the problem persists with her, I load all her apps on the phone I carry as well to see if I start to have the issue or it becomes a training issue. The thing I like about this the most is that it is a clear process to rule out several things. I can go over there and sit with the phone but if it doesn't power off when I am there I don't gain much other than spending some time with my parents.
I don't think this is an issue but I did have to provide my IMEI# when doing the activations. In the past though on T-Mobile I have handed phones down to others and all we did was a SIM swap. I would imagine that is the case here.
Oh and one thing I did leave out. They were using their old cell phone chargers on the N4 phones. I told them to swap chargers and use the ones that came with the phone. The old ones may not put out enough power and the phone could in theory run down to the point where it shuts off and slowly charge from that point and I don't think it would turn back on. Keep in mind a retired user who just had a knee replacement so she is at home more often than not.
Did you find out the cause? I have the same issue happened twice today
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
noodles2224 said:
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
Click to expand...
Click to collapse
So you're saying it's a software issue?
Looks like it.. Turning off optimization or not even using WiFi at all worked..
Sent from my Nexus 4

Can Kit Kat solve it all for Nexus 7 2013

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

redmi note 7 ran smoother while charging.

Anyone facing the same problem? Is it something to do with the battery optimisation?
Mine makes no difference, smooth as butter all the time. Maybe you need to debloat the crapps?
kennyk09 said:
Mine makes no difference, smooth as butter all the time. Maybe you need to debloat the crapps?
Click to expand...
Click to collapse
Maybe I should try that. But I found the keyboard is whats affected the most.
bbtee said:
Maybe I should try that. But I found the keyboard is whats affected the most.
Click to expand...
Click to collapse
Maybe is the slow touch latency problem a lot of us are suffering. I am dissapointed i bought this phone.
eldoggor said:
Maybe is the slow touch latency problem a lot of us are suffering. I am dissapointed i bought this phone.
Click to expand...
Click to collapse
Yep I have the touch latency problem too, I actually made another post about that
Fortunately, I don't have the touch latency issue. I only heard it emerged for some Chinese users with MIUI 10.3.5.
For people who've had it since they bought it, might be the case of a bad batch of digitizers used by Xiaomi. The phones are under warranty, why not simply send them for repair/replacement?
Quaresma_7 said:
Fortunately, I don't have the touch latency issue. I only heard it emerged for some Chinese users with MIUI 10.3.5.
For people who've had it since they bought it, might be the case of a bad batch of digitizers used by Xiaomi. The phones are under warranty, why not simply send them for repair/replacement?
Click to expand...
Click to collapse
Mine is the global version, not the Chinese version and I tested the demo in the store and it kinda had like the same problem.
So how bad is the latency? Are you talking about micro lag, or something that effectively prevents normal typing? If I'm really trying to dissect it on my device, I can notice a lag when quickly swiping up and down multiple times without pausing. Or if I open a drawing app and draw lines very quickly. Even then, it is a barely noticeable latency. And I don't have any issues typing. If in your case it's (much) more than what I described, you should definitely replace the phone or have it repaired.
Quaresma_7 said:
So how bad is the latency? Are you talking about micro lag, or something that effectively prevents normal typing? If I'm really trying to dissect it on my device, I can notice a lag when quickly swiping up and down multiple times without pausing. Or if I open a drawing app and draw lines very quickly. Even then, it is a barely noticeable latency. And I don't have any issues typing. If in your case it's (much) more than what I described, you should definitely replace the phone or have it repaired.
Click to expand...
Click to collapse
I think you described some of the problems I have, is exactly what you are talking about. Is barely noticible many of the times, but doing some task like reading a book is just kinda annoying, cause I need to kinda scroll more to make it move. Can you maybe do a screen video with the pointer location on your screen so I can see if you're actually having the exact same problem? For the typing issue, is also quite minor but noticible when you're typing really fast.

Categories

Resources