Ever since Miui and Cyanogen moved over to Gingerbread (2.3) my HTC EVO's acceleromtor has been off set. I've checked my sensor settings with Z-DeviceSet and confirmed that the y/x/z axis are all off set. Since there's no built in g-sensor calibration like in previous Android builds how do I correct this? I need some type of fix to correct the screen rotate issues i'm having through MIUI 1.5.27 ROM.
I've even tried to log into system/bin looking for the "sensorcalibutil_yamaha" but no such file exsist!
I'm out of ideas, please help!
Bump--same issue here!
Related
Since I usually only download ROMs and modify them for myself in a simple manner I am forced to ask this here, and not the ROM dev section, due to "not enough posts".
I am running a rooted HTC Desire Z, the ROM is Andromadus Mimicry 1.4.0 stable. This is not my first Cm9 based ROM, before ICS I was running official ports of CM7 (up to the newest nightly) as well.
Question:
Is there a way to change a setting in Mimicry, to make the device not unlock the screen while I slide the keyboard? I remember CM7 had this option somewhere, The phone sometimes flips while I take it out from my pocket, and unlocks the screen upon that. I hope this is understandable. I need the Desire Z not to unlock itself upon opening keybard (want it to flip the screen, backlight on, lock screen still on). Is there an option burried somewhere in the menu? Or the ROM simply lacks that option? Thx in advance for any reply.
Ponury666 said:
Since I usually only download ROMs and modify them for myself in a simple manner I am forced to ask this here, and not the ROM dev section, due to "not enough posts".
I am running a rooted HTC Desire Z, the ROM is Andromadus Mimicry 1.4.0 stable. This is not my first Cm9 based ROM, before ICS I was running official ports of CM7 (up to the newest nightly) as well.
Question:
Is there a way to change a setting in Mimicry, to make the device not unlock the screen while I slide the keyboard? I remember CM7 had this option somewhere, The phone sometimes flips while I take it out from my pocket, and unlocks the screen upon that. I hope this is understandable. I need the Desire Z not to unlock itself upon opening keybard (want it to flip the screen, backlight on, lock screen still on). Is there an option burried somewhere in the menu? Or the ROM simply lacks that option? Thx in advance for any reply.
Click to expand...
Click to collapse
I don't believe that option exists. Post in the Mimicry forum asking it to be added as a feature
Like I said previously, I do not have persmission to access replying in development sections, since I got a 10 post limit to reach, and I don't want to travel from sub-forum to sub-forum spamming random posts to achieve that -.-
Hello,
I have ARC S that runs very well with all Stock based kernels (Ultimate HD, JJ Hybrid, OptiMAX, and others)
I wish to upgrade to the JB, however on all kernels and roms (FXP, AOKP, Lupus) I have the following problem:
when I answer or make call -> the screen becomes black and no key is responding.
when the call ends -> the screen return to normal condition.
seems that the proximity sensor is making this problem (maybe the calibration is wrong with the JB kernels / roms)
how can I solve this case ?
BR,
From what I know, it is normal that screen turns off during call, if you put phone next to ear. Or did I misunderstand anything?
I'm referring to a problem I have:
In all versions of JellyBean when I answer a call the screen becomes black and nothing functions as if the phone thinks its close to the ear (as if the proximity is stuck on 0 distance).
I do not have this problem on ICS versions.
* all versions of JellyBean = cm10, aokp, aosp, slimbean,
I've tried multiple kernels for JB and with all I experience the same.
Anyone knows the reason why proximity sensor is not working properly on cm10 ?
Then it is because Sony hasn't made the libs open-source, so they could be made to work on JB. Due to incompability issues, these bugs occur. Nothing that developers could do at the moment.
Apparently I'm not the only one suffering from this proximity sensor issue.
the effect is huge:
when answering a call the screen does not response any more and I cannot disconnect calls.
I found:
http://forum.xda-developers.com/showthread.php?t=1985539&page=9
Originally Posted by f_zurzolo View Post
Yes the proximity sensor bug is the main reason why I am not using this ROM as well. But check back a few posts. . . the dev said he's gonna fix it. Thanks in advance n1kolaa
Click to expand...
Click to collapse
Since it happens with all JB ROMs, could it be a kernel issue?
Anyway thanks
Click to expand...
Click to collapse
Does anyone know how to solve proximity sensor on the JB roms ?
Does anyone ha any updates on this?
I'm having the same problem and it gets quite annoying.
Hello everyone!
I've been busy lately flashing different roms to my t989, trying to solve the problem described in this thread: http://forum.xda-developers.com/showthread.php?t=1161262.
I've tried some of the newest roms and kernels (All-star 4.2, CM10, 10.1, AOKP) but the issue is still there. The attached APK on that thread does not work And I have no idea how to do the kernel modification ;(
Anything that can be done to solve it? The touchscreen sensitivy option is grayed out on the roms I've tried so far. It's annoying on games like Modern Combat, or TeamViewer (mouse is jumpy). Or do I have to modify an existing kernel? :crying:
Thanks!
I have just noticed this problem.. no wonder the touchscreen sometimes jumps in Dead Trigger
Thank you for bringing this up, hopefully the kernel devs will take a look at this and probably fix this
It could be a slider or something like that :laugh:
I just noticed that, I was noticing lag, mainly in the youtube application when i'm scrolling, thought it was my rom or phone. I notice it as well with the ripple lock option in embryo 6.
This topic is meant to summarize all that was written about that diabolic DHD proximity sensor.
Let's gather everything you find, and try to solve this once for all, and please let's not spam dev forum section with such talks.
Scenarios:
1) The screen doesn't dim/shuts off when making a call.
Solution: First try a great app Proximity recalibrator, which can be found here (thank the guy, he did great job):
http://forum.xda-developers.com/showthread.php?p=11312762
Also, READ the whole thread before saying it doesn't work.
2) The screen dims fine (or eith some help of above app), but DOESN'T LOCK, or it turns ON when the call is answered/randomly during the call.
Solution: NONE found.
Let's assume that you've eliminated the "faulty sensor" option by:
- cleaning the sendor with cotton wab and alcohol
- trying some really different rom, like Sense.
As far as I know, sensor works with Sense roms, and problem happens with:
- aosp cfx 4.x.x (no matter the SR version)
- jellytime
So it might be something in cm10.
Or?
Write below what you know!
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
My sensor works fine with 4/5 (LT/HT) values
Sent from my Desire HD using Tapatalk 2
Ok
Also, I think the country you bought it from (and whether it is a inspire/desire), the radio in use (and RUU) could be important factotrs.
Using a British Desire HD,
July 2012: Radio 12.69.60.29_26.17.14.11_M - AT&T Inspire 4G 3.20.502.52 (Latest)
Running CFX 4.2.2 SR15+banks gapps with no work arounds.
I have used Ice Cold sandwich, jellytime 4.1/4.2 trainwreck, CodefireX 4.1/4.2 and multiple sense Roms (2.3/4.0) in the past.
I am having NO issues (although on older release of CFX, SR8 I had some random reboots)
IDK what all the complaining is about
(I have had other issues on Alpha releases (and occasionally betas)of ROMs, but Alphas are expected to have issues.)
Great, detailed info to start from.
For me, only sense (stock gb, sabsa ICS, Viper ICS) worked fine. All JB cm10 failed, and screen just doesn't lock.
Didn't realize that radio has anything to do with sensor.
What do you mean by "country matters"?
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
I have also had NO issues with the proximity sensor or the screen lock during calls, no fixes or calibrations made.
I've been using only JellyTime R6.1 for about a month now as my daily driver.
My DHD was bought from England. Using it now in Israel. All other info is in my signature.
broken hardware
Is there anyone that knows where the proximity sensor is actually located in the phone?
My guess would be the motherboard flex cable... :/
So my problem is, that i've dropped my DHD, and ever since then the proximity sensor/light sensor doesn't work (it is the same sensor), and I'm pretty sure that the hardware is broken.
Lately, I have been looking into the possibility of disassembling the phone, and replacing the broken part...
But as of now, i have no idea which part the proximity sensor is actually integrated onto.
Any ideas? I watched about a dozen disassembly videos on Youtube, but not one of them mention the proximity sensor.
Thanks in advance
This seems like HTC official dissassemble video:
https://www.youtube.com/watch?v=JfatoeWbMRk&feature=youtube_gdata_player
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
iopetja said:
Great, detailed info to start from.
For me, only sense (stock gb, sabsa ICS, Viper ICS) worked fine. All JB cm10 failed, and screen just doesn't lock.
Didn't realize that radio has anything to do with sensor.
What do you mean by "country matters"?
----
If I helped, please press Thanks...
DHDcfx4.2.1SR11deappified
Click to expand...
Click to collapse
The model sold in different countries (if it differs, I don't know) and the radio provided in different countries will make a difference.
(Sorry for late reply)
edit: The radio controls many of the phone's functions like the wireless and the cellular. It might control or affect the proximity sensor too.
I'm still running Whomp 3.2 for my Note 2 has anyone had problems with the auto rotation getting stuck once it rotates? The only way to get it back is to uncheck the auto rotation.
I know that 3.4 is out but it appears there are a couple of issues that might be resolved shortly so I was waiting to upgrade.
I would like to post this issue for the development team but don't have rights yet
I would also be interested in testing 3.5 if you need testers.
Any feedback would be great
Joe