hello every one
proximity sensor of my s3 works continiously on secret menu it shows PROXIMITY:1 ADC:0(0.0.0)
i did every think
flash other stock roms upgrade and downgrade
cleane sensor
recalibrate with many methodes mentioned it stops for few minutes but retunes to work
is it a hard or soft problem
what is the solution a ccording to you please help
any solution ???,,
i am still waiting for your help
Rom or kernel issue.
Stick with the roms that work for you.
Darke5tShad0w said:
Rom or kernel issue.
Stick with the roms that work for you.
Click to expand...
Click to collapse
but because of somme bugs on somme roms i hated my s3
stock roms always are full working
i installed my stock roms on other I9300 phones it didn't cause any problem
i think that the problem is similar to 'not registred on network' issue
:good: thank you for your responce i thinked that no one will anwer me
thank you again
problem remains
i have edited the post because i observed that even with custom rom it works some hours and the problem returns
Hello everybody
I think that the problem is sloved but i am in test period
I cleaned hardly the sensor till i scared that it is broken definitivelly now it is working
And i test it
I will update if any news .thanks
Related
hey,recently i`ve some problem with my touch screen,it sometimes doesn`t respone till i switch screen off then on,specially in Ics roms ,in gb it happends also but not all day long|! anyone have had same issue ? is there any solution to fix it ?
moritd said:
hey,recently i`ve some problem with my touch screen,it sometimes doesn`t respone till i switch screen off then on,specially in Ics roms ,in gb it happends also but not all day long|! anyone have had same issue ? is there any solution to fix it ?
Click to expand...
Click to collapse
Never had such a problem. I think it may be hardware problem
btw i saw in fera`s post he had mentioned same problem for his ics rom but i have this problem even in stock rom,but its much less than any other rom
hope its a software problem can be fixed by something!!
\
btw i saw in fera`s post he had mentioned same problem for his ics rom but i have this problem even in stock rom,but its much less than any other rom
hope its a software problem can be fixed by something!!
\
Hi,
i have tried changing from a couple of roms and i am just unable to connect to the front camera. I do not know what is wrong! can someone please hlp me?
try going back to stock rom. camera still not working? than it is probably a hardware issue .take it to a service center
Try flashing the ROM again after wiping caches. Faced this problem today for the first time with Omega. If that doesnt help try to flash some other ROM.
E: Sorry, read wrong the OP
xG-Tank said:
Hi,
i have tried changing from a couple of roms and i am just unable to connect to the front camera. I do not know what is wrong! can someone please hlp me?
Click to expand...
Click to collapse
Check camera firmware digits this in the dialer:
*#34971539#
skassa22 said:
Check camera firmware digits this in the dialer:
*#34971539#
Click to expand...
Click to collapse
it says invalid code... can someone please help me change the camera firmware?
xG-Tank said:
it says invalid code... can someone please help me change the camera firmware?
Click to expand...
Click to collapse
See your identical same post
Is this a common issue
From the experiences on installing custom roms (AOSP based) such as CM 10.1(snapshot release) and AOKP(milestone). Camera crashing was the common and irritating bug ever had. In CM 10.1 it was slightly less, but in AOKP Camera freezes like 1 time interval (1st time not responding and 2nd time it's working).
I've read in most of the AOSP based roms for S3 (I9300), this is a common since the firmware itself is locked. Is there any glitch free AOSP based roms with good rom controls and customizable options available for S3? I'm really looking forward for Paraniod Android and RootBox, fingers crossed
Also does flashing kernal will do any good? (see: http://forum.xda-developers.com/showpost.php?p=42766353&postcount=4)
I'm sorry if this post intended to against the thread topic.
** FIXED THIS WITH THE ROOTBOX ROM, BUT PROBLEM CAUSE IS STILL CONFUSING **
hey all . i have galaxy S2 gt-i9100g and i posted here because i found no Q&A for that .
i have 9100g was on stock 4.1.2 , i flashed a couple roms (CM11 , PA , CRDroid,.......) and now i settled on PA beta6
i have this strange issue when my phone won't charge or recognize a connected USB port , it happens rarely and when it does a reboot is enough to fix it .
Is this software realted (kernel or so ...) or hard ware related ??
Oh and how can i revert back to stock official i found no 4file flash with bootloader and pit so i got afraid i might end up with a brick or a bootloop
please help me guys
Please tell does it have the same issue on other roms? Or are you encountering this issue only on Paranoid Android?
I had about same issue with my i9100. When I charge my phone it stuck at same percent for a while (10 or 20 minutes maybe). My solution is observe your battery voltage with Battery voltage s app and try to charge when battery voltage is at 3500mV.
syedbilal093 said:
Please tell does it have the same issue on other roms? Or are you encountering this issue only on Paranoid Android?
Click to expand...
Click to collapse
i tried alot of roms like CM11 and CR rom and slim cat all had the same issue now after the latest update of CM11 i think the issue is solved 2 days and all is going well .... what do you think could it be kernel related !!
It seems like ...! It occurs due to kernel... i havent experienced such kind of issue but it is a kernel issue.
Hello guys, the camera on my CHD has stopped working from a few days, at first I thought this was a software issue because the camera would randomly work sometimes, I tried almost on all roms, the camera didn't work and just two days ago I flashed the KK 4.4.2 and the camera apk itself is missing from the system so I think its a hardware issue.
So if anybody had this problem earlier, or knows any solution for this please help me.
The thing is I don't think the camera unit is faulty because sometimes it opens when i press hard above the camera unit on its connector. So I'm not 100% sure on what problem it is..
Any help/advice is welcome..
Thank you
-Aaditya
It could be a hardware prob , i encountered the no camera app prob after installing GAPPS in CM11 and The pacman rom , i reflashed it without GAPPS and now its working, so try that.
I own a Galaxy S4 I9505 device.
Earlier I was running the stock based Custom ROM (Imperium 16.1, Android 4.4.2) on my S4 and there was no problem at all. That ROM gave me supreme performance, stability and battery life.
And then official Lollipop (5.0.1) was released by Samsung. I flashed the latest stock based custom Lollipop ROM on my device and the problem started (or may be the problem started because I have dropped my device once).
Now what happens is ... after I flash a ROM everything is working fine. But then after some uncertain period all the sensors stop working on the device.
Sometimes the issue is resolved by a simple restart, at times I have to clear the Cache and sometimes I have to clear the Cache and Dalvik Cache**.
All the sensors start working and after some time suddenly, all the sensors stop working.
I have tried all stock based Custom Lollipop ROMs and even AOSP based Lollipop ROMs, but this problem is persistent with all the Lollipop ROMS.
I have even tried Original Lollipop Firmware (flashed through odin), but the problem persists.
I open the back-cover and tightened all the screws, thinking it could resolve the issue. But the problem persists.
I am not able to decipher if this is a Software or Hardware issue.
Can anyone help me on this? Has anyone faced this type of problem? :crying:
I am not sure if this is the right place to post such a question. If it isn't please guide me to a proper thread.
Thanks
Since you just said you drop the phone.. i think it has something to do with that... looks like a hardware issue..
radz.min said:
Since you just said you drop the phone.. i think it has something to do with that... looks like a hardware issue..
Click to expand...
Click to collapse
@radz.min thanks for the screen shot .... you think it could be a hardware issue ... but as i mentioned .... sensors work good for half an hour or so and then they stop working ... if it was a hardware issue ... it should not work at all .... right ??