Related
I have installed different ICS roms to 3 different i9000s. All of them has touchscreen problems.
Some parts of the touchscreen does not react to your touch sometimes. You have to lock and unlock your phone to regain the full touchscreen. I have tried different kernels etc... No go. It really annoys when you are dialing a number, writing a message etc.
And interestingly no one mentions about it at ICS Rom and ICS kernel threads. Can I be that unlucky to have the problem on 3 different i9000s (They are not from the same batch, each one is bought from another part of the world, at different years).
I would really like a solution or suggestion. Till now i have tired different kernels, different ROMs (mostly ICSSGS (different versions), and Dark Knight (different Versions)). I even tiried diffrent schedulers and governors.
Peace.
That's weird, I have used SlimICS and have never had TS problems... Are you sure you flashed everything right? Please explain the way you've done it
with one phone installed team icssgs as it should coming from the stock , other phones back to stock with odin than cf root and flashing the roms after wipes factory resets. the usual flashing procedure....
Try flashing the team hacksung base first, afterwards flash your desired custom ROM. That should do it.
could you try to explain the diff. between flasiing without cm9 or or with cm9. whar would
be the difference at the end?
I don't exactly know why this is needed, but I would assume that TeamHacksung or CM9 have some frameworks included which are perhaps missing in custom ROMs. I'm just guessing, don't really know =/
Have you tried it? For a CM9 based ROM, flash CM9 first and for a TH based ROM, TH first
Hello,
Have you checked if the Problem still remains when you are on Stock ROM?
CU
tenos
Gesendet von meinem GT-I9000 mit Tapatalk 2
no i havent but it was working just before i flashed icd.
also i have 2 more phones with the same problem. So it is not my phone malfunctioning.
In ICS-333 from you can turn on show touches in developer options in settings menu you could see if its registering your touch immediately or at all. The browser is the only place I've experienced touch lag though.
Sent from my GT-I9000M using XDA
Hey I got ur prob and I know what causes it, it not a bug, its dirt or water on your screen that causes the prob if u keep the screen spotlessly clean u don't get it
Sent from my GT-I9000 using XDA
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
belmethos said:
I have activated show touch before, it does not register your touch at all. also I have tried cleaning it no go, since this is happening with 3 different phone, i doubt it is dirt etc.
Click to expand...
Click to collapse
I know what causing it. It a bug where dirt or water or something gets on the screen and because the drivers on ics is so sensitive it picks it up, try changing sensitivatiy or keep that screen very clean
Sent from my GT-I9000 using XDA
i have the same problem. its very frustating. never happened in gingerbread. only on ICS.the bug happened occasionally, the funny thing is it only affect the first row area of the screen. (lower left altheway up to upper left corner), it doesnt register tapping on the screen but it still register swiping from outside of the area..., like ussual i need to lock and unlock again to make the touch working again.
I have installed GB back and problem is gone? I am out of ideas anyone?
Flashed back ics bug returns, flashing jb same thing.
Exactly the same problem here
With Stock GB everything works fine, with custom roms the right side of the touch screen doesn't react. You have to lock and unlock your phone to regain the full touchscreen.
This is interesting this is far more than i anticipated anyone with a clue?
same problem here. my screen was working when i bought it (obviously). it was froyo then. the touchscreen problem appears when i upgraded to custom ICS rom. the middle part of my touchscreen does not respond to touch. none. nada. although the rest of the screen seems to be responding to touch so far. turning the screen off the on again temporarily fixes the problem, but not always. i put back a gb rom, the problem was gone. i was thinking maybe there's a different digitizer driver samsung put on their stock gb roms. it's really annoying.
any more ideas? should i replace my touchscreen digitizer?
Yes it's really annoying :crying:
What is different between stock gb/froyo and ics/jb custom roms that have such an effect on the touchscreen?
I will try the app SGS Touchscreen Booster to decrease the screen sensivity, maybe it helps
never heard of this problem in all the time i was ics.maybe time for some jellybean
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0*# code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
mregmi121 said:
Hi everyone,
I bought a Samsung galaxy s last week from an eBay auction. The phone was described as touch screen lag. I was thinking that flashing a new firmware will solve the problem. I got really cheap though
The touch screen stops suddenly in every 5/6 minutes and I have to lock the screen using power key and unlock again to make it working.
when I got the phone:
Non Samsung battery and chargers were used, I changed and using original ones.
Stock XXJVS firmware in it.
First I flashed stock 2.2.1 froyo and test the screen using *#0#* code. it got pass. But when I start using it, the problem was still there.
Then I flashed stock GB, same story, now slim ics, same thing.
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
This happens to me sometimes very rarely though, it will be weird and hard to touch but speaking to someone with the same phone they said they had this problem to all I do to resolve the problem is lock and unlock the screen, I thought this was normal?
Sent from my GT-I9000 running remICS-UX using XDA premium
It shouldn't be normal. I am using another galaxy s for almost two years. But never had this problem in such extent, little bit lag on touchscreen when on froyo. But never after. Now with slim ics Temple run is more smooth then iphone 4.
Sent from my Galaxy S using xda premium
Kurre said:
Sounds like a hardware problem to me..but it's really hard to say if it is. But it would definitely seem like it since it isn't ROM related. Maybe a water damage or faulty digitizer?
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for reply. When I got it first time, it was really annoying, the problem was so frequent that it was almost unusable. Now in new rom, after unlocking the screen it works little longer then before. Works like a charm when it works. So not sure this is hardware problem.
Sent from my Galaxy S using xda premium
I don't think this is a hardware or problem either, I broke the screen and replaced it and I still have the same thing when though it is very rare, so if it was the screen it should of gone after I installed the new one, btw I installed a whole new pre built front so the bevil and LCD, and my phone has never hib water damaged? Maybe its something to do with the bootloader? As that doesn't change through ROM flashes
Sent from my GT-I9000 running remICS-UX using XDA premium
mregmi121 said:
Please someone help me, there is nothing I can do with it now.
I search few threads related to screen problem but couldn't find one with similar problem. So asking here.
Click to expand...
Click to collapse
try using a LCD modder LCD density modder https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&feature=search_result
@xsenman;
I did that couple of times going through Advance slim setting. That didn't change anything. Now I'll try this as well.
I change touchscreen into chainfire sensitive option in semaphore app. Still lagging.
Tried over clocking to 1200 but it freezes and automatically reboots into recovery mode. I can use only after changing to default
Sent from my GT-I9000 using xda premium
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
mregmi121 said:
Guys its really annoying now. Its behaving strangely. I played with it few hours and found out that the screen near the home button freezes first. I cant press the dock but still pull the notification bar? then stops working whole screen. I checked the show touches in developers options setting. Sometimes it works randomly actually without touching it , I just place my finger near the screen but didn't touch and on few occasion it works opposite direction, like I scrolled down but it gone up:crying:
Is this the sensor issue? Is there any way to fix? Any idea please?
Click to expand...
Click to collapse
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
xsenman said:
try this tool to verify where the problem is , if its hardware, you have no choice but to take it to a technician
https://play.google.com/store/apps/details?id=com.gombosdev.displaytester&feature=search_result
and this
https://play.google.com/store/apps/details?id=com.vital.tst.n7000&feature=search_result
https://play.google.com/store/apps/details?id=zausan.zdevicetest&feature=search_result
Click to expand...
Click to collapse
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Kurre said:
Screen+digitizer panel can be changed by yourself. For it, you just need couple of tools and little nerves
Instructions can be found from YouTube, this forum and many other places..
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
I tried all of those apps, nothing wrong. I think I should change the screen and digitizer, I might need to go to the repair center because my hands shake (my usual problem) and hard to fix tiny things. I want to do few experiments before taking it to repair. I already put it in the freezer for two hours it was acting like crazy after.
Suggest me more...
Sent from my GT-I9000 using xda premium
Me too!
and i thought i'm the only one experiencing this kind of problem. it is exactly what i'm having on my sgs. seems to be temporarily fixed by turning the screen off and then on again, but after a while, the screen doesn't respond on the same spot as you're having.
i've managed a low level debug on screen touch response using adb logcat, and my touch doesn't really register any on adb logcat console.
they might be correct on the hardware problem, but when i'm on any gingerbread rom (2.3.6), the problem is gone.
guys, any idea what kind of drivers they're using on gingerbread for our touchscreen?
I have this too on ics, left half of screen stops responding, lock on/off sorts it....until the next time! Bugs the hell out of me!
Me too! on ICS
btw, i'm already on ics team nyx
change
flash CF KERNEL and put ICS CM9
middle screen not responding
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
psycotrompus said:
- when in stock gb firmware (official from samsung), the touchscreen problem is gone.
- but i want the features of an ics rom, so i flashed one (first was slim ics); the problem appeared first; first guess was the custom rom was still in its early stages.
- flashed back to gb, no touchscreen problem.
- flashed new ics rom from cm9 (nightlies), problem appears again (ugh!).
- flashed backed to updated slim ics since this was the fastest and easiest to install, touchscreen problem still persist.
- found a temporary fix by turning the screen off then on again.
did a adb logcat full trace log of touchscreen input: what i noticed was the whole vertical middle part of the screen is not responding to touch; dragging touch from one side to middle is working just fine, but not starting from the mid vertical part.
the problem may sometimes go away after a while, and sometimes persist even after the temp fix. it's very intermittent indeed.
help please.
Click to expand...
Click to collapse
So your sgs touchscreen working fine on stock gb rom! It might not be a hardware problem then. We have similar problem, only difference is I have problem on GB too. I've even tried stock froyo, same story
Sent from my Nexus S using xda premium
same problem here, left part of the screen would be unresponsive at times
can fix by locking the phone through power button and unlocking it, thats why i think its a software problem.
I dont remember having this problem in GB also.
maybe something is messed up during flash?
I have the same problem with ics and jb roms from the onecosmic ics times and i had a topic http://forum.xda-developers.com/showthread.php?t=1648287
I have written here but no one seems to now what it is, i have been using ics from onecosmics first release and had the problem from that moment on, different kernels, roms etc it is still here i have flashed gb again and problem is gone, flash again with ics the middle part still acts sometimes. ?...
We should request from kernel developers and rom developers to look into it. I have tried almost everything no luck so far
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Andddddddd it stopped working again. Super legit.
Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app
My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
you better do it before its too late. id rma it.
cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?
cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.
Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.
Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.
Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app
Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?
cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.
Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.
Hi all, lurker here.
I've been having an issue with my OP3T that hasn't really phased me until now. From time to time my phone would lock up and crash (phone shuts down unexpectedly). I would have to manually reboot the phone by holding the power down button.
I am running on OOS Beta 10, rooted with Magisk 13, EX Kernel and whatnot. This has happened prior to being on beta channel and root as well. I've read somewhere that this is a hardware issue that arises from SD821 clocking up to max Freq which causes the crash but I think even with the custom kernel and underclocking I am still experiencing lock ups.
If there is a log I can provide for you guys I can post it, just don't know which one.
Thanks.
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch ?
pitrus- said:
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch
Click to expand...
Click to collapse
I don't have Substratum installed
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
shivagajavelli said:
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
Click to expand...
Click to collapse
Damnn, i've got the same problem.. blank screen with white light notif then off, when 3T not get random shutdown they give me random restart every 2-3mins, aarrgggghhh really annoying!
same problem with my devices
And then whats the solution for these problem? Arrggghhh
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
Anyway which kernel?
I have the same with stock and beta OOS, stock and bluspark kernel. Never rooted. I though that maybe i just press power button in my pocket but then it happend on the desk as well.
Similar issue, sometimes black screen with unresponsive buttons (they do vibrate), sometimes I can unlock it via fingerprint to the home screen but touch is unresponsive, only appswitch via recents button works but can't exit the app with home button, sometimes it just reboots.
Never had these issues from dirty flashing from open betas but now when I started clean these things began lol. Seems more laggy too.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
I just clean flashed all stock, pure without UBL, root but still same. Then tried to UBL, MAGISK + Franco Kernel, and still the same condition...
Ahhh i hate this phone! Really sucks
Hmm yeah I've had another crash but this just happened during boot.
Still have no idea what the possible cause is. Not aure why it's just us few that are experiencing this.
Maybe faulty hardware? Who knows
I used to have this problem when running the open betas for the 3t, I moved over to RR and there hasn't been any problems especially after the latest update
Edit. Also when turning on the phone the bootanimation (the two dots spinning around the thingy) it would freeze constantly, also fixed after moving to RR
My phone was crashed few times when using cameraMX application. I do not know reason, maybe last update fault? I have simple question, why we have beta version? Where is stable
Yeh I've had it freeze on multiple accounts while booting up. It would crash while the two dots are spinning and would need a hard reset.
Many times it would crash when entering my PIN for smart lock or lock screen as well..
Issue seems to have popped up again., after flashing OOS OB 14.
Most frequent symptom is after entering pin or unlocking device, at random times it would lock up Android and crash (shut down, not reboot). So I have to boot my device again by holding down power button.