Hi guys,
I've been using ms2ginger 4.0 and just changed to CM10 by Quarx.
The problem is that as soon as i dial a number the screen goes dark and i could use the power button to display the screen in ms2ginger but not in the cm10 edition.
It happens atleast 9 times out of 10.
Any solution, is the screenguard culprit ?
or any fix for the sensor to work properly?
it was wrking perfectly when used the official froyo!!!
trojanx said:
Hi guys,
I've been using ms2ginger 4.0 and just changed to CM10 by Quarx.
The problem is that as soon as i dial a number the screen goes dark and i could use the power button to display the screen in ms2ginger but not in the cm10 edition.
It happens atleast 9 times out of 10.
Any solution, is the screenguard culprit ?
or any fix for the sensor to work properly?
it was wrking perfectly when used the official froyo!!!
Click to expand...
Click to collapse
I'm on CM9 and there is a setting under "System Settings > Display" which says "In accurate proximity". See if that's in CM10 and works for you.
defydent said:
I'm on CM9 and there is a setting under "System Settings > Display" which says "In accurate proximity". See if that's in CM10 and works for you.
Click to expand...
Click to collapse
Thanks for your reply, in cm10 couldn't find that option moved to cm9(mig edition)
the problem is still there after checking the proximity option but not that much
Found a Solution
I was searching all around this place.
Found a solution that the screw just behind the proximity sensor (when you open the back panel) was a bit tight, too much i guess, just loosened that screw to a single round and it is working perfectly.
Maybe help anyone facing the same issue.
P.S. i did open my whole phone once and i guess tightened the screw too much.
Related
Hi Guys, my first post! I'm having a troubles with my Blade. The rotating sensor axys isn't working, to be honest it never been working, even with the stock rom. I'm now running Cyano Gingerbread 7 and the situation looks always the same. Tried to switch the button on the menu off/on many times and tried also to move fast the phone in my hands... There is a way to check it? Somebody haves the service manual of the Blade, or help me in some way.
Thanks in Advance.
Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers
rohan2jos said:
Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers
Click to expand...
Click to collapse
Which phone MB526 or MB525??
If it is MB525 then which color lens (Green or Red)?
However, in both the cases you may search the thread from which you have downloaded the ROM; that thread may have Camera fix for your phone.
rohan2jos said:
Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers
Click to expand...
Click to collapse
Maybe, it helps.
Go to settings > apps > manage apps > all > camera > erase data
rohan2jos said:
Guys,
i had earlier flashed cm 7.2 to my defy plus with the battery fix and the camera fix....everything was working fine
However, a few days back, i got it back to the stock 2.3.6 via custom recovery....everything works normally, however, the camera is not working
It starts up and shows a blank screen with all the options....as if the camera were on, and someone had switched off just the lens....
When i click, the picture is taken and i can see the image, however, i cannot see the viewfinder view.....
Please help me....cheers
Click to expand...
Click to collapse
Happened to me few days back on CM7.2... turned out the culprit was "live logcat"...
[check: http://forum.xda-developers.com/archive/index.php/t-1146496.html]
Not sure if what you are facing is the same thing...
Playing around with Android Sensor Box I noticed that the accelerometer on my device needs calibration. Right now, laid on a flat horizontal surface, it looks like it's tilted a little to the left. The problem is I can't find the option to calibrate on Jelly Bean. On my old Gingerbread phone I could do it from Settings > Display > Horizontal calibration.
Is there any way to do a system-wide calibration of the accelerometer?
OK for anyone having this problem: I turned the tablet off, laid it horizontally and turned it on again, which seems to recalibrate the accelerometer. Rather inconvenient, but it works.
Try the sensor tester app from the play store.
Sent from my Nexus 7
zamuz27 said:
OK for anyone having this problem: I turned the tablet off, laid it horizontally and turned it on again, which seems to recalibrate the accelerometer. Rather inconvenient, but it works.
Click to expand...
Click to collapse
I have just tested that and it does not work for me.
veeman said:
Try the sensor tester app from the play store.
Click to expand...
Click to collapse
well, it seems that this also does works only sometimes - at first it solved my problem, but after few days and reboots (there was also a ROM change involved), it stopped working for me (well, the calibration seems to works well, but other apps sees only miscalibrated results now... Looks like I will have to have my Nexus replaced (which I realy hate) :crying:
kar10s said:
I have just tested that and it does not work for me.
Click to expand...
Click to collapse
For what it's worth, I've always been on stock Jelly Bean. When I first had issues with the accelerometer, powering off/on to recalibrate worked for me on 4.1.2, and I haven't had issues since, even after upgrading to 4.2 and doing a factory reset. Maybe you could give the latest stock ROM a try before replacing your Nexus 7.
hello fellow xda-ers
I recently updated to the latest and stable CM10.1 (after using M2,M3, RC3 and RC5) and noticed that my home button stops working after a while. I'm not sure when it started but I think it was with the RC.
I did a search but it didn't yield anything particularly relevant. Is that a known problem?
I just reinstalled everything after resetting all data and it still happening.
thanks in advance for your input,
n
edit: before someone mentions it, I read this thread:http://forum.xda-developers.com/showthread.php?t=2340170 where the user indicates that re-flashing everything and restoring his apps using TB fixed the problem. That's exactly what I did but the problem persists unfortunately.
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
same thing is happening to me. i was running cm since i bought the phone in February. Decided to flask Franco and now I'm getting this weird touch screen problems. The bottom row where the home button is located will become unresponsive. I decided to go into developer settings and enable "show touches". My phone is sometimes touches without my physical input.
Not sure if kernel related or if my touchscreen coincidentally has given out. I'm gonna try flashing stock kernel and see if that fixes things
nks2105 said:
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
Click to expand...
Click to collapse
I have the same problem on
Franco M3 and CM10.1 stable, just I'm not sure if it started when I flashed CM stable or Franco M3. Home button doesn't work with app draw open and also it doesn't swap from one homescreen to the default.
However if I got to settings>Launcher>Homescreen>Default screen and change it to another screen then back again the home button works properly but after a few days it stops again.
edit: its as if it just forgets what screen is supposed to be default
Hi all.
I have an issue with proximity sensor on my i9505.
It works well when i reboot my phone... But after 30 min - 1 hour it stops to work.
I'm on c-rom 7.1 but i have this issue on all roms.
I've tried to clean it. I've disassembled my phone and cleaned the sensor with alchool and a cotton fioc, but i have even the problem.
I've noticed the problem because when i go to modify the automatic brightness values, the value "lux" is stopped on a number and doesn't change...
What can be? Please help me!!!
santya95 said:
Hi all.
I have an issue with proximity sensor on my i9505.
It works well when i reboot my phone... But after 30 min - 1 hour it stops to work.
I'm on c-rom 7.1 but i have this issue on all roms.
I've tried to clean it. I've disassembled my phone and cleaned the sensor with alchool and a cotton fioc, but i have even the problem.
I've noticed the problem because when i go to modify the automatic brightness values, the value "lux" is stopped on a number and doesn't change...
What can be? Please help me!!!
Click to expand...
Click to collapse
Hi mate,
See if the sensor calibration is ok, check here:
http://forum.xda-developers.com/showthread.php?t=2569141