Related
This is my third device and for 8 days it has been pretty rock solid, Yesterday I had 2 screen freezes and noticed it had been rebooting randomly.(for how long I do not know but I thought at first the app was turning itself off, than learned the device was actually rebooting itself) Today while at a restaurant I lost data and the signal would go in and out. In this same place my Vibrant gets 3-4 bars of 3G consistently. Upon arriving at home I had the same situation but additionally the GPS refused to lock or even see any sats. After rebooting twice it finally straightened out. I only have a couple of days left to decide whether to get a refund or take the chance of getting one that has even more issues or just keep this one and hope for the best. Anyone else have these or issues like them?
Are you running stock? There is a patch that fixes the slow Downs which can cause a reboot.
LG left the device in engineering mode which is why it boots up so fast.
Root and flash the patch, or wait for official gingerbread, or foot and flash CM7 which is doing me good.
LG G2x CM7 2.3.4
http://www.MiiWiiChat.com
http://www.SnapSiteAdmins.com
Yes, my data randomly gets stuck, switching to airplane mode and back fixes it sometimes, otherwise a reboot fixes it.
My GPS randomly dies and gets stuck, usually while navigating, only way I've found to fix that is yet another reboot. Cycling the GPS on and off does nothing.
Also, about once a week, the phone will crater, come back up to "system checking", decide it doesn't like something and do a factory reset! I'm actually scared every time I reboot that it'll come up reset.
Also notice if I make heavy use of the internal SD card, say, 1080p video recording, it'll randomly reboot. Defective memory?
Par for the course until LG figures stuff out. I wish this was like a computer and everything worked when it was expected to work!
Running the dexopt patch, rooted, and nothing else major.
player911 said:
Are you running stock? There is a patch that fixes the slow Downs which can cause a reboot.
LG left the device in engineering mode which is why it boots up so fast.
Root and flash the patch, or wait for official gingerbread, or foot and flash CM7 which is doing me good.
LG G2x CM7 2.3.4
http://www.MiiWiiChat.com
http://www.SnapSiteAdmins.com
Click to expand...
Click to collapse
Yes running stock and applied the patch as soon as it came out. I have not tried cm7 yet. The patch does not seem to do any good for this device.
Lightning Blue said:
Yes, my data randomly gets stuck, switching to airplane mode and back fixes it sometimes, otherwise a reboot fixes it.
My GPS randomly dies and gets stuck, usually while navigating, only way I've found to fix that is yet another reboot. Cycling the GPS on and off does nothing.
Also, about once a week, the phone will crater, come back up to "system checking", decide it doesn't like something and do a factory reset! I'm actually scared every time I reboot that it'll come up reset.
Also notice if I make heavy use of the internal SD card, say, 1080p video recording, it'll randomly reboot. Defective memory?
Par for the course until LG figures stuff out. I wish this was like a computer and everything worked when it was expected to work!
Running the dexopt patch, rooted, and nothing else major.
Click to expand...
Click to collapse
Gosh, sounds like we got the exact same phone!!LOL Almost my situation word for word!!!!!!!!!!!!!!!!!!! Do you really think that software patches will fix all the issues? I would like to believe but am doubtful. I went through the GPS debacle with the Vibrant and it still has not been fixed after almost a year for a lot of people.
As powerful this phone sounds I am hesitant of getting it because of the list of complaints. I think the g2 might be a better choice even though it has an inferior chip
The patch made a big difference with mine. After the patch is successfully applied, it will take longer to boot and won't slow down and laggy after a few hours.
I'm wondering if it was applied correctly? It would have to be applied after every wipe you've done. Thing is you have to remove the X-Factor from the equation. Flash CM7 and see if the problem is persistent or not. If it is, replace the phone. If not, then you owe me $5 cause I called it. There is a weird bug with the stock kernel. We are expecting an updated Kernel with the new Gingerbread rom that is about to be released.
@Jjday7: I wouldn't sweat it. I've been around the block and as far as hardware goes; the G2x is solid. The initial kernel is a little wonky but thank god we have CM7 right? I used my GPS today and had no problem getting a lock and keeping it. Of course I'm on CM7. I also don't have anymore random lockups.
player911 said:
The patch made a big difference with mine. After the patch is successfully applied, it will take longer to boot and won't slow down and laggy after a few hours.
I'm wondering if it was applied correctly? It would have to be applied after every wipe you've done. Thing is you have to remove the X-Factor from the equation. Flash CM7 and see if the problem is persistent or not. If it is, replace the phone. If not, then you owe me $5 cause I called it. There is a weird bug with the stock kernel. We are expecting an updated Kernel with the new Gingerbread rom that is about to be released.
@Jjday7: I wouldn't sweat it. I've been around the block and as far as hardware goes; the G2x is solid. The initial kernel is a little wonky but thank god we have CM7 right? I used my GPS today and had no problem getting a lock and keeping it. Of course I'm on CM7. I also don't have anymore random lockups.
Click to expand...
Click to collapse
I have applied it before and after GB update. I have hesitated flashing cm7 (have a couple of questions) If I do flash it and want to go back to stock or some other rom, would I have to flash a different kernel even with my nanroid? If so what would be the process for that? AS far as GApps I notice that you cannot use the one for tegra. All I have found at the cm7 site is universal which I suppose would be the one to choose. Do you know for sure?I have used cm7 on my nexus one but not on my Vibrant . Any and all help is greatly appreciated.
I also have all the same issues as the OP. Hopefully the update fixes all these issues. Did any of you notice the phone really hot when the reboots and freezes occurred?
Sent from my LG-P999 using XDA App
So where is this patch? My GPS has been non-functional this morning. Usually it just takes a LONG time to lock on. Also, last two days I've been getting the freezing while on a call. Black screen, won't come back, have to remove the battery. Early this morning after taking the phone off the charger was the first time it froze to black screen while not on a call.
Jjday7 said:
As powerful this phone sounds I am hesitant of getting it because of the list of complaints. I think the g2 might be a better choice even though it has an inferior chip
Click to expand...
Click to collapse
To my G2x friends above. Keep swapping phones. Don't give up. I was at my wits end until I swapped out a couple of times. My new phone has no bleed issues and the random crazy stuff has completely stopped.
lilaliend... take it back. get another. It should not do that. It will be nothing but a head ache/heart ache until you do. I get a solid lock within 5 seconds.
Jjday... if you get one, run the heck out of it the first few days to see if all is good. Any issues pop up...swap it.
This is a solid phone that seems to have had some issues with the first run of production. There are many detailed posts on how to fix any minor annoyances. TMobile sold out of them for a reason.
Swap bad behaving phones then read, read, and then read some more. The potential of this phone is awesome. I am a die hard WM guy who has been converted.
So .. I ended up exchanging my g2x in via t-mo customer support since I was out of the window of taking it back to the store (having 4g/wifi toggle issues etc, random reboots). The new phone is by far better, but I am having issues with the GPS still. It will see 10 satellites, all locked on (green via GPS test) but it takes forEVER to lock. When I first took the phone out of the box it locked within seconds inside my house ... should I send this back for another one again?
My Charge has seen decreasing performance. I'm running 2.3.6, the last TBH leak, and I was initially getting Quadrant scores as high as the 1400's. Now, I'm down around 700! Needless to say, the phone has gotten laggy.
I'm using OSMonitor to look at what processes are busy, and I keep seeing k3g_wq running, using anywhere from 20% to just under 40%. Never used to see it before. I figure it's a system process, as if I kill it, it starts back right away and always has the PID of 54.
I've searched here and with Google and I can't find anything about what this process is. From the name, I might guess it has something to do with 3g access, but it's running like that even when I go into airplane mode.
Thanks for any info.
just a suggestion but since GB has officially been released i would wipe cashe,dalvik and data. Then flash infinity, tweak stock or danalo's stock debloated/deoxided rom. Then flash imoseyon's repacked voodoo kernel. you will get a quadrant score of around 2000. Im currently running infinity ext4 without tsm, imoseyon's kernel and v6 script. its been pretty good for me so far. i have no complaints.
But if anybody else has a better setup. I myself would like to know as well
Wow, that's quite a prescription! For now, I'd just like to know what that process is and why it's running, so I can try to get it to back down.
Thanks for the tips. BTW, I was running voodoo lagfix back in the day, and it got me quadrant scores similar to what I was getting with this GB ROM (not 2K, but 1600 wasn't unusual); I'd like to get back to that point. Without necessarily starting over.
You're basically going to have to. The TBH leak is really old.
Sent from my SCH-I510 using xda premium
The TBH leak isn't that old (I downloaded it on Nov 7th), and the age of it doesn't make kernel processes run away. It's GB 2.3.6, basically the same as the latest OTA. And it only started doing this recently.
I'm afraid either something I've installed recently is triggering this (the better option, as I can start uninstalling stuff until the problem goes away), or there is something gone wonky with the hardware itself that the kernel is reacting to (obviously the worst case). That wouldn't surprise me, as this is my 3rd Charge, the first two having had lost their minds, running really hot and then rebooting every few minutes (this on the stock OS, rooted with the voodoo lagfix kernel).
More data (if there's anyone out there who actually knows what that kernel process is): OS Monitor's "messages" list is flooded with this:
"k3g_work_func: fifo entries are less than we want"
I get dozens of these PER SECOND.
Again, if anyone has any insight on what that process is about, glad to hear from you. Those who say "Nuke and pave!", not so much.
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
"Nuke and pave" still seems like the best option.
Sent from my SCH-I510 using xda premium
kvswim said:
Fifo is an io scheduler if I remember correctly. Try changing it and seeing what happens.
Click to expand...
Click to collapse
Fifo is a general term for a queue -- "first in/first out". Many kernel processes live their lives managing queues. This one is complaining about it's queue being shorter (fewer entries) than it thinks it should have.
Did I see your name attached to a thread about trying to compile a kernel? If so, would you do me a favor, so I don't have to get all into git so I can get to the AOSP code, and grep for "k3g" and/or "k3g_wq" (still sounds to me like like "kernel 3g worker queue") and see if you can see what it does? Nothing in depth, just in general what it handles.
kvswim said:
"Nuke and pave" still seems like the best option.
Click to expand...
Click to collapse
Funny thing happened today. It was getting worse and worse. Battery stats showed a shocking thing--for the first time ever, Display wasn't the biggest battery hog, it was Android OS!
So I decided to just reboot, to see if I could get it back to good enough to do backups and start the nuke-n-pave process. I had rebooted a few times over the last few days, and it didn't solve anything. Today it did! Back to normal, and I ran Quadrant twice and got a 16xx on the second run. Nice. A few hours later, and it's still good. Keeping my fingers crossed.
Oh, I had also uninstalled DropBox (which I wasn't using yet anyway) and this massive Gameloft game, "Tintin". Those didn't help, before reboot. But maybe those, coupled with the reboot, did.
I may still nuke and pave, but probably with the stock GB and just root after that. And keep hoping the CyanogenMod comes out with a ROM for it.
Thanks.
I'm gonna revive this thread because I have a similar problem. My dad's charge is fully stock. He has never messed with anything. It was fine the whole time he had it except today. He has not used it at all today (10m screen time in 12 hours, and half of that was me trying to fix it) and the battery drained down to 30% all by itself. Me being the tech guy, he gave it to me and I checked battery usage. Android OS was reported to be using 89%. Cell standby was at 3%, and display came in last at 2%.
Since "Android OS" is very generic, I used adb to put the xda version of betterbatterystats on his phone, and under process, there is this thing called "k3g_wq" with almost a full bar. Under other, it shows the phone being awake 98.2% of the time. This problem only arose today. As he has not used the phone at all, there would be no rogue apps unless something just turned up. I disabled automatic updates in the market since the stock tunewiki app updated its permissions to read SMS (spyware???).
Does anyone have a solution to this besides factory reset?
K3G is a sensor, specifically the level sensor. Not sure why it would take up system resources, but I would think turning off auto screen rotation may be one method to try and limit its use and battery drain.
See my posts on k3g_wq above. Note that I found error log message about it not having enough entries--thus my supposition that wq == worker queue. If imnuts says it's a level sensor, then that's got to be it; from the name, I figured k was for kernel and 3g was...well...3g.
In my case, I was able to see it using OS Monitor (free in the market), using consistently about 30% of the CPU, which resulted in the OS being the largest consumer of battery.
And, for me, it finally just stopped doing it, after one more reboot. Hasn't come back. But every time the phone gets a bit laggy, I go look at that process list.
On another note, we're using my Charge at work as a test phone for our Android app, as it makes it blow up like no other device we have.
I have noticed a sensor leak associated with google maps. Try opening maps in that phone, exit out of it and see if sensor usage persists. I hadn't mentioned it before assuming it was unique to my device.
Sent from my SCH-I510 using Tapatalk
I also notice runaway usage of k3g_wq in the last week. I have stock OTA EP4 and it had been running fine for many weeks with no issue. So there has to be something that changed recently. My guesses are the new version of Google Maps, or new version of Tiny Flashlight with the "shake on lockscreen" feature. I don't see Tiny Flashlight running any services, but since I disabled the shake on lockscreen feature my k3g_wq usage seems to be OK.
I factory reset the phone and the problem disappeared.
Sent from my pocket-sized, Linux-based computer using electromagnetic radiation.
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Scrappy1 said:
Ooooh, I just had the k3g_wq high usage issue while actively using my phone. OS Monitor showed it using 40% of processor all the time. So I tried the following:
1) disable auto-rotation. No impact.
2) started and exited maps. No impact.
3) Unistalled maps update and tiny flashlight. No impact.
3) Turned off wifi, GPS, data, BT. No impact.
4) Killed every running service that would stay killed. No impact.
5) Rebooted. This fixed it for now.
This makes me think back to the flash destroying early leak of GB for the Fascinate. This ROM would also have a similar process that got stuck using lots of CPU. On that dirty ROM, auto rotation needed to be enabled to see the issue. However once you had the problem, it wouldn't go away until reboot. The only safe thing was to disable auto rotation, reboot, and never reenable. Perhaps the Charge is now the same.
My opinion of Android and Samsung is not improving. In fact I do have some anger issues.
Give me a freaking iPhone at this point, I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
xdadevnube said:
Must resist urge to flame... Seriously though, I think it's just good practice to get used to flashing ROMs, making backups, and learning to mod your phone. I've had some curious problems that only a reflash would solve. In any case, the only thing worth a damn on the iPhone 4S is the camera. The internals are fast, but what's the point?
Click to expand...
Click to collapse
If you're a geek and have time to flash and mod, that's great for you. I used to be in this camp. Now I just want my phone to work without contanstaintly modifying it, babysitting process and battery life. I want a phone I could recommended to ANY friend or parent without worrying. The Charge definately isn't it.
My brief history in Android:
Samsung Fascinate: got tired of poor battery life and runaway processes.
Samsung Charge: got tired of poor battery life and runaway processed. Also, voice quality is horrendous.
Samsung Galaxy Nexus: Tons of reviews of runaway "Android OS" proccessed during idle. Voice quality is bad and outbound audio drops.
With each generation, problems weren't fixed and Google/Samsung continue their careless ways. To me its just sloppy, sloppy, execution.
Scrappy1 said:
I'll do anything for a quality engineered and tested device that actually works out of the box. Android and Google are sloppy if nothing else. Open sloppy mind you.
Click to expand...
Click to collapse
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
charlie_c said:
You're running a leaked, unofficial build that was part of the testing process, not the result of the testing process. If it's a software related problem (either due to a rogue app or to a bug with the leaked build), there's no one to blame but yourself for installing it. If it's a hardware related issue on the other hand, there's probably warranty coverage that would cover the problem.
Go back to stock, OTA, unrooted. See if the problem persists. Reinstall your apps. See if the problem persists. If it does, your phone will be "stock" and you can pursue a warranty claim.
Click to expand...
Click to collapse
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Scrappy1 said:
No man, i already mentioned, I'm stock OTA EP4. I'm also unrooted.
Click to expand...
Click to collapse
Sorry, thought you were OP
Sent from my SCH-I510 using Tapatalk
k3g_wq ... it came back, and then I killed it, I think
OP here.
Today I was looking at my Charge and marveling at how I was getting pretty good performance but better battery life due to my latest tweaks in SetCPU, when I looked at battery usage: Android OS was creeping up on Display as juice-user No. 1.
Uh oh.
So back to OS Monitor, and sure enough, there's k3g_wq on a steady 25-30% of the CPU.
Opened and closed Maps--no luck.
Killed its process in the process list in OS Monitor (it appeared to be swapped out, but what the heck)--no luck.
Opened another cool app called Elixir that shows you sensors, and lets you enable/disable them. Hrm...gyroscope, rotation and orientation sensors. All were off; turned each on, then back off.
Looked in OS Monitor and...YES! k3g_wq is gone!
Wild guess time, but apparently the start-up/shut-down of whichever sensor it is doesn't always work right, and leaves that service looking for its momma (that's a highly technical description of the problem, sniff).
Anyway, if you're seeing k3g_wq running wild, give that a try. Next time I do, I'll try them one at a time, see which one does the trick (assuming it's only one).
LDog
PS -- Kudos again to imnuts for letting us know it's the level sensor. Or sensors.
Hey guys a couple of days ago my Nexus S batter started only last 6 hours give or take and hour. Before then I would get 15-24 hours depending on the kernal I was using. I did not get a phone call since the battery drain started happening until yesterday and the call would drop in 10 to 30 secs. I cannot make a call at all, they are all dropped, sometimes it won't even stay online long enough for the person to pick up on the other end.
The battery info showed the screen as being the biggest drainer @ 40-50%.
I was on CyanogenMod 9 V7 with its own kernal, and have been on it since the day it came out with no problems. Previous to that I was just on incremental versions of CM9 (no nightlies) any many months ago I was switching between the Matrix kernal and Glados.
I have done many complete wipes and reinstalls, flashed different radios, I am even now back to stock, and nothing seems to have fixed this.
Does anyone know what could be wrong or do you think it is toast and I will have to get a new phone?
Bigalsworth
got it figured. toggled airplane mode on and then off and it seemed to fix everything.
Glad to hear you got it fixed and posted your solution. It may help others who may experience the same issue.
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version
Hi everyone.
First off, I'd like to say that I don't like opening new threads, and I always read up on my problem first, but I'm simply at my wit's end.
The problem is fairly common (not only on nexus 5 phones), and something a lot of you forum guys have encountered and tried to help with, with more or less success.
Basically, my WiFi doesn't work, it shows 'turning on WiFi' most of the time, and sometimes (fairly rarely), has a couple of hours where it reboots to no end, but I'm thinking that's a power button that sticks. It usually fixes itself after I gently but firmly stroke it (lol) and doesn't happen again for weeks. The WiFi issue started randomly, totally out of the blue, and never happened before to any of my phones (it might have started a couple of days after the last OTA security update, but I can't say for sure). The phone was a 100% stock 16gb Nexus 5.
What I've tried (some steps even multiple times, with different variations):
- removing the sim card
- switching airplane mode on/off
- factory reset (3 times in total think)
- wiping cache
- reflashing stock ROM
- reflashing stock everything
- flashing TWRP and rooting, and manually changing/removing either the .macaddr and .btaddr files, or changing/removing their respective folders
- playing with ownership of those files
- flashing CM, flashing a custom kernel and flashing Paranoid Android
- all in all, i've wiped and rebooted the device like 50 times
Honestly, I don't know what I've missed, I've been at it for days, and I'd be very grateful if someone would point out an oversight.
Also, what's weird, my bluetooth didn't work too, but after i tinkered with .btaddr and .macaddr, it now works perfectly, no matter what I throw at it. This is what gives me hope that I still can resolve this issue without paying for a new motherboard/phone.
Thanks in advance, guys, you've been truly helpful so far.
A defective wifi chip could be the cause of the problem and, in my experience, is not that uncommon. I have come across two n5 and two Samsung s4 phones that work perfectly except the wifi either won't turn on or tries to turn on for about 10 minutes.
I tried different modems, bootloaders, and roms without any success.
Yeah, sadly, that's what I'm thinking too. I had some hope because bluetooth works, but not anymore. I've kinda already made my peace that I'm gonna have to spend +$200 on a repair or $400 on a new phone. I'm just thinking if anyone knows something that helps that I haven't tried yet, please come forward, possibly before I take it to a service centre :laugh:
Maybe look for a used N5 with a smashed screen and working motherboard?