Related
We're trying to determine the "root" (pun intended) of the problem so if you wanna come in here and start a fight go find a local bar to do so. We need to try and locate the source of the problem so either post something useful or walk away.
There seems to be some confusion and I dont know if its being ignored or what but theres an issue with these kernels that needs to be looked into further before new ones continue to be released.
Theres an obvious problem for a good amount of people and everytime I look I see comments that there isnt a problem. So heres everything I could quickly find regarding it.
Now Im not trying to be a **** about this but I dont get how the issue is unheard of when its one of the biggest topics in this section. And so we're clear, this is happening in ALL kernels. Unfortunately its been more profound in Zedos because it seems more people went with his method.
All Im asking is before more and more kernels are released that someone at least acknowledge the problem and see if it can be addressed before more and more people root and start complaining because they were told there was no LO.S. bug
zedomax said:
data drop? dunno about that, this shizzle will not drop. It's ZEDOMAX!
Click to expand...
Click to collapse
zedomax said:
jump and we will find out. no they should be worked out. there was no data loss kinks in da first place, where did u get that?
Click to expand...
Click to collapse
________________________________________________________________________________________________________
joetemp75 said:
Man I was fine then I flashed v5 and got the no signal issue
Click to expand...
Click to collapse
SupahDave said:
Everything seemed to be fine last night but today I've had 4 separate times now where my phone has lost signal all together and needed to be rebooted to get phone/data back. When this has happened I tried going into About-->Status to see if I could see anything odd and I kept getting a FC of com.android.phone
Click to expand...
Click to collapse
jimbobtexas said:
I did. No love. I'm without a signal, period.
Click to expand...
Click to collapse
MILH0U5E said:
Got the no signal issue here too. I put it in airplane mode overnight and upon waking this morning the no signal circle was there. I had to do a reboot to get 3g and cell signal back.
Looking forward to seeing this process develop.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
wbyrd said:
Yeah this just happened to me too, everything was fine this morning then I played a game of solitaire and after going back to my home screen I saw the circle. Rebooted phone and everything came back on. It's possible that the circle was there before I played the game of solitaire but I didn't notice until right after I quit playing.
Hopefully it gets straightened out soon. At least rebooting fixes the problem, I can handle rebooting for a little while if needed.
Click to expand...
Click to collapse
plmiller0905 said:
I can't really deal with the issue of having no service. My daughter has a heart issue and can't afford to miss a call. It's not like I walk around all day literally looking at my phone's screen seeing if I have service or not.
I did reboot...so like your's my service is back up.
But I definitely hope this gets fixed soon. I'd rather have root with broken heptic feedback than the inability to receive calls.
But I'm sure the Op the get it fixed...
Click to expand...
Click to collapse
volwrath said:
I've had a dead call issue and also tday my radios were just dead and there was a circle in the middle of the notification barr. A reboot fixed the issues each time, but I think it might be a problem. I thing newer kernels will also fix said issues. Still very satisfied
Click to expand...
Click to collapse
JLine05 said:
I am having the issue of the phone (voice) and sms not working. Strange because everything else is working fine. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
mcflargen said:
Still seems to have the data drop issue. Popped it on the second u dropped it, was great till a min ago. least a "restart" fixes it.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
joetemp75 said:
Man I just lost data again. This sucks
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
kindaskimpy said:
I'm giving this one a try because with the zedomax kernel I kept losing 3G and CDMA calling and not even noticing it unless someone told me they'd been trying to reach me for hours. A quick reboot would solve the issue but then it would happen again.
I'll report back and let you guys know if this one is giving me the same issue.
Click to expand...
Click to collapse
bbedward said:
I did this one because losing service on the other one, haven't lost it yet but its only been a couple hours
Sent from my sprint galaxy s2
Click to expand...
Click to collapse
fordmanck said:
I tried both, i'm back on this one. I lost service with zedos twice and haven't on this at all.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Telling you right now someone is going to come in here and go "this belongs in General" then a mod will move your thread and deduct 5 points from something, not sure...but just a heads up
I also see a lot of people having issues, but I'm now on day 2 of flashing Zedo V1 and have yet to experience any of these issues. Not sure what I did different, but everything just works... The only thing I did was after rooting was getting my MSL from Sprint and erased the proxy servers in the ##3282 menu.
EDIT: Ok, I just lost service 1 1/2 day after rooting... Bug finally hit me..
I dont mind it being moved and I have no clue what the deduction in "points" does but I'll deal with it.
Now Im getting much better battery but I know people are still losing service on the new OC kernel. My roommate happens to be on e the unlucky ones.
Man...thanks for posting this. Hopefully the mod doesn't close this thread. This definitely is a concern and a serious matter. I don't care if these kernels are, "use at your own risk" these kernels should've been listed as betas, and/or the bugs should've been listed and further testing should have been. If those steps were taken, I bet a lot of people would've held back from flashing them. I know I would have.
Shabby posted this earlier in the other thread (post 160):
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
One thing that got to me was this morning I woke up, hoping to see a stock kernel and/or a way to return to stock. And instead, I see a new overclockable kernel. To me that's just not right. I think that you have to prioritize. That's like putting out a rom that has all data broke. Then instead of fixing it, you put out another rom...while disregarding the issues with the first rom. At least acknowledge the issue and let everyone know it's been worked on....don't just blow it off.
I know some of the devs over in the Evo forums was good about this....if something went haywire with one of their roms or mods...they were all on top of it to get the issue fixed and they also communicated with posting updates on the matter.
Like I said, hopefully the mods don't close this.
I'm definately gonna follow this thread...thanks Wingzfan
i rooted yesterday using zedomax method, did the OC kernel last night.. havent had any issues so far ..
plmiller0905 said:
Shabby posted this earlier in the other thread:
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
post 160
I'm definately gonna follow this thread...thanks Wingzfan
Click to expand...
Click to collapse
Bubby does have the stock kernel pulled. I was testing it till 1:30 in the morning but he's gotta recompile it. It was bootlooping so today thats his first order of business.
As for the kernels, I flashed it by choice. I dont blame the devs for ANYTHING, Im just saying acknowledge theres a bug and lets see how to resolve it.
I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?
Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...
OrygunGal said:
I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?
Click to expand...
Click to collapse
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.
Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...
wingzfan said:
Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
Sounds good...can't wait
Sent from my SPH-D710 using Tapatalk
This is an issue that started with mine also yesterday. But not only did I lose data but gps also. A reboot fixed it but I would like to know whats going on. I just came from the evo 3d and there was an issue that had to do with the prl so I am going to give that a shot with the 11115 prl that fixed the evo. Will post back with the results later today.
On V5, Ive only had the loss of data once in about 12 hours, versus about 3 times on Zedo V1.
I also did http://forum.xda-developers.com/showpost.php?p=17703908&postcount=11 for the hell of it to see if that helped (even though I got it at a sprint store)
For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.
wingzfan said:
Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
I would think it would be widely discussed as well so that seems odd. I'm waiting to see what evolves or at least for stock kernel (an undo) before flashing a rooted one. I don't have TEP.
It's still a bit early for the issue to be too widely discussed.
dmarden said:
For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.
Click to expand...
Click to collapse
Nice. I was told by a helpful Sprint cust. serv. rep. a while back that you should update your PRL & Profile when you go into a new area (tavel, move, or even long commute to work) regardless of which phone you have. I would think unboxing your phone would qualify as well. It sure couldn't hurt.
---------- Post added at 06:59 AM ---------- Previous post was at 06:53 AM ----------
dmarden said:
It's still a bit early for the issue to be too widely discussed.
Click to expand...
Click to collapse
Good point. Many people would not likely research on the web/forums, instead they'd likely address the issue directly with Sprint.
plmiller0905 said:
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.
Click to expand...
Click to collapse
Ever owned a Samsung phone before?
This is my 3rd one and I swore after the last one Id never buy a Samsung phone again but I got sucked back in. Samsung is notorious for shipping phones with all kinds of bugs that should be considered showstoppers then pushing out fixes months later.
It would not surprise me at all if that was the case here. I am one of the ones having this issue and I am not rooted. Ive lost data several times after hanging up a call. The data never restores and I have to toggle 3G to get it come back.
I dont think this is a kernel issue. I think its something to do with the rest of the OS, either that or the kernel is a different problem thats just acting the same way.
Ok thats what i was hoping to find is nonrooted and rooted people who are having the issue. Now on my moment this issue was huge so i went to htc and maybe thats the case again. Maybe sammy dropped the ball again. Question is what can be done about it.
Sent from a Galaxy far far away...
If you are an Epic Touch user that is experiencing the LOS (Loss of Signal) issue please click on the link below and report in that thread with Sprint.
http://community.sprint.com/baw/message/339779
If you do end up posting on the Sprint site please do post in this thread as well...
Also it was just pointed out that there also is a Samsung support Twitter @ www.twitter.com/samsungsupport
(Please also contact there if you experience LOS)
If you would like to follow this up with a call to tech support, it will help. Try and get transferred to advanced tech support.
This needs to happen from as many people experiencing this as possible!
Don't be lazy!
Thx!
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Double post
Sent from my SPH-D710 using XDA App
graffixnyc said:
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I don't think those other threads were specifically aimed at getting people to do this
I have been told by a reliable source that sprint is aware there is an issue and their engineers are working diligently to find a fix.
Sent from my SPH-D710 using Tapatalk
graffixnyc said:
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Anything is better than "is our phone compatible with random tech blog rumor" threads.
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
I have been told by a reliable source that sprint is aware there is an issue and their engineers are working diligently to find a fix.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I hope your reliable source wasn't a Sprint CSR.
Those of us coming from the Moment were constantly being told that by Sprint regarding the radio lock up issue. They never did fix it. It wasn't until the devs at SDX got 2.2 onto the phone that the issue went away.
I have also found that tweeting complaints to www.twitter.com/samsungsupport during business hours will get a quick response, which results in escalation of real issues.
adma84 said:
I have also found that tweeting complaints to www.twitter.com/samsungsupport during business hours will get a quick response, which results in escalation of real issues.
Click to expand...
Click to collapse
Nice find! Thx!
i just got off the phone with sprint and they told me that samsung pushed an update on friday to fix a delay in receiving text messages which has borked the internal antenna. that would explain why i only started having problems yesterday.... sprint will give you a ticket number and they will fix your phone for free at a store.
call up and get it fixed.
its only going to get worse!
dtr145r said:
i just got off the phone with sprint and they told me that samsung pushed an update on friday to fix a delay in receiving text messages which has borked the internal antenna. that would explain why i only started having problems yesterday.... sprint will give you a ticket number and they will fix your phone for free at a store.
call up and get it fixed.
its only going to get worse!
Click to expand...
Click to collapse
This is false. The issue has been going long since before Friday.
It will be fixed in the first update though.
... and here I was thinking about exchanging my 3D for a GS2... it seems the signal problems are widespread to all phones. :/
Droga said:
... and here I was thinking about exchanging my 3D for a GS2... it seems the signal problems are widespread to all phones. :/
Click to expand...
Click to collapse
Its not a showstopper and it doesnt happen on all devices. So if it happens when you get it use your 30 swap to get a new replacement. It hasnt happened on mine at all. Also there is going to be a fix... So, with all of that said I cannot think of a single thing that should cause anyone to decide not to get this and choose another phone. Thx
DeeXii said:
Its not a showstopper and it doesnt happen on all devices. So if it happens when you get it use your 30 swap to get a new replacement.
Click to expand...
Click to collapse
It is a 14-day swap unless you bought your device pre-launch.
This is a total show stopper, I have 2 of these and they both do it constantly. I cant even surf for more then 10 minutes without it happening to both units. I cant make calls, I cant receive calls, cant go online, cant use streaming music, cant use navigation. total waste at this point. I love the phone physically and its great when on WiFi but that's only 1/4 of the day. I am not taking a chance of getting stuck with a phone that I cant even make calls on. maybe I will try again once everything gets fixed but for now its not worth the trouble.
davedave1234 said:
This is a total show stopper, I have 2 of these and they both do it constantly. I cant even surf for more then 10 minutes without it happening to both units. I cant make calls, I cant receive calls, cant go online, cant use streaming music, cant use navigation. total waste at this point. I love the phone physically and its great when on WiFi but that's only 1/4 of the day. I am not taking a chance of getting stuck with a phone that I cant even make calls on. maybe I will try again once everything gets fixed but for now its not worth the trouble.
Click to expand...
Click to collapse
You have something seriously wrong with yours then. I've had mine since launch and it's done it twice. You should exchange yours.
I rooted my phone and got this for the first time the next day. Hasn't happened before that. Didn't even know what you guys were seeing until it happened. I just got a zero with a line across the middle of it in my top bar and my signal bar and data icon were gone.
Is that what people are getting also that have not rooted their phone? When I say not rooted, not the people who rooted then installed the stock kernal back on. People who never rooted in the first place. That is what I would like to know.
Mine did it once before rooting, once after.
And yes, it happened just like you described. I thought rooting and flashing Zedo v3 fixed it, but it didn't.
clamknuckle said:
Mine did it once before rooting, once after.
And yes, it happened just like you described. I thought rooting and flashing Zedo v3 fixed it, but it didn't.
Click to expand...
Click to collapse
Cool, I hope it is device problem and not just a rooting problem. This way we can get a fix for it from Samsung, hopefully.
I have it on good authority it will be fixed in the first software update from Sprint. No idea when that will be though. It's not a rooting problem.
Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung
But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2
Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app
johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.
Try wiping your SD card
When I use my Nexus 7, sometimes the screen will flash a black screen shortly, I track the logcat using the adb. But didn't find any
error information, it seems like the surfacefinger problem in Android 4.3. Dose anybody find the same problem?
------------------------------------------------------------------------
Thanks XDleader555
Reconnect the cable of LCD can fix this problem!!!!!! the casing of nexus 7 need to be opened, but it's not hard!
If you are not able to fix it, try to use the JWR66N version!
Can't say I've seen this issue. Then again, I don't have any of the issues some are complaining about. I feel so lucky to have gotten one with no problems.
Does the black screen appear when you're doing something specific or is it completely random?
Sent from my Nexus 7 using Tapatalk 4
Yes, completely random. And the black screen flash in a short time. Normally it's difficult to meet.
Try to use clean ROM, but still happen. Hope the problem relate to the software but not Hardware.
isacclin said:
Yes, completely random. And the black screen flash in a short time. Normally it's difficult to meet.
Try to use clean ROM, but still happen. Hope the problem relate to the software but not Hardware.
Click to expand...
Click to collapse
I have the same issue. For a split second the screen will flash to black (off maybe) then back to whatever I'm doing. I had my tablet since the release date, but this issue started maybe a week ago.
Having the same issue myself on Clean Rom and can't figure out a pattern. Has anyone found a fix for this? Do I need to file for a replacement? Thanks!
Sent from my Nexus 7 using xda app-developers app
when I use stock rom, screen randomly darken for just 0.1 sec. after I change to cm10.2. it hasn't happened.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am on the 8-29 cm10.2 nightly. I've tried both with and without faux's kernel same issue. Wiped my device fully last night. No luck.
Sent from my Nexus 7 using Tapatalk 4
This is so frustrating. I just passed my 30 days so I can't turn it back in for an exchange at best buy
Sent from my Nexus 7 using xda app-developers app
myron317 said:
This is so frustrating. I just passed my 30 days so I can't turn it back in for an exchange at best buy
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You should still have a warranty. I think this might be some sort of bug that could be corrected maybe. It seems weird for something like this to occur out of the blue. I may go back to stock to test or try a different Rom that didn't use cm as a base.
Sent from my Nexus 7 using Tapatalk 4
Turn off auto brightness if its on. If it doesn't help you can try desabling HW overlays in Developers options settings
moosefist said:
You should still have a warranty. I think this might be some sort of bug that could be corrected maybe. It seems weird for something like this to occur out of the blue. I may go back to stock to test or try a different Rom that didn't use cm as a base.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes that's true and a good point. I just didnt feel like dealing with sending it in to ASUS and all that rather than just taking it back to best buy (laziness). I was thinking the same thing, that there would be a repair update and missed my easy exchange window. Never been on CM with this device so not sure if it's related. Fingers crossed, just an annoyance really... Thanks!
Sent from my Galaxy Nexus using xda app-developers app
Blackwidowman said:
Turn off auto brightness if its on. If it doesn't help you can try desabling HW overlays in Developers options settings
Click to expand...
Click to collapse
Doesn't seem to help. I'm starting to lean more and more to a hardware issue...
Sent from my Nexus 7 using Tapatalk 4
If the update and the factory reset doesn't work, I strongly recommend sending in the unit for RMA. While there, we can take a look at the hardware, and if needed, actually fix it for you.
My screen flicker (random black screen for a millisecond) went away after I checked the connection. I unplugged the screen, blew a little compressed air into the connection, and popped it back on. No screen flicker in sight after that.
XDleader555 said:
My screen flicker (random black screen for a millisecond) went away after I checked the connection. I unplugged the screen, blew a little compressed air into the connection, and popped it back on. No screen flicker in sight after that.
Click to expand...
Click to collapse
I am also experiencing the same problem. I assume you had to open up the tablet to do that? I might give that a try too.
Was anyone able to reproduce this fix?
XDleader555 said:
My screen flicker (random black screen for a millisecond) went away after I checked the connection. I unplugged the screen, blew a little compressed air into the connection, and popped it back on. No screen flicker in sight after that.
Click to expand...
Click to collapse
Hi, that is a good suggestion! I am
testing now! Wish have a good luck!
did it work?
isacclin said:
Hi, that is a good suggestion! I am
testing now! Wish have a good luck!
Click to expand...
Click to collapse
Isacclin, were you able to fix it?
I had the exact same issue and after reading this thread decided to take the plunge and check the connection. I am typing this on my Nexus now so I don't appear to have broken anything, however I think I have just seen the screen flash black so the problem may still be there.
Given disassembling the thing voids the warranty I would probably recommend not risking it for this issue. I'll let you know if I change my mind.
redders6600 said:
I had the exact same issue and after reading this thread decided to take the plunge and check the connection. I am typing this on my Nexus now so I don't appear to have broken anything, however I think I have just seen the screen flash black so the problem may still be there.
Given disassembling the thing voids the warranty I would probably recommend not risking it for this issue. I'll let you know if I change my mind.
Click to expand...
Click to collapse
I take this all back. After 24 hours of no black flashes I am very happy I took the risk.
The flash I saw when I was writing the above post must have been me being over sensitive to chrome redraws or something!
isacclin said:
Hi, that is a good suggestion! I am
testing now! Wish have a good luck!
Click to expand...
Click to collapse
redders6600 said:
I take this all back. After 24 hours of no black flashes I am very happy I took the risk.
The flash I saw when I was writing the above post must have been me being over sensitive to chrome redraws or something!
Click to expand...
Click to collapse
I looked at the iFixit pictures but they don't point out which cable is for the display. Can you advise which cable I should be cleaning?
thanks!
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
I get this issue when playing a game or typing.
pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.
Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.
Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app
sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.
danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.