Database Develop

Non ROM Specific Camera Issue

I've been scouring the forums in hopes of a fix for my problem (the G1 Q&A and the Android Development forums). In my searches I have found 10-20 people who have had this similar problem, specifically, a force close whenever I (we) attempt to use the camera.
I'm %90 positive this is a software issue. I have had this phone (my 3rd one) for a few months now, and never have I had any issues with the camera, i actually use the video cam fairly often. Anyways...I decided a while back to root and flash Cyanogen's latest ROM, with the latest radio (posted a few days ago) and the Death SPL. Once i completed this, I was met with an instant force close when attempting to use my camera.
I have actually wiped and installed Cyanogen's ROM 2x, (the 2 latest versions), I have also installed KingKlick latest ROM, neither of these, coupled with countless different configurations has solved the problem. I have attached a small snippet of the last log I pulled. Any help or ideas would be greatly appreciated.

I also forgot to mention (and this might be completely wrong), I did restore the 1.5 image from the SPL, rebooted the phone, and the camera still didn't work, it didn't force close, just hung like it was trying to boot. I have also used the latest Super D ROM and I'm experiencing the same issue.

With my minimal knowledge, only one thing in the log jumped out at me, or, should I say I only saw one thing that I understood.
"X: /dev/msm_camera/control0 open failed: No such file or directory!"
Please help, this is a major deal for a number of people, every time it's posted, people just seem to ignore it.

Download Camera Magik from the market. If the problem is software related, then using a different camera app could be the solution. I like camera magik because is takes better pictures at low lights then the stock and the ability to zoom, but you can try any other app. Another suggestion is trying a sense based rom and using HTC camera. GL

I guess I should have said Kernel based as opposed to software based. I tried Camera Magic as well as one other new type of photo software, Camera Magic FC's, the other one opens, but, the camera never turns on.

Do you have any other apps that use camera(i.e barcode scanner, shopsavy)? You may have to uninstall and re-install. Did you wipe in-between roms? Try clearing your rotation settings from recovery, that may sort it out (I know it's a long shot). Other then that, email whoever's rom you're using directly with that log, they may be able to help you a lot faster then any of us regular folks can
Good luck

try a complete super duper wipe.
start from rc29, nonrooted. see if the camera works. if it does, start the root-rom process and check at certain intervals. if it doesnt work when your not rooted and on the stock original firmware, then its gotta be the phone. did it ever work before? i know you said this is your 3rd phone. has it ever worked on this particular phone?

First off, the camera/video has worked on all 3 of my phones, the 1st one had to be replaced because the keyboard went out, and, the 2nd one just kept randomly rebooting, the 3rd hasn't had any problems what so ever until my first root, which was Stock 2 Cyanogen.
So, I went back to RC29 unrooted and experienced a different problem. The camera didn't FC, but, it hung indefinitely at a black screen (kind of a dark grey). Unfortunately, for some reason the system option to force update to cupcake wasn't available, so, after 5hrs of waiting, I went back to root SuperD.

[Q][i9000] Custom Firmware?

I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.

Pinpong blockbuster rom - ticks all your boxes. Get faster fix from market.
Your gps will never be 100% satisfactory in the city, in fact it will probably always be poor - no matter what custom rom you use.

Halkus said:
I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.
Click to expand...
Click to collapse
Have you think about CM7? Great Rom, works well on my phone, and add many new things.

Hi Mate, I tried many custom roms and finally settled for
(ROM)GingerCriskeloV77-9LS-CamHack- SIP + NoIncRing I9000/T/M JVP 2.3.4
Cheers

Well, I managed to get it on. Booting up is weird though, it looks for a long time as if the screen is broken, but eventually ti comes on to the Blockbuster lock screen and then everything is fine. It does seem faster - but I'll only really know when I get to one of those situations where I feel the phone is frustratingly slow.
Thanks very much Woolf!
Time allowing I'll give the other roms a shot, although this Blockbuster one does seem to be good enough for me.

Sadly my phone now reboots constantly. it seems to do it when the screen locks

Halkus said:
Sadly my phone now reboots constantly. it seems to do it when the screen locks
Click to expand...
Click to collapse
Check you got the installation right for that rom, maybe you had to flash a jvp stock first or some similar omission?
Sent from my GT-I9000 using XDA Premium App

Sorry to hear you're having issues. Try flashing to a totally stock JVQ first (with repartition) once you've backed up, then if you don't like that, try a custom ROM. I don't think many JVQ custom ROMs are worth trying if you want a taste of custom ROMs. Better to try CM7 or MIUI for something fast and different.
As a side note, the best tip I've seen for fixing the dreadful GPS we have with the i9000 is to buy a Nexus S or just ANY other phone! Yes, some radios appear better than others, but nobody can prove anything and it's almost all subjective feedback. A drop in the ocean of improvement needed for satisfactory function. If you must use it, a bluetooth GPS receiver and 3rd party navigation app seem the best way to deal with it.

I've now stepped away from Blockbuster. Even doing the a perfect install it crashed often and repeatedly. I did try upgrading to the very latest and that crashed several times in the past hour. Part of the problem was the rom starts with a lockscreen that has a messaging unlock on it, but it isn't set to an app that comes with the rom, so it reboots every time. Sadly that wasn't the only problem, as I was still getting loads of reboots.
So that's out of the way.
I'm now a lot more comfortable using Odin so I'll be able to try other options. I'll try the other two suggested in this thread first of all.
Next to test is CM7.
Thanks for the help folks!
CM7 aborted. Instructions are incorrect, the file they say to download doesn't actually match the instructions so that's out. Plus it clearly states it's not suitable for day to day use... so I don't thnk the time in working out how to fix it is justified since it looks like it wouldn't be useful.
I'm going back to the original question in the thread, to say that I'm looking for something stable. I now think that a custom rom is not the way to go. However some modifications may well be.
Can anyone suggest some kind of lagfix/speedup that isn't a complete overhaul like CM7, Blockbuster etc, that is very stable and that'll make my phone faster?
Edit : Part of what I was doing to install Blockbuster was install Speedmod kernel. So I've gone and put that on, and used the clockwork mod to root it, and also convert to ext4. I think things are looking pretty fast so far. I'm not sure if there's a lagfix for this, but I'm quite comfortable just now footering around - unlike the complete rom I don't feel out of my depth. So I think I'll be ok for now.

[Q] Touchscreen Problem with ICS Roms

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

[Q] Some question in regard to flashed P1000 [Alroger CM10.1 Android 4.2.2]

Phone: Galaxy Tab P1000 16G (apparently the Euro Unbranded version)
ROM: Alroger CM10.1 Android 4.2.2 20130913 Unofficial-P1
Kernel: 3.0.94 HumberOS V1.45-00920-g9fcdd44
i been using this P1000 for about a year now
a friend gave it to me coz my old phone died
anyway, last weekend i started learning about rooting and flashing ROMs
thank god its been successful so far, lol
tried a few different 10.1 4.2.2 rom, seems pretty stable except few minor issue
i have done some research myself, but could no find a clear answer (or any answer for that matter)
since i am new to this whole rooting and flashing business
i think it's best if i could ask you guys who is more experienced for some advise
if anyone could give me some tips on the issues
will be much appreciated ^^
1. i have notice with all the 10.1 rom i flashed, the GPS never worked
could no get more then 3 satellites pickup
since i use the P1000 as my nav device while driving, i spand a whole night learning about this issue
then i found out that the gps.conf file in all of the roms, only had 3 line in it
after copy another .conf file from my roommate's S4, it seems to be working again
is this a common issue?
cos atm, on road i can only pick up about 6~8 satellites
but cuts on and off every now and then...
2. currenly on the Alroger CM10.1 Android 4.2.2, the camera screen flashes/jumps when lighting/focus changes
this happens for both front and back camera
i did not test this on other rom at the time, so no sure if this is a common issue with all 10.1
when taking photo its ok, as long as i don't move too much, its dosen't happen
but with video recording, it happens during recording as well, which is very annoying
happens when i am recording with DVR app as well
dose anyone have the same problem?
or is there a way to fix this?
i've been digging for a bit, but didn't find anything regards to this issue
3. the Screen-off animation (electron beam animation when the screen is turned off) dose not work
i seen it on other phone, looks pretty cool
so i wish i could activate this option
is this another one of those so called "wrong Kernel version" issue?
or is that because they disabled it when making the rom to reduce system usage?
could this be reactivated?
4. i know this might be a stupid question to ask... but i am gonna shoot it anyway
i've notice after i flash the 10.1 rom, my RAM reading when up from the factory 444, to now 487MB
some other 10.1 reads in between that figure, but the Alroger CM10.1 seems to give the highest number
even tho it's still far from the factory promised 512MB
dose this mean the total RAM availability can be adjusted?
or is that just a fake reading due to different Kernel version or such?
i mean the phone is now running much smooth then the factory 2.3.6
no sure if that is due to the system trip down from the rom (most likely because of this?)
or the actual 43MB RAM increase....
for the first 3 issues
i have tried wipe and re-flash as some forum have suggested
yet still didn't change anything
any suggestion, info, tips will be most appreciated
~Icarus~
~The P1000 Newby~

bump~?

Its mean custom os lets use device see more ram
Sent from my GT-P1000 using Tapatalk

robindebruin said:
Its mean custom os lets use device see more ram
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
so it's just a fake reading?

No i lets the os use more ram
Sent from my GT-I8190 using Tapatalk

[Q] Need to wait a while for the screen to turn on

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