My phone is faulty, but everything works except proximity sensor, which makes my devise unusable after i end a call. I really need a way to disable the proximity sensor.
Im using cm7 rom.
Please help me out to make my phone usable again!
EDIT
I put this in the build.prop to completely disable it, but it doesnt work
gsm.proximity.enable=false
Click to expand...
Click to collapse
EDIT2
This didnt work either
http://www.youtube.com/watch?v=uMk1S90MjbY
EDIT3
Can anyone tell me where is the Proximity sensor driver??
I want to remove it.
Have you tried
Code:
Settings > Display > In-accurate proximity
mmec2 said:
Have you tried
Code:
Settings > Display > In-accurate proximity
Click to expand...
Click to collapse
I dont have this setting.
Im on CM7.1 official.
Is this setting available in nightly builds?
Oh, maybe it's not in the official builds because it's just for the Defy.
It is in Quarx's CM7.1.0-11 Stable (11.11.11)
I'm downloading now.
What does this option do exactly?
I m having a hardware problem, and i think only if disable the sensor will do for me.
It says it forces the screen to turn back on after a call ends, but I haven't tried it - I just saw it in the settings when I was looking for something else
I just flash the cm72-111125.0850-NIGHTLY-Defy.zip and I try the setting
Settings > Display > In-accurate proximity
Click to expand...
Click to collapse
and did the job!
Million thanks to mmec2 !!!!
But the big thanks goes always to Epsylon3, the boss
it works! huge thanks
mmec2 said:
Oh, maybe it's not in the official builds because it's just for the Defy.
It is in Quarx's CM7.1.0-11 Stable (11.11.11)
Click to expand...
Click to collapse
Hi, I had the same issue and tryed all the tricks around without success, until I read your post, flashed the 7.2 (actual quarkx), checked the option, and it is fixed indeed. Huge thanks!
Related
This thread don't update any more.
This post [CM-9.0.0-RC0-2012.03.03-KANG-XT720-J.Y.Daddy] is latest update.
From now on, please use fjfalcon's CM9.
Thanks.
------------------------------------------------------------
This rom is just alpha version.
And i did not test much.
Now sensors working!
[Not works]
camera not work.
accelerated video decoding using TI DSP not work. (from nadlabak's notice)
[nadlabak's original thread]
CM9 http://forum.xda-developers.com/showthread.php?t=1445209
[Outline]
CM9 ROM customized.(nadlabak's Milestone ROM based)
Phone Model : Motoroi XT720
Kernel Based Rom : STSKT_N_79.33.50R (Android 2.2.1)
[Install for Motoroi-XT720]
1) RSD for STSKT_N_79.33.50R (Android 2.2.1)
2) root
3) OpenRecovery install
4) ROM download and copy (/sdcard/OpenRecovery/updates)
5) OpenRecovery boot
6) Wipe Data / Factory reset (Please reset first!)
7) Apply Update
8) reboot (first boot takes a long time)
[Mirror]
http://min.us/mmDjsB8g0
[Credit]
nadlabak(kabaldan)
J.Y.Daddy said:
[Not works]
sensor's not work. (need someone help)
camera not work. (from nadlabak's notice)
accelerated video decoding using TI DSP not work. (from nadlabak's notice)
Click to expand...
Click to collapse
For now - this problems really deep inside. Video system in android 4 changed mostlly.
Wow, I knew that you wouldn't abandon us.
Edit: Just loaded it up. Really fast. Obviously, a lot of problems but nevertheless, really good start.
No market?
No wifi?
And an error kept popping up, in part english, part Korean, at every new screen, stating it will eliminate something.
So glad to have you back
rationalthinker1 said:
Wow, I knew that you wouldn't abandon us.
Edit: Just loaded it up. Really fast. Obviously, a lot of problems but nevertheless, really good start.
No market?
No wifi?
And an error kept popping up, in part english, part Korean, at every new screen, stating it will eliminate something.
Click to expand...
Click to collapse
Wifi is ready! light sensor seems to working fine.
but gravity sensor not working, camera not working
Okay it booted fast I was able to sign in to Google.
I did some ram tweaks I was able to get 70+.
I used a bootfix to get it booted.
I will get even more ram after sensors get fixed.
Looking forward in using cm9.
Sent from my XT720 using xda premium
Update.
Market works,wifi works.
I been using cm9 all day I only wish sensors worked
Sent from my XT720 using xda premium
Hi still using cm9.
Replace launcher with nova launcher replace keybroard to smart key broads.
Ram is avg 64.
Any body working on sensors.
Thanks.
Sent from my XT720 using xda premium
It's awesome & sweet, man!
I was tried with CM9 but no luck and have not much time to play around with it. Now you are back with it, that great!
Thumb up & keep great working.
I will try it soon
Tried, and this is my experiences:
Good things:
- Speed is incredible fast with many apps I installed on last CM7.X
- Wifi, 3G works
- Home button not work (cannot go home by pressing Home button) EDITED: Home button is go with different behavior compared with GingerBread, so press & hold it to see list of recent & running app, this way it work for me
and many things work as expected.
and Bad things:
- Screen rotation is not work well: look it start to work but mostly forced in landscape mode (in launcher, app) some time it go portrait for dialing screen, error message ... I was unchecked auto rotation options but not help.
- Call not work for me, it go end nearly immediate after I press call.
- SMS not work, EDITED: work after reboot, may it has blocked by some overload operations.
- Net monitor through some exceptions due: /proc/net/xt_qtaguid/stats not exist, we need kernel module for this stuff.
- Cam not work (of course )
I don't see where to customize Cyanogen such as fast switch widget on notification bar, look like we are missing Cyanogen Settings
I have problem with IO schedule in CM7 and was remove dalvik-cache from list of app2ext startup script and it solved 50% of mine. I used `lsof` to see what's going to use /sdcard & /sd-ext and see that almost operations come from background apps like launcher, theme. I think we should avoid to use bind mount to SD's ext partition to get better speed. Also use `vmstat` command will see sometime 1-3 applications block IO process and it will cause IO wait almost full (about > 90).
Anyone face problem like me? and what's solution you guys was used to solve it?
Will try to tweak it and fix some buggy if possible, keep the good work guys!
I see some have offered to help with cm9 but I'm dispointed in these forms .
The first thing thats needs to be fixed are sensors.
The camera will be the hardest to fix.
I believe the defry has the same sensors as our xt can someone do a port for are xt.
The worked good for me but their seems to be battery drain.
I would like to see some team work on this cm9.
Thanks J.Y.Daddy for your help.
Sent from my XT720 using xda premium
Anyone know the way to let android force display in portrait mode?
Currently sensors not work correctly then it always go landscape mode, it is weir.
I tried some prop in but no luck.
About sensors I tried one from CM-7.1 but no luck, look like ICS using different stuff for use sensors then fix in framework may help but I don't have time to check it out.
tiger2wander said:
Anyone know the way to let android force display in portrait mode?
Currently sensors not work correctly then it always go landscape mode, it is weir.
I tried some prop in but no luck.
About sensors I tried one from CM-7.1 but no luck, look like ICS using different stuff for use sensors then fix in framework may help but I don't have time to check it out.
Click to expand...
Click to collapse
Un-check the box for: Settings --> Display --> Auto-Rotate Screen
Unless....of course....that is being overwritten by something in CM9.
I tried it already, unchecked auto rotate option in display setting & Trebuchet but no luck.
mchlbenner said:
I see some have offered to help with cm9 but I'm dispointed in these forms .
The first thing thats needs to be fixed are sensors.
The camera will be the hardest to fix.
I believe the defry has the same sensors as our xt can someone do a port for are xt.
The worked good for me but their seems to be battery drain.
I would like to see some team work on this cm9.
Thanks J.Y.Daddy for your help.
Sent from my XT720 using xda premium
Click to expand...
Click to collapse
we can always use a 3rd party Camera App, if we can not fix the camera, right?
or are you referring to the kernel knowing there's a camera attached to the phone?
AllGamer said:
we can always use a 3rd party Camera App, if we can not fix the camera, right?
or are you referring to the kernel knowing there's a camera attached to the phone?
Click to expand...
Click to collapse
ICS changed the camera API significantly. I don't think anyone's figured out how to use the older libraries yet. Non-functioning camera is pretty common at the moment.
We really to find a fix for the sensors first then fix other things.
Sent from my XT720 using xda premium
For camera, AFAIK we need to write a new kernel module for it as ICS is using HAL then we must have:
- /system/lib/modules/camera.ko
- /system/lib/hw/camera.sholes.so
EDITED: I've just tried with hw/camera.goldfish.so & camera.ko from MS2 then Camera app just loaded with colored box pinging, at least it not show "Cannot connect to Camera" message
Stskt_n_79.33.50r
hey guy where can i get STSKT_N_79.33.50R
What are you using motorio or milestone xt720.
If you using motorio go J.Y.Daddy cm7 thread the link is their.
Sent from my Milestone XT720 using xda premium
I have a problem on this rom v2.1 Illusion I came subscribe to the whatsapp it seems to me that it is not available for the tablet anyone know where are you fix it?
naor120 said:
I have a problem on this rom v2.1 Illusion I came subscribe to the whatsapp it seems to me that it is not available for the tablet anyone know where are you fix it?
Click to expand...
Click to collapse
Clear data and cache of whatsapp.
hotdog125 said:
Clear data and cache of whatsapp.
Click to expand...
Click to collapse
ok Thank you i will try this
naor120 said:
I have a problem on this rom v2.1 Illusion I came subscribe to the whatsapp it seems to me that it is not available for the tablet anyone know where are you fix it?
Click to expand...
Click to collapse
You can't just solve it by wiping app data. Whatsapp does not support tablets!
I think you have a market fingerprint issue. Because Illusion is a new ROM port by Kayant, he might not have changed the original market fingerprint. Since illusion uses Paranoid's LCD density settings, meaning that you can set a phone/tablet/phablet ppi, you should try changing it back to phone dpi if you can.
droid_<3er said:
You can't just solve it by wiping app data. Whatsapp does not support tablets!
I think you have a market fingerprint issue. Because Illusion is a new ROM port by Kayant, he might not have changed the original market fingerprint. Since illusion uses Paranoid's LCD density settings, meaning that you can set a phone/tablet/phablet ppi, you should try changing it back to phone dpi if you can.
Click to expand...
Click to collapse
I also thought about it but could not find the settings to change it
naor120 said:
I also thought about it but could not find the settings to change it
Click to expand...
Click to collapse
This error is quite common in the new CM10 and CM10.1. It can be fixed that way. Even with tablet UI and dpi i could make whatsapp work.
dunno, whatsapp works for me on all the CM10 and CM10 based ROMs I've tried. I think the fingerprint is the only logical explanation, if the add data wipe doesn't work.
I got cm10.1 is really good but I having trouble with the camera like its just stopped working after I switched to front camera. Can anny one pleeeeaaaaase find me a fix !!
MooSeKilla said:
I got cm10.1 is really good but I having trouble with the camera like its just stopped working after I switched to front camera. Can anny one pleeeeaaaaase find me a fix !!
Click to expand...
Click to collapse
What's your phone model?
adrienj said:
What's your phone model?
Click to expand...
Click to collapse
p705g ,but the rom is p700.
MooSeKilla said:
p705g ,but the rom is p700.
Click to expand...
Click to collapse
you can't switch back to the back camera? How did you switch to front camera?
adrienj said:
you can't switch back to the back camera? How did you switch to front camera?
Click to expand...
Click to collapse
i just went to the camera and it was working fine. i herd down on the screen for the options and i switched to front camera and i got a message saying couldn't connect to camera and it crashed now everytime i go to use the camera its just grey and crashes
MooSeKilla said:
i just went to the camera and it was working fine. i herd down on the screen for the options and i switched to front camera and i got a message saying couldn't connect to camera and it crashed now everytime i go to use the camera its just grey and crashes
Click to expand...
Click to collapse
yes the default camera application crash at start in this case. Try to install CameraMX, launch it, go to options and then select front camera.
adrienj said:
yes the default camera application crash at start in this case. Try to install CameraMX, launch it, go to options and then select front camera.
Click to expand...
Click to collapse
Camera mx doesnt even work crashes
Try this in the Terminal:
Code:
su
rm -rf /data/data/com.android.camera/shared_prefs/com.android.camera_preferences.xml
adrienj said:
Try this in the Terminal:
Code:
su
rm -rf /data/data/com.android.camera/shared_prefs/com.android.camera_preferences.xml
Click to expand...
Click to collapse
okay wrote it but nothing happens .......
same problem
MooSeKilla said:
i just went to the camera and it was working fine. i herd down on the screen for the options and i switched to front camera and i got a message saying couldn't connect to camera and it crashed now everytime i go to use the camera its just grey and crashes
Click to expand...
Click to collapse
Tudor never fix the front camera :/
I try to compile cm10.1 to fix the error, but always give me error in compilation
Sorry for my bad english.
FedeeManchiini said:
Tudor never fix the front camera :/
I try to compile cm10.1 to fix the error, but always give me error in compilation
Sorry for my bad english.
Click to expand...
Click to collapse
i honestly love the rom cause all other ones seems too laggy on my phone. but the only problem this has is teh camera maan i just need to find a fix !!
give the file list in /data/data/com.android.camera*/shared_prefs/ :
su
ls /data/data/com.android.camera*/shared_prefs/
I installed BlissPop 4.0 (http://forum.xda-developers.com/tab-4/development/rom-blisspop-3-1-t3084757) on my T530 the other day. Everything went fine and it's running smoothly. But the pulldown menu (notifications section) when you swipe from top to bottom is small, as if the rom thinks I'm on a phone. Is there a UI setting to tell it this is a tablet, and that it can use the entire screen?
Thanks in advance!
ClutchFanB said:
I installed BlissPop 4.0 (http://forum.xda-developers.com/tab-4/development/rom-blisspop-3-1-t3084757) on my T530 the other day. Everything went fine and it's running smoothly. But the pulldown menu (notifications section) when you swipe from top to bottom is small, as if the rom thinks I'm on a phone. Is there a UI setting to tell it this is a tablet, and that it can use the entire screen?
Thanks in advance!
Click to expand...
Click to collapse
there is an overlay setting to size the drawer. i will try too enlarge in the next build.
btw. better post rom specific things into the rom thread.
BlissPop Didnt Work for Me
sub77 said:
there is an overlay setting to size the drawer. i will try too enlarge in the next build.
btw. better post rom specific things into the rom thread.
Click to expand...
Click to collapse
@sub77, I tried the blispop builds that you provided. The 110 was the last update. I would like to mention here, that the animations and the other features are awesome... Great work pal!!!
In my case though, I did a custom ROM Install and then also flashed the modem (from bruce) yet I dont have any luck with the Mobile Connection. Also, the rear camera did not function for me. But yes, I have the Wifi and Bluetooth running. themes are functioning proper. There is a little glitch in opening the notification bar, as it does not easily get pulled down.
Can you shed some light on my concerns???
Regards,
GenXCoders
genxcoders said:
@sub77, I tried the blispop builds that you provided. The 110 was the last update. I would like to mention here, that the animations and the other features are awesome... Great work pal!!!
In my case though, I did a custom ROM Install and then also flashed the modem (from bruce) yet I dont have any luck with the Mobile Connection. Also, the rear camera did not function for me. But yes, I have the Wifi and Bluetooth running. themes are functioning proper. There is a little glitch in opening the notification bar, as it does not easily get pulled down.
Can you shed some light on my concerns???
Regards,
GenXCoders
Click to expand...
Click to collapse
camera issues are well known.
110 update?
try to flash the modem shipped with your stock kitkat rom.
if you wont get it work i need logs to help you.
sub77 said:
there is an overlay setting to size the drawer. i will try too enlarge in the next build.
btw. better post rom specific things into the rom thread.
Click to expand...
Click to collapse
thanks!
I tried replying to the rom thread but it gave me a hard time. I'm not allowed to post there till I have like 100 posts or something. Oh well.
Anyway thanks again - great rom I'll keep my eyes peeled for the next build
sub77 said:
camera issues are well known.
110 update?
try to flash the modem shipped with your stock kitkat rom.
if you wont get it work i need logs to help you.
Click to expand...
Click to collapse
by 110 i meant the built of 20150831-0110
Hi there,
I'm using Google Cardboard quite a bit. In the latest NucleaRom (Nougat 7.1/CM 14.1) I have come across the following:
-- DPI is set to 420 via Nuclear Tweaks
-- in Google Cardboard, the view area is somehow scaled down to a fraction (full screen before, now it's about 1/4 of the screen) of what it used to be? => see as well the vid of somebody else with the same problem: http://youtu.be/UPJoNlolF0o
Anybody else had that problem and could fix it?
Many thanks in advance for any help/hints/suggestions
You must set it to 400 DPI.
Borja Viera said:
You must set it to 400 DPI.
Click to expand...
Click to collapse
Thank you for the answer, but that didn't do anything.
Can you please confirm, that it works on your device with NucleaRom 7.1?
Thank you
meikelrix said:
Thank you for the answer, but that didn't do anything.
Can you please confirm, that it works on your device with NucleaRom 7.1?
Thank you
Click to expand...
Click to collapse
I had that same issue with cm14 and that seemed to do the trick, I hadn't tried cardboard yet so I didn't know about this issue and exactly the same has happened to me with Nuclear 7.1 . After using an app called vr calibration for cardboard and trying to calibrate it seemed that increasing screen to lens distance seemed to do the trick. Try it out and tell me how it works for you.
Edit: After editing the profile and trying it out with another app it is still the same so I guess it will stay like that whatsoever. We'll have to tell to Nuclear devs.
Borja Viera said:
I had that same issue with cm14 and that seemed to do the trick, I hadn't tried cardboard yet so I didn't know about this issue and exactly the same has happened to me with Nuclear 7.1 . After using an app called vr calibration for cardboard and trying to calibrate it seemed that increasing screen to lens distance seemed to do the trick. Try it out and tell me how it works for you.
Edit: After editing the profile and trying it out with another app it is still the same so I guess it will stay like that whatsoever. We'll have to tell to Nuclear devs.
Click to expand...
Click to collapse
Well, in the mean time I went to https://vr.google.com/cardboard/viewerprofilegenerator/ and created my own 'viewer' by exaggerating the "Screen to lens distance" and the "Inter-lens distance". => Trial and Error
meikelrix said:
Well, in the mean time I went to https://vr.google.com/cardboard/viewerprofilegenerator/ and created my own 'viewer' by exaggerating the "Screen to lens distance" and the "Inter-lens distance". => Trial and Error
Click to expand...
Click to collapse
That didn't work at all for me
Borja Viera said:
That didn't work at all for me
Click to expand...
Click to collapse
you want to use Google Chrome browser. Then, once called the above mentioned URL, you can "Save or Load Viewer Parameters". There you can paste following URL: http://google.com/cardboard/cfg?p=C...CAABIQgAASEIAAEhCWAE1KVwPPToICtcjPArXIzxQAGAA
Those are settings for the "Homido Mini" device (please keep in mind theyr'e counter compensating the screen resolution).
After pasting the settings URL, you need to click on the blue "Generate Profile" button. This will give you a DataMatix, that you need to scan via Cardboard as a new viewer (the same for Street View, btw.)
best regards