Related
Hey guys, i have had only one gripe with my dream since i got it, the camera sucks. Way back when Dude was making 1.5 and .6 I installed one of his zips and amazingly the camera worked like a REAL one that you get in a store. no lag in the viewfinder at all! I asked him what he did, and he said nothing. so i tried flashing again and the camera reverted. forward circa 2010... i flashed cyanogen 4.2.13 from scratch. wiped, formatted, installed htc base and then flashed the cyan. yesterday i installed 4.2.14.1 without a wipe, BUT First I reformatted the sdcard(three partitions) for other reasons, then installed. when the g1 booted up it was very quick but Android Market disappeared. so i checked to see if anything else was missing and i opened the camera and VIOLA. The camera works flawlessly again! no lag or anything. So my point in this is to figure out why, only after a format of my sdcard, do i get excellent camera performance. Any ideas on how we can implement something to keep this around!
I've had a weird problem with my phone for the past month where the camera preview shows the colors shifted. For example, my off-white desk is a mustard color transitioning to green, then black, then dark blue instead of what it actually is. If I take a picture, the wrong colors are saved. Sometimes it works correctly but that's pretty rare.
Any ideas? I was using the latest Cyanogen 1.6 rom, then I decided to try moving to CaNNoN202-CompleteEclair-v20 with the same results after wiping everything.
This seems to have started around the time I was messing with the extra RAM patch and JIT hack but wouldn't installing the 2.0 ROM overwrite those? My free memory is 98,196k. The only thing I can think of is maybe the radio image got corrupted? Any ideas would be appreciated!
jcostantino said:
I've had a weird problem with my phone for the past month where the camera preview shows the colors shifted. For example, my off-white desk is a mustard color transitioning to green, then black, then dark blue instead of what it actually is. If I take a picture, the wrong colors are saved. Sometimes it works correctly but that's pretty rare.
Any ideas? I was using the latest Cyanogen 1.6 rom, then I decided to try moving to CaNNoN202-CompleteEclair-v20 with the same results after wiping everything.
This seems to have started around the time I was messing with the extra RAM patch and JIT hack but wouldn't installing the 2.0 ROM overwrite those? My free memory is 98,196k. The only thing I can think of is maybe the radio image got corrupted? Any ideas would be appreciated!
Click to expand...
Click to collapse
Did you have this problem with the Cyanogen rom?
Did you try clearing the data for the camera (Settings>Manage Applications>Camera>Clear data)
Binary100100 said:
Did you have this problem with the Cyanogen rom?
Did you try clearing the data for the camera (Settings>Manage Applications>Camera>Clear data)
Click to expand...
Click to collapse
The Cyanogen rom was working, then something happened around the time I did the RAM and JIT hacks and the camera screwed up. I reversed my changes but it never fixed the camera. Wiping and updating to the 2.0 ROM didn't fix anything either.
jcostantino said:
The Cyanogen rom was working, then something happened around the time I did the RAM and JIT hacks and the camera screwed up. I reversed my changes but it never fixed the camera. Wiping and updating to the 2.0 ROM didn't fix anything either.
Click to expand...
Click to collapse
Well I'm not familiar with the Eclair rom that you used. I would suggest going back to CM and see if that clears it up.
Sounds like hardware issue to me. :/ Lets hope its not.
Agreed - I doubt I have warranty left. The strange thing is that it will work every so often but 95% of the time it won't.
I attached an example picture I just took. Some of it is right but mostly everything is wacky colors.
I vaguely remember this being a problem on the original cooked roms but I don't think it was quite like this.
I reflashed the radio and that didn't do anything - I suppose the next logical step would be to use the drea100.nbf and go back to total bone stock with nothing.
jcostantino said:
Agreed - I doubt I have warranty left. The strange thing is that it will work every so often but 95% of the time it won't.
I attached an example picture I just took. Some of it is right but mostly everything is wacky colors.
I vaguely remember this being a problem on the original cooked roms but I don't think it was quite like this.
I reflashed the radio and that didn't do anything - I suppose the next logical step would be to use the drea100.nbf and go back to total bone stock with nothing.
Click to expand...
Click to collapse
I had exact same thing. I had warranty left so I sent it in. Sorry.
jcostantino said:
Agreed - I doubt I have warranty left. The strange thing is that it will work every so often but 95% of the time it won't.
I attached an example picture I just took. Some of it is right but mostly everything is wacky colors.
I vaguely remember this being a problem on the original cooked roms but I don't think it was quite like this.
I reflashed the radio and that didn't do anything - I suppose the next logical step would be to use the drea100.nbf and go back to total bone stock with nothing.
Click to expand...
Click to collapse
I don't know why, but I kinda like that. It's a nice effect. It reminds me of the Predator movies.
Binary100100 said:
I don't know why, but I kinda like that. It's a nice effect. It reminds me of the Predator movies.
Click to expand...
Click to collapse
Straight trade, my phone for yours then
Binary100100 said:
I don't know why, but I kinda like that. It's a nice effect. It reminds me of the Predator movies.
Click to expand...
Click to collapse
I agree. It looks really cool. Take a picture, submit it into a contest, and when enough money for a new phone.
Kidding, but I'm really sorry you're having this problem. As much as I HATE that ****ty camera HTC gave us, I find myself using it constantly. I would still lean towards hardware, though. =[
jcostantino said:
Straight trade, my phone for yours then
Click to expand...
Click to collapse
LOL! Ummm... no?
I preordered my G1 on the launch in 2008 and I still have warranty until December 2010? WTF?
Dear all,
I noticed my phone has an issue and I think this may not be rom / kernel related, so I would like to ask here.
My phone is running fine every time after booting up, however after running for a random period of times (say 2 - 7 days), it cannot play any media files. I can't play youtube (it said the video cannot be played), can't listen to mp3 (music player reported unsupported codec), ringtone disappeared (phone don't ring if i get call) and other apps failed in similar way. A reboot can solve the issue.
It is a bit annoying (especially when you when to play something and you suddenly identified that you need to wait for 5 min for a reboot), does any one experienced similar issue?
To clarify , I am running darky rom with darky kernel 1.0, however I had this issue for a few months, I was using super optimized kernel and had the same issue as well.
Same here. i'm running Darky's 9.4 but I don't know if it is related to this rom.
I don't remember that I had this problem before.
Sent from my GT-P1000 using XDA App
Another one running Darky rom with a problem .
jje
I have this problem.
(dark kernel 1.4 and darky rom 9.5)
I get this occasionally and I'm on stock 2.2.1. It's a massive pain in the arse. I thought maybe it was something to do with my external micro sd card but I formatted it and waited hours to copy all my music to it again and I'm still having problems.
Sent from my GT-I9000 using XDA App
So quite a few of people having this problem. Did anyone of us find out the root cause? And what's the reason that others do not suffer from this? This happened on Darky, Super Optimized Kernel, Speedmod, Stock Rom...
Some experts can help?
Also know this problem. Had it on stock and some custom roms too. Tried nearly every kernel ever available for our phone but didnt help. so it really maybe some strange Hardware issue...just speculating but when did you guys get your galaxy? cause mine was one of the `first generation` got it immediately when it was available here in germany in june/july 2010...perhaps this got fixed by Samsung later on
Sent from my GT-I9000 using XDA Premium App
An old Nokia trick may work . Delete your MP3s .
Load only a few MP3s to phone and see if it works .
jje
JJEgan said:
An old Nokia trick may work . Delete your MP3s .
Load only a few MP3s to phone and see if it works .
jje
Click to expand...
Click to collapse
And then??? next time when my cars engine does not work i will follow your tip and try to remove all my seats and move back my drivers seat only to see if it works again...
Sorry but i dont get your point...i also have completely formatted internal and external sd several times for different reasons and the Problem still occurs. In addition this is not only for mp3s but also for recorded vids etc no matter were i store them
Sent from my GT-I9000 using XDA Premium App
hofinho said:
And then??? next time when my cars engine does not work i will follow your tip and try to remove all my seats and move back my drivers seat only to see if it works again...
Sorry but i dont get your point...i also have completely formatted internal and external sd several times for different reasons and the Problem still occurs. In addition this is not only for mp3s but also for recorded vids etc no matter were i store them
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Ignore it then your choice try Samsung Service ..
jje
I've seen another thread were someone said it was called by the twitter client. They have updated the official twitter client recently, and I've not had the problem occur since. Although, it may be too soon to tell, it used to happen to me very regularly.
And just to followup, the problem hasn't gone away with the new version of twitter.
So, I'm not sure of what is the cause (or solution) to the issue.
echidna2001 said:
And just to followup, the problem hasn't gone away with the new version of twitter.
So, I'm not sure of what is the cause (or solution) to the issue.
Click to expand...
Click to collapse
Hi, where do you find the post also mentioned the same problem?
I am having the problem regularly too, after updating the Twitter client the same problem still happen yesterday, the phone run for around 2 days after last reboot.
HKcow said:
Hi, where do you find the post also mentioned the same problem?
I am having the problem regularly too, after updating the Twitter client the same problem still happen yesterday, the phone run for around 2 days after last reboot.
Click to expand...
Click to collapse
Nope, i though you are talking the twitter update around 1 week ago. I just found that twitter have a new update today and never tried it if it fixed the problem. The change description do mention something similar, fixed a bug to skip music player while updating.. not sure if this is really the case.... need to test now...
good topic
I'm going to get rid of the twitter app then to see if it helps as updates don't seem to have done anything and I reformatted the sd card again and stuck everything back on there today and not only did it happen again, it's getting worse! Not only could I not play any music a minute ago, a load of my apps had vanished too! I assume ones that installed to SD by default rather than the phone storage.
If this sorts it out I'll be very happy. Twitter's crap anyway.
I've been having the same problem for a while now. I have just uninstalled Twitter and will see if that helps.
Basically all media stops working. Can't even record anything with the camcorder app. Nothing plays back. No youtube, no camcorder videos, no nothing. BUT arcmedia will open some videos sometime. HMMM weird, because other video player apps don't seem to be able to play them.
I'll give an update later today if it works. Videos normally stop working after only a few hours on my phone.
Bell SGS Vibrant I9000M
Alex
Do you guys have 8GB or 16GB models?
I've only come across this once and it was on a stock 16GB, one of the early ones, started about a week ago...upgraded to JVB seems to have solved it for now, time will tell.
16gb model, I've had 3 updates, and none have fixed the problem.
LAHAL Droid said:
16gb model, I've had 3 updates, and none have fixed the problem.
Click to expand...
Click to collapse
Wonder if it's just the 16GB?
Just wanted to see if anyone is having trouble with this. I have all my pics stored on an SD card and every once in a while, when i try to open the stock gallery app, it takes a long time (sometimes up to 15-20s) to come back.
i originally thought it was slow sd card. I upgraded sd card to class 10 and still see the issues. FYI...AnTuTu benchmark has SD Card write/read at 14.8MB/s and 17.5MB/s respectively.
Has anyone seen this before?
GingerVolted and BliztKrieged
Haven't had that issue yet. Did you try to clear the program cache?
Sent from my VS910 4G using Tapatalk
I have this happen a lot too. I don't think it takes as long as 15-20 seconds but it takes a whlie to load up the first time. Then when I got back to the gallery it's pretty instant. I'm guessing cuz it's already loaded up. I think O/Cing it helps with the load time.
it did help after OC'ing. and i still get it even after i have previously loaded the gallery.
yes, i've cleared out the cache too.
scyther2333 said:
it did help after OC'ing. and i still get it even after i have previously loaded the gallery.
yes, i've cleared out the cache too.
Click to expand...
Click to collapse
That's weird. Do you have Rom Toolbox? Maybe try applying the SD card boost and see if that helps. It shouldn't be taking you that long every time. Maybe the first time it loads but after when you open it up again in a couple minutes it should be much faster.
just freeze the gallery and download quickpic, waaaay better
installed spc_hicks's tweak and seems to be working better now.
http://forum.xda-developers.com/showthread.php?t=1420828
i'll try other apps
Mine would take upwards of a minute sometimes to get all my galleries loaded. Manually (through settings) would unmount and remount and that seemed to help. Never figured out why, silly phone...
Sent from my Galaxy Nexus using Tapatalk
well...i think it might have been words with friends again. seems to happen whenever i play that game.
....effin a cotton, effin A
Guys when this happens, jus go bak n press gallery again! It will load quickly :-D
Sent from my GT-S5830 using Tapatalk
I agree with revo... QuickPic is soooo much better and faster. Free from the market.
Sent from my VS910 4G using XDA App
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.