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
Related
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
Anyone else experiencing this? In the 24 hours I've been using my nexus 10, this has happened at least 10 times. All of a sudden the device becomes unresponsiv, the screen dims until it turns off, and the only way to get the device back on is holding down the power key multiple times until it boots back up. Needless to say, quite frustrating. Otherwise, love this device.
Anyone else experiencing this?
Sent from my Nexus 10 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1998496
Sent from my Galaxy Nexus using Tapatalk 2
Not quite sure how one loves a device that forces you to reboot ten times in the last 24 hrs. It's like buying a new Honda and loving it even though it stalls ten times a day.
Too many people apparently buy their device to adoringly stare at like a trophy or a collectors item than actually use.
Those all seem like pretty legitimate apps to me. This would suck but I would suggest deleting one app and using the tablet till it happens then rinse repeat till you find the offending program.
Try the secret magic spell: a full wipe
Sent from my GT-N7100 using xda app-developers app
Add me to the list of people with random freezes and reboots. It's happened to me 3 times since I've gotten the tablet a few days ago, and I was using a different app each time. I suspect it's an OS bug rather than an app that's causing it. It's a little disheartening that Google let their new flagship 10" device get released with such a bug. Hopefully they release an OTA update sooner rather than later.
For the record, I rooted using the flashable CWM SuperSU file - I did not use the toolkit.
I have had my 16gb 10 now for almost a week - currently stock and non rooted. No problems whatsoever and I have been working it pretty hard.
Mine has frozen 2-3 times in the past few days. No idea why either. Audio continues to play, and the device responds to button use, but the display stops altogether.
Sent from my Nexus 10 using Tapatalk HD
I got mine like a week ago and it's been frustrating. I debated whether to return it or not. I really like the Nexus 10 but this has been really inconvenient. Does CM10.1 have the issue coz I am planning on rooting and flashing CM10.1 if it resolves the issue. Just trying to get an input.
ralphconrad91 said:
I got mine like a week ago and it's been frustrating. I debated whether to return it or not. I really like the Nexus 10 but this has been really inconvenient. Does CM10.1 have the issue coz I am planning on rooting and flashing CM10.1 if it resolves the issue. Just trying to get an input.
Click to expand...
Click to collapse
In another thread someone said it slowed the issue but didn't stop it.
Sent from my Nexus 4 using Tapatalk 2
Thanks man, now I'm debating if I should just get the transformer infinity. I really don't need root that much because I only use my tablet for school...
Sent from my Nexus 10 using xda app-developers app
Happened to me several times as well. Last time the screen went black (not off) and the tablet was extremely hot, to the point of burning my hand when I touched it! Seems it was stuck that way for several hours and didn't reboot itself.
I've been having random rebooting and freezes since getting this tablet i've replaced it three times already so i'm tired of calling google about it don't even think they have a solution because we've been waiting since November for them to fix this problem so i decide to turn off location and took HD widgets out and so far my tablet has not frozen or rebooted in two weeks it been working really well hope it continues to perform this way.
Chrome has major stability issues as far as I can tell. It crashes very frequently and causes a complete system lock-up when it does. I've resorted to Firefox. To me, this is absurd on a core first party app. Google: get your act together on Chrome.
I recently noticed this issue and have been reading what a lot of others here have had to say and so far it seems to be related to wifi. I would bet it's a software / kernel / driver issue because others have reported not having the problem before the latest update.
If I think about it, I probably had the lockup/reboot happen once before now and I can't really tell you what I was doing at the time. But I thought nothing of it. I have however found a way to force it to happen. All it takes is a large download (1gig'ish) in uTorrent, the download works fine for about 10 minutes and then the tablet either just restarts, or it first becomes unresponsive to input (screen or buttons) but is still functioning, followed by a hard lock up that can only be fixed with a forced power off.
It may be a buffer issue, or memory leak, I've been able to prolong the lockup by throttling the uTorrent download speed and minimizing the number of active apps running. As suggested in other threads I've disabled location discovery and it may have bought me a little more time but if so it's not much. I can't tell if it's because of the amount of constant data flow coming in, or the number of active connections to different seeders, or more likely a combination of the 2. I can also say that if I attempt to browse the web with either chrome or Dolphin while downloading in uTorrent the freeze or reset happens much quicker.
So for now I'm hoping that in the next update they resolve the issue and will just use my pc for torrent downloading.
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Turning off the location services and uninstalling HD widgets sorta worked for me... I still get random reboots though but mostly when I'm using Chrome. Google should have just left the stock android browser and made Chrome optional.
Sent from my Nexus 10 using xda app-developers app
3DSammy said:
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Click to expand...
Click to collapse
Thanks, ya that had crossed my mind but wasn't sure which defect to post it to so thanks for the link.
HELP!!
I am experiencing the same problem.
3DSammy said:
T.D.K,
It may help Google resolve this issue if you reported your obvervations in this bug report thread:
https://code.google.com/p/android/issues/detail?id=39879
I think the wording you used in your post would be sufficent. Nothing helps identify where a bug is more than a repeatable instance of the issue.
Click to expand...
Click to collapse
Nope, the problem was submitted to Google months ago and is listed to only receive medium priority. A total system failure that affects every single Nexus device is only given medium priority. Makes me ponder what in glory be would be considered high priority. Maybe if the tablet reached out and kicked you in the balls whenever you looked away from it
I am fed up with this thing. I have so many issues with it, I have tried a lot of difference ROMs and get the same crap with all of them. The most annoying things are that it constantly reboots and WiFi never stays connected for more than an hour at a time. I don't even trust this tablet for any word processing or anything important. What the hell am I supposed to do with it. I am so disappointed in this tablet. I've had it since Christmas and whilw the build is great and the screen is awesome, the WiFi and the random reboots are just rediculous for a 400 dollar tablet. My HP touchpad was more reliable than this and it even had android ported to it, and this is a Nexus device that is supposed to be top of the line. Now my question is, is there a ROM out that there actually fixes the WiFi or am I going to have to sell this while its still worth money and pick up the next tablet that's going to be announced at I/O
I don't know what issues your having with the WiFi, I've seen 5ghz routers have issues.
As for the reboots I'm sure they will get worked out, I do agree they are annoying, but considered to other android tablets this one is by and far the best
Sent from my Nexus 10 using Tapatalk HD
Juicy92 said:
I am fed up with this thing. I have so many issues with it, I have tried a lot of difference ROMs and get the same crap with all of them. The most annoying things are that it constantly reboots and WiFi never stays connected for more than an hour at a time. I don't even trust this tablet for any word processing or anything important. What the hell am I supposed to do with it. I am so disappointed in this tablet. I've had it since Christmas and whilw the build is great and the screen is awesome, the WiFi and the random reboots are just rediculous for a 400 dollar tablet. My HP touchpad was more reliable than this and it even had android ported to it, and this is a Nexus device that is supposed to be top of the line. Now my question is, is there a ROM out that there actually fixes the WiFi or am I going to have to sell this while its still worth money and pick up the next tablet that's going to be announced at I/O
Click to expand...
Click to collapse
Maybe give it a last chance, install KTManta kernel, I have zero random reboot since I install this kernel. Didn't notice any WiFi problem.
http://forum.xda-developers.com/showthread.php?t=2015874
Thanks. I'm throwing the aokp 4.22 ROM on when in get home and I'll try that kernel. I appreciate it. As for 5ghz router I'm not sure, but it drops at my home, work and my school.
Bigxie or mrrobinsons aokp pub builds are good, no reboots or anything. Kts kernel is amazing has newest wifi drivers from google and a color tweak. This tablet has been amazing for me
xda hd - nexus 10 - KT infused Carbons - booooom!
So far so good on 4.22 aokp and ktskernel. I looked at my battery usage today and I didn't see any time with WiFi off and no reboots. Granted I used it for only about an hour before it slept all night but still. 10 hours with no drops is a great improvement. Thanks guys for giving Mr faith in this device. I was about to give up on it lol.
Glad it got fixed for you. This devices issues arent the device really its been with android 4.2.x from google.
Sent from my Nexus 10 using XDA Premium HD app
You should return this device. You keeping this device when it's this faulty is like rewarding Google and Samsung for making a defect product. I love Android, but I took my N10 back and got an iPad 4 and it's functionally the same as the N10 and, here's the most important part, not defective. If you really love Android, you'll take this tablet back and get something else and vote with your money.
zmattmanz said:
You should return this device. You keeping this device when it's this faulty is like rewarding Google and Samsung for making a defect product. I love Android, but I took my N10 back and got an iPad 4 and it's functionally the same as the N10 and, here's the most important part, not defective. If you really love Android, you'll take this tablet back and get something else and vote with your money.
Click to expand...
Click to collapse
Your comment completely contradicts your sig lol.. Also in my mind the nexus 10 has much more functionality than ipad... Hdmi out for one... Also I don't have a PC so I'd be SOL with an ipad having to connect to iTunes to load music... No true jailbreak available with ipad 4 yet which is absolutely necessary for me with any iDevice... Just saying not same functionality just different functionality
Its not the Nexus 10 thats defective. Its bugs in android 4.2. Read the thread. If the device itself was faulty his problems wouldn't get fixed with a rom and he has stated all his problems are now solved.
Sent from my Nexus 10 using XDA Premium HD app
iamikon said:
Its not the Nexus 10 thats defective. Its bugs in android 4.2. Read the thread. If the device itself was faulty his problems wouldn't get fixed with a rom and he has stated all his problems are now solved.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
There is no definite blame on the issues. If it was bugs with 4.2, then I wouldn't have a 100% stable WiFi connection at all times and would be having random reboots (my WiFI connection is 100% stable from what I've seen, and I can't recall any random reboots on 4.2, and very few prior to it). This was with stock also.
I'll either say it's an issue with some 3rd-party app(s), or hardware.
The hardware is not at fault if his connection works perfectly now is all im saying. Faulty wifi card would be faulty no matter what. Roms dont make hardware work better i never had random reboots or wifi issues either so i dont know but i know others' issues were solved by switching. Apps? Yeah could be.
Sent from my Nexus 10 using XDA Premium HD app
the_boo said:
Your comment completely contradicts your sig lol.. Also in my mind the nexus 10 has much more functionality than ipad... Hdmi out for one... Also I don't have a PC so I'd be SOL with an ipad having to connect to iTunes to load music... No true jailbreak available with ipad 4 yet which is absolutely necessary for me with any iDevice... Just saying not same functionality just different functionality
Click to expand...
Click to collapse
How does having an Android blog contradict Google making a defective Android product (this was absolutely the case with my N10). It's like saying because I like hamburgers that I should love eating a ****ty hamburger. Functionally, you can do the same stuff with both of these tablets. That's not really the issue at hand though.
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
iamikon said:
Its not the Nexus 10 thats defective. Its bugs in android 4.2. Read the thread. If the device itself was faulty his problems wouldn't get fixed with a rom and he has stated all his problems are now solved.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
There's a part of me that believes this, but I've never had this issue on my Galaxy Nexus that runs the exact same software.
espionage724 said:
There is no definite blame on the issues. If it was bugs with 4.2, then I wouldn't have a 100% stable WiFi connection at all times and would be having random reboots (my WiFI connection is 100% stable from what I've seen, and I can't recall any random reboots on 4.2, and very few prior to it). This was with stock also.
I'll either say it's an issue with some 3rd-party app(s), or hardware.
Click to expand...
Click to collapse
There's just so many factors that no one is talking about or thinking about:
-What if there are problems with wifi drivers/subsystem, then everyone's different access points are going to give different results
-What if there is a difference between starting with 4.2.2 as opposed to going to it from OTA
-What if there is a physical problem that only happens if you hold it a certain way
-What if there is a problem that manifests its self differently depending on peoples charge habbits
-What if letting the screen sleep is different than pushing the power button to sleep it
-What if there is a DRM issue that is dependent upon certain titles in a persons Play library
-What if there is a GPS issue that is caused by certain towers
-What if Maps has a flaw that loads only when you are physically close to a certain area
-What is the technical definition of "crash" when one of us end users reports "crash"
These are just some examples off the top of my head. I think the community has focused too much on "3rd party app" in general. Perhaps it would be worthwhile for everyone to get more oranized in the troubleshooting? I see a lot of complaining but not tons of people talking about their test actions. (Yes, this should be Googles job, but absent that...)
iamikon said:
Its not the Nexus 10 thats defective. Its bugs in android 4.2. Read the thread. If the device itself was faulty his problems wouldn't get fixed with a rom and he has stated all his problems are now solved.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
The big issue here is that there should not be so many problems with android 4.2, or if there were not for four months. I would have been fine with my nexus 10 if Google fixed the horrific stability issues within a month and a half but its been over four since I got my tablet.
I'm right there with you TC. This tablet blows to me. I don't care if iOS has less functionality, there were no random reboots, the color accuracy, brightness and contrast ratios were much better with zero backlight bleeding, blacks were much deeper and richer, twice the battery life, no slowdowns, no lag and had actual good accessory support.
I have tried just about every rom/kernel combination on here with no end to the problems. I've gotten it replaced three times. Terrible experience, and will likely not buy another Nexus device again.
I was in this expecting a comparable experience to the GSIII I had when I bought this tablet (I now use a Note 2) and I was utterly disappointed.
zmattmanz said:
There's a part of me that believes this, but I've never had this issue on my Galaxy Nexus that runs the exact same software.
Click to expand...
Click to collapse
And honestly I'm not sure what is causing the issues. Some people have them and some don't. Most people a ROM/kernel fixes everything for a few it doesn't. As for people saying they've had three or four defective devices is pretty bullish. I just know how hardware works and if the hardware is bad it stays bad most likely you're right its not 4.2 per say but more likely the Google/Samsung blobs for the n10 which include display and wifi.
Sent from my Nexus 10 using XDA Premium HD app
Well I figured I'd come back here. I swapped ROMs for a 4.2.2 build as well as installing minimal apps for now and also installed the kts kernel. I have not had a reboot yet *fingers crossed*, but like I said I have not been using the tablet as intensively as before. The WiFi seems stronger as well. I think part of the problem is my home WiFi has its own issues, but it is discouraging when my phone is sitting next to me and has 3 bars and my tab is fighting for 2. Maybe the WiFi adapter in the n10 is just inferior to that of the galaxy s3 and I am expecting too much.
All in all though, anyone having reboot issues, definitely get on a 4.2.2 build and flash the kts kernel. Thanks everyone for the help!
Sent from my SCH-I535 using Tapatalk 2
Juicy92 said:
Well I figured I'd come back here. I swapped ROMs for a 4.2.2 build as well as installing minimal apps for now and also installed the kts kernel. I have not had a reboot yet *fingers crossed*, but like I said I have not been using the tablet as intensively as before. The WiFi seems stronger as well. I think part of the problem is my home WiFi has its own issues, but it is discouraging when my phone is sitting next to me and has 3 bars and my tab is fighting for 2. Maybe the WiFi adapter in the n10 is just inferior to that of the galaxy s3 and I am expecting too much.
All in all though, anyone having reboot issues, definitely get on a 4.2.2 build and flash the kts kernel. Thanks everyone for the help!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would change router settings if you haven't already, more specifically the channel. Might have an effect on signal. The WiFi signal on my N10 is pretty awesome, compared to other devices I have anyway.
espionage724 said:
I would change router settings if you haven't already, more specifically the channel. Might have an effect on signal. The WiFi signal on my N10 is pretty awesome, compared to other devices I have anyway.
Click to expand...
Click to collapse
Yeah, I will say, from all the problems I have on the Nexus 10, wifi is not one of them. It connects and stays connected even better than my iPad 3 did. Its the stability things that bother me so much.
espionage724 said:
I would change router settings if you haven't already, more specifically the channel. Might have an effect on signal. The WiFi signal on my N10 is pretty awesome, compared to other devices I have anyway.
Click to expand...
Click to collapse
+1
Sent from my Nexus 10 using XDA Premium HD app
So I updated to 4.4 yesterday with adb sideload. Since that I was using my Nexus 7 "heavily" and I always had "buttons stucked" on keyboard, but now it's gone and I havent experienced any other touchscreen bug.
I don't think I have had any buttons sticking since I updated as well. That was my only issue with my Nexus 7 when in was still running 4.3. It would usually have a keystroke stick several times while typing things and I haven't experienced it once while typing this entire post, which is also why it keeps going because I'm trying to keep typing to see if it'll happen, and instead I just keep making spelling mistakes.
It did not fix the touch issues that may be related to grounding. In a case or stand, both Nexus 7 devices I have still fail to see any touch on numerous occasions, even single finger touch events. Manufacturing issue I guess, but we all know how G & Asus deal with those.
Let's hope it lasts... some issues are fixed temporally.
touchscreen is definitely improved for me too.
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
bokoy said:
Yeah but multitouch still fails, playing dead trigger 2 could be an impossible mission.
Click to expand...
Click to collapse
Never had multitouch issues, only single touch problems like quad touches innstead of one etc. (As u can see it happened again lol)
They poped up after the R update, and im waiting for CM11
I had single touch issues even after sending my tablet in for service. I had called yesterday to send it back again when I noticed the update was available for side loading.
After the update my screen is behaving!
I'm going to hold off on claiming that my issues are completely resolved but it is looking promising.
Sent from my Nexus 7 using Tapatalk 4
I was going to make a thread about this same thing my keyboard is good now.
Sent from my Nexus 7 using XDA Premium 4 mobile app
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.