Related
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
Hi.
I recently i noticed onMy 5 month old edge there is screen flekring. this start 2 week ago and was so minimal and stayed for sec and disappeared. today its wont disappeare. and stayed for longer time
i made video showing my problem Here
and advise or tips
Note my phone out of warranty at least local warranty.
. Thank you
Hey ,
did you try to flash stock firmware ?
i never root the device its running stock firmware. ? Maybe i need to test different Rom.
phone back to work normally and flicking happen from time to time. and for short time. its kinda wired!
murad052 said:
i never root the device its running stock firmware. ? Maybe i need to test different Rom.
phone back to work normally and flicking happen from time to time. and for short time. its kinda wired!
Click to expand...
Click to collapse
Hi, I have the same problem too. Could you share your solution with me?
Mine display today gone crazy, I already reboot it and still the same, I will reset but I think is hardware.
cavags5 said:
Mine display today gone crazy, I already reboot it and still the same, I will reset but I think is hardware.
Click to expand...
Click to collapse
It's hardware issue.
https://forum.xda-developers.com/showpost.php?p=70499471&postcount=73
cavags5 said:
Mine display today gone crazy, I already reboot it and still the same, I will reset but I think is hardware.
Click to expand...
Click to collapse
FİXED İ AM METHOD KERNEL FLASHED REPAİRED
https://forum.xda-developers.com/s7-edge/how-to/troubleshoot-gray-line-problem-fixed-t3558262
hasanben35 said:
FİXED İ AM METHOD KERNEL FLASHED REPAİRED
https://forum.xda-developers.com/s7-edge/how-to/troubleshoot-gray-line-problem-fixed-t3558262
Click to expand...
Click to collapse
Huh? Wha? That's a fix for screen flickering?
Op, search youtube for S7 Edge screen flickering and be amazed! Brand new S7s were doing that.
If you slide the brightness to max, it should stop. Or if bright light hits the dimming sensor, it stops.
TRoN_1 said:
Huh? Wha? That's a fix for screen flickering?
Op, search youtube for S7 Edge screen flickering and be amazed! Brand new S7s were doing that.
If you slide the brightness to max, it should stop. Or if bright light hits the dimming sensor, it stops.
Click to expand...
Click to collapse
Exactly, at max brightness stop.
But i think is hardware.
And when gets more hot it's worst.
I had the same problem on MM but fixed all problems on Nougat.
Wu187 said:
I had the same problem on MM but fixed all problems on Nougat.
Click to expand...
Click to collapse
I had Nougat since beta, and I have latest BTU more than a week since last update but only yesterday starts doing this. I will try a reset if it continues, I will send it to warranty.
nougat echoe rom problem solved ael kernel problem fixed !!! no max brightness problem ael kernel and echoe nougat rom fixed friends device
---------- Post added at 09:42 PM ---------- Previous post was at 08:56 PM ----------
OH MY GOD ANDROID MARSMALLOW STOCK ROM AND pwmfree-v11_g935f kernel work gray line problem fixed
https://www.dropbox.com/s/88bdtdgqvraah85/pwmfree-v11_g935.zip?dl=0
Most likely an issue with the AMOLED PWM implementation/controller, the flicker free Kernel doesn't use PWM to control Brightness.
So this might be an suitable workaround for users without warranty or possibility of repair.
Wootever said:
Most likely an issue with the AMOLED PWM implementation/controller, the flicker free Kernel doesn't use PWM to control Brightness.
So this might be an suitable workaround for users without warranty or possibility of repair.
Click to expand...
Click to collapse
I already reset and now flash M and gonna send to warranty.
They fix it.
cavags5 said:
Mine display today gone crazy, I already reboot it and still the same, I will reset but I think is hardware.
Click to expand...
Click to collapse
fixed kernel flash my tested fixed screen
hasanben35 said:
fixed kernel flash my tested fixed screen
Click to expand...
Click to collapse
I need my warranty and don't gonna root it only because of this.
murad052 said:
Hi.
I recently i noticed onMy 5 month old edge there is screen flekring. this start 2 week ago and was so minimal and stayed for sec and disappeared. today its wont disappeare. and stayed for longer time
i made video showing my problem Here
and advise or tips
Note my phone out of warranty at least local warranty.
. Thank you
Click to expand...
Click to collapse
Its a hardware issue, happened to me on day one, returned phone and they replaced the screen.
I fixed my phone follow link https://www.xda-developers.com/nexus-6p-bootloop-fix/. Now my phone is back but I was wondering how to bring phone run 8 cores instead using 4 cores is very slow and sometime freeze. Is there any way to fix performance?
Maybe Android 8 will fix it ?
Thank you.
AFAIK the answer is no, it is not related to Android.
psuputspon said:
I was fix my phone follow by https://www.xda-developers.com/nexus-6p-bootloop-fix/. Now my phone has back again but I was wondering how to bring phone run 8 cores instead now is 4 cores is very slow and sometime freeze or Is there any way to fix performance? May be Android 8 will fix it ? Thank you.
Click to expand...
Click to collapse
No. The bootloop "fix" is a workaround that permanently hobbles your device, allowing you to make backups and remove any photos/data you need from the phone so you can transfer to your next phone. Since your phone has a hardware defect directly related to the motherboard, there is no software update that will help. Take everything you need off the phone asap and start looking for your next phone.
v12xke said:
No. The bootloop "fix" is a workaround that permanently hobbles your device, allowing you to make backups and remove any photos/data you need from the phone so you can transfer to your next phone. Since your phone has a hardware defect directly related to the motherboard, there is no software update that will help. Take everything you need off the phone asap and start looking for your next phone.
Click to expand...
Click to collapse
Um...no? I mean, it's not that it hobbles your phone. And it's not that it's just a workaround to make backups. In fact it runs almost the same. Turns out, after some digging in, @XCnathan32 found out that even a normal 6p was throtling it's 4 BIG cores from 2ghz to 800mhz, because of which the phone was heating up and marginally running better as compared to the current fix. Now it doesn't heat up and runs slightly lower (not even noticable) than what it used to.
My phone, for one, works almost identical. No dip in performance for my usual activities - no games. Occasionally I run Drastic DS for some emulated NDS games. Never had a bootloop since.
As for the original question: the bootlooping will still occur. It seems to be a hardware issue as far as what I've followed in XCnathan32's posts.
The same link that OP has, will take him to the fix with the flashable Oreo kernels as well.
Tivaldi said:
Um...no? I mean, it's not that it hobbles your phone. And it's not that it's just a workaround to make backups. In fact it runs almost the same. Turns out, after some digging in, @XCnathan32 found out that even a normal 6p was throtling it's 4 BIG cores from 2ghz to 800mhz, because of which the phone was heating up and marginally running better as compared to the current fix. Now it doesn't heat up and runs slightly lower (not even noticable) than what it used to.
My phone, for one, works almost identical. No dip in performance for my usual activities - no games. Occasionally I run Drastic DS for some emulated NDS games. Never had a bootloop since.
As for the original question: the bootlooping will still occur. It seems to be a hardware issue as far as what I've followed in XCnathan32's posts.
The same link that OP has, will take him to the fix with the flashable Oreo kernels as well.
Click to expand...
Click to collapse
Have you heard reports from people that got bootloopd again after applying the 4 core fix?
darkriff said:
Have you heard reports from people that got bootloopd again after applying the 4 core fix?
Click to expand...
Click to collapse
I haven't read any such. There may be. I believe the best person to answer this would be the creator of the bootloop fix, since people with such issues would PM him.
v12xke said:
No. The bootloop "fix" is a workaround that permanently hobbles your device, allowing you to make backups and remove any photos/data you need from the phone so you can transfer to your next phone. Since your phone has a hardware defect directly related to the motherboard, there is no software update that will help. Take everything you need off the phone asap and start looking for your next phone.
Click to expand...
Click to collapse
So the boot loop issue has been definitively identified as a hardware issue then? I just got paid out for my Square Trade insurance on my 6P and was considering going back hoping against hope that O would finally fix some of this stuff. Damn shame...
BushidoCowboy said:
So the boot loop issue has been definitively identified as a hardware issue then? I just got paid out for my Square Trade insurance on my 6P and was considering going back hoping against hope that O would finally fix some of this stuff. Damn shame...
Click to expand...
Click to collapse
BLOD is a hardware defect plain and simple. No software upgrade (or workaround) will ever change this but not all devices are affected. I think the chances of you finding a NEW 6P are pretty slim... but still possible. We have two 6P's that are approaching 2 years old and no sign of battery degradation or any other issues. I wouldn't touch a refurb at this stage. Probably the best bang for the buck would be a Pixel XL, now the new ones are in the pipeline, prices should be dropping significantly.
I get alert to update Android 8 today. It's worth to update?. Anyone who has experience update the phone with patch fixed bootloop. Is there any concern?
psuputspon said:
I get alert to update Android 8 today. It's worth to update?. Anyone who has experience update the phone with patch fixed bootloop. Is there any concern?
Click to expand...
Click to collapse
If your device is stock there is no concern and yes, you should take the update . If you had the bootloop issue and needed to apply the workaround to your device to get it working, then you will have to wait because the update would overwrite the fix.
v12xke said:
If your device is stock there is no concern and yes, you should take the update . If you had the bootloop issue and needed to apply the workaround to your device to get it working, then you will have to wait because the update would overwrite the fix.
Click to expand...
Click to collapse
I tried to OTA update but it can't install then I decided to flash stock with google image and flash to fix bootloop again then I can't open it stuck in loading animation. my device is gone now, Dead completely.
Ps. I installed twrp also before flashing is OTA problem to update
Has anyone else here played this game on the essential phone? I have a couple of strange glitches. I initially thought they were associated to my original faulty device, but after receiving my warranty replacement that is not faulty the same issues still persist on PUBG Mobile. So I am assuming it's something with this phone in general.
First glitch is some artifacting during the loading screen on the notch end of the phone. I am assuming this is because of the screen resizing to accommodate for the notch. It seems like it starts to attempt to resize the screen a few times in a row every once in a while resulting in what looks like some screen glitching. I've noticed this in other apps while using them too like chrome and OfferUp. Looks like every once in a while the app suddenly attempts to resize back to full screen mode for a split second, then immediately shrinks back down again to cut out the notch area.
Other issue is while using both fingers on the screen at the same time. Moving while aiming for instance it will spin my character around a little bit.
Doesn't display any of this behavior on any other phones I've ever had. I already contacted the publisher of the game but Wondering if anyone else has these issues and knows a workaround.
Android P fixes all of the touch related bugs. Game is running flawlessly on my phone
crixley said:
Android P fixes all of the touch related bugs. Game is running flawlessly on my phone
Click to expand...
Click to collapse
I'm on P also, but I still get the glitch that I got in Oreo
Thomas Cloutier said:
I'm on P also, but I still get the glitch that I got in Oreo
Click to expand...
Click to collapse
Strange, I don't at all. I full wiped and flashed from fastboot though. Did you ota?
So you still have the graphical glitches?
How do I get P?
Also is it possible to force games and other apps to utilize the full screen pace around the notch? As much as I don't like apple I do notice in YouTube videos that it does fully utilize the notch area on the iPhone X.
Alright nevermind found the settings in developer options from YouTube video to force all apps to use the notch area.
crixley said:
Strange, I don't at all. I full wiped and flashed from fastboot though. Did you ota?
Click to expand...
Click to collapse
I flashed the ota through adb, did not factory reset though. I think the issue is involving the multi touch that was broken in and 8.1, and I don't think Google has fixed the issue
Thomas Cloutier said:
I flashed the ota through adb, did not factory reset though. I think the issue is involving the multi touch that was broken in and 8.1, and I don't think Google has fixed the issue
Click to expand...
Click to collapse
Yes they have. Lol I'm using it fine right now.
crixley said:
Yes they have. Lol I'm using it fine right now.
Click to expand...
Click to collapse
Well I'm still having issues with mine
Thomas Cloutier said:
Well I'm still having issues with mine
Click to expand...
Click to collapse
Like I said before, I flashed the full fastboot file, not just the ota. It is fixed completely. You could try that.
Yes! God, I thought I was the only one with the multi touch issue..but I'm too lazy and stupid to get P so I suppose I'm out of luck.
There's a fix for the multi touch glitch bug. It's a magisk module called "Pixel 8.1 multi-touch fix".
Let me warn you, DO NOT install it if you are on the stock essential ROM, because it will fail to boot. It is only safe on AOSP based ROMs. I can only vouch for myself that it works flawlessly with lineage. If you are on stock ROM you'll have to wait until essential releases a fix.
I just read up on it a little. Apparently it's an issue with all phones running 8.1.0 Oreo witch I did not know. My original essential PH1 was faulty, kept crashing and rebooting so I thought this was part of the faulty device.
Looks like they plan to release a fix in June security update.
Nickvanexel said:
I just read up on it a little. Apparently it's an issue with all phones running 8.1.0 Oreo witch I did not know. My original essential PH1 was faulty, kept crashing and rebooting so I thought this was part of the faulty device.
Looks like they plan to release a fix in June security update.
Click to expand...
Click to collapse
So then are you on Android 9 aka P or not?
No. Just going to wait until they release the fix for 8.1.0
i thought the pixel now has the fix from the May patch... maybe our June update will fix this? How is P ? stable enough for daily driver.. cause i like my chicken dinner!!
Sent from my PH-1 using Tapatalk
Incredible... P preview makes this phone amazing.. touch response is way better.. pubg is soooo much more playable.. no more touch issues or screen jumping around.. got me some chicken just a few minutes ago
Sent from my PH-1 using Tapatalk
stinger4321 said:
Incredible... P preview makes this phone amazing.. touch response is way better.. pubg is soooo much more playable.. no more touch issues or screen jumping around.. got me some chicken just a few minutes ago
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
The difference is insane right? Night and day. Even if there were any bugs, which I haven't noticed any, I still wouldn't be able to go back I don't think.
Way smoother, all touch bugs fixed, better battery life... What's not to like?
crixley said:
The difference is insane right? Night and day. Even if there were any bugs, which I haven't noticed any, I still wouldn't be able to go back I don't think.
Way smoother, all touch bugs fixed, better battery life... What's not to like?
Click to expand...
Click to collapse
Yep.. only bug I have seen is that wifi isn't on when phone is restarted..
Sent from my PH-1 using Tapatalk
crixley said:
The difference is insane right? Night and day. Even if there were any bugs, which I haven't noticed any, I still wouldn't be able to go back I don't think.
Way smoother, all touch bugs fixed, better battery life... What's not to like?
Click to expand...
Click to collapse
Yep, everything is great for a dev preview. I fixed my PUBG, by just uninstalling, then reinstalling the game. Runs flawlessly
Hello everyone. I very recently updated my phone with the mokee nougat rom and while the rom is very good, I very been experiencing that the screen heats up after a period of usage (not incredibly but noticeably) while noticing a particular smell when removing the back cover (the kind of smell when plastic is heating up). Has anyone else experienced something like that using a note 3 n9005 ? Is so, what could be the cause of it ?
As that rom thread is closed since oct 2017.
Suggest wipe and flash stock rom to test hardware .
InfinityBlaze said:
Hello everyone. I very recently updated my phone with the mokee nougat rom and while the rom is very good, I very been experiencing that the screen heats up after a period of usage (not incredibly but noticeably) while noticing a particular smell when removing the back cover (the kind of smell when plastic is heating up). Has anyone else experienced something like that using a note 3 n9005 ? Is so, what could be the cause of it ?
Click to expand...
Click to collapse
Yio may have the "increased touch sensitivity" option enabled. The screen gets warmer whil using it.
Is that option on all Note 3 ??
JJEgan said:
Is that option on all Note 3 ??
Click to expand...
Click to collapse
As far as i know yes. In kit kat it is under Settings - Controls. It may be in a different place in newer firmwares.
I've been searching for a screen sensitivity option in the settings but couldn't find one (currently on the stable 7.1 mokee build). Also, I noticed that in mokee the whole screen heats up while in phronesis v7 just the very top of the screen and not nearly as much.
Their is no screen calibration setting in later roms.
Poster has none Samsung rom and that may well be the problem .