I had Slimbean w/ Android 4.1.2 up until a few days ago and and now the newly released Slimbean RC2 w/ Android 4.2.1 and across both roms, I've had problems with the proximity sensor not working. Since it's across both roms and my friend with the exact same phone and same rom doesn't have this issue, I don't really think it's a rom specific problem. When I am in a call, the screen never shuts off, and I just tried a sensor testing app today and it doesn't detect changes when I wave my hand in front of it. I haven't found anyone else with this problem either, and have no idea what to do from this point.
It's entirely possible that it's just broken...?
Bump
Related
Hello folks, I just wanted to know if anyone else if having issues with the proximity sensor when making a call with this HKTW 2.3.4. I made a few calls and it doesn't shut the screen off when I put the phone to my face, so I accidentally hung up on a couple people while talking to them.
Anyway, I guess I should flash back to Froyo, lol for stability leave the new ROM alone until it's finished, but I was really enthused about unlocking, flashing, setting up.
I haven't had that problem no i been on this since yesterday trying to find every bug but , I gotta say this is pretty stable.
Blur dont work but could careless my gps works which what u use the most
and i like how this rom supports usb tether and wifi tether WHICH BOTH work.
I think the prox sensor should work..it works for the pocket detection thing...
Don't know if your still having this problem but you can change sensitivity for proximity sensor with your build.prop. well not sensitivity but range.
AT&T ATRIX - VERSION 2.3.4 ROOTED BL UNLOCKED
I searched for discussions on this and couldn't find any. Sorry if I'm posting something that has already been discussed.
I have followed the saga of GPS on Gingerbread, and I tried out a couple of GB ROMs over the last couple of days and was thrilled to see GPS working!
Unfortunately, the compass, an important component when navigating, it seems is broken on all Gingerbread ROMs for the Vibrant, from what I hear.
What is preventing this from working? Is it another component that is completely blocked until we get a leak?
Thanks!
Bump.
No one knows?
Try turning on the GPS sensor.
Emal510 said:
Try turning on the GPS sensor.
Click to expand...
Click to collapse
As I mentioned, from what I understand, this is an issue with GB ROMs on our phones, similar to the GPS issue that was only just recently somewhat solved. I got that info from the dev of Revolution ROM.
Could someone please test it on the newsets GB ROMs/Kernels? I'm also wondering is it working correctly with CM/MIUI?
I'm almost 100% sure this isn't working in the latest nightlies of CM7. Viewed as a low priority in comparison to the 911 issue and other things.
Okay so this is my first post on XDA and I hope it's in the right section. Anyways I bought an HTC Incredible off a collegue of mine about two weeks ago. I got the phone and immediately rooted and installed a custom rom (MIUIv4 to be exact) I noticed after a lil while that the touch screen would randomly go berserk clicking things, calling people, etc (usually right after turning screen on) When the screen starts doing it I'd turn it off and back on and it would be completely fine. I thought to myself "maybe it's just a problem with MIUI and installed PONS CM7. I still had the same issue. Now whats strange about all of this is if I'm running an RUU or Stock based rom the screen NEVER acts up. I've read on several forums that this is a hardware issue but most people still experience it on stock roms, this is not the case with me. I won't deny that it could be a hardware issue, but it's an issue that can be solved with kerenl/dirvers/software. I'm wondering if I can use the drivers and software from a stock based rom to combat the issue and make custom roms run like they are supposed to. In all of my research I found this link which seems to be pretty promising but I don't know where to begin with it. Unfortuneately I can't post a link until I've posted 8 times, uuugh.
Edit: It seems the longer I run a custom rom the more frequently the issue happens.
If anybody is intrested in helping it would be greatly appreciated. I've been racking my head for over a week on this one. You can look up the blog I read on google. It looks like it could solve my problem.
Unresponsive touchscreen of Nexus S solved by tuning kernel
I have been trying a variety of Android 5.0 Roms on my Verizon Galaxy S4. While most of them work pretty well, there is one thing that is consistent across all the 5.0 roms on my device: the compass' orientation is completely off. When held in portrait mode, the compass points east when facing west and west when facing east. If the phone is rotated into landscape mode, then north and south are flipped instead. The problem seems to be the X-axis of the magnetic sensor. I have tried calibrating the compass in variety of different ways with a variety of different apps. I also tried both the GoogyMax kernel and the Alucard kernel with the same results compass-wise.
While this would appear to be a hardware issue, the compass works perfectly in Kitkat and older roms. I even tried flashing an old Kitkat rom after trying some Lollipop roms and, sure enough, the compass was working properly as soon as the Kitkat rom booted.
Is there any way to mod the system to inverse the number normally reported for the X-axis of the magnetometer? Otherwise, is there some other way to fix this flipped compass issue?I have searched high and low, but can't find anything of use.
Same issue here, but I have sprint sgs4.
MehStrongBadMeh said:
I have been trying a variety of Android 5.0 Roms on my Verizon Galaxy S4. While most of them work pretty well, there is one thing that is consistent across all the 5.0 roms on my device: the compass' orientation is completely off. When held in portrait mode, the compass points east when facing west and west when facing east. If the phone is rotated into landscape mode, then north and south are flipped instead. The problem seems to be the X-axis of the magnetic sensor. I have tried calibrating the compass in variety of different ways with a variety of different apps. I also tried both the GoogyMax kernel and the Alucard kernel with the same results compass-wise.
While this would appear to be a hardware issue, the compass works perfectly in Kitkat and older roms. I even tried flashing an old Kitkat rom after trying some Lollipop roms and, sure enough, the compass was working properly as soon as the Kitkat rom booted.
Is there any way to mod the system to inverse the number normally reported for the X-axis of the magnetometer? Otherwise, is there some other way to fix this flipped compass issue?I have searched high and low, but can't find anything of use.
Click to expand...
Click to collapse
Currently I'm still running the KitKat GPE ROM and my compass is also flipped, I know the fix was to flash a Ktoonz kernel and it would fix the issue for that. However I don't think they've fixed it as yet for 5.0 ROMs.
It's the Kernels.
It's not due to the ROMS or hardware.
The backwards compass is due to the Kernel installed with the ROM or that you may have downloaded and applied. Kernels now are compiled as Unified kernels which work across all carriers. They are simpler for the Devs to manage without having to compile their kernels for each carrier. That messes up our compass though.
KT-Kernel's fixed our issue when they were compiled carrier specific.
Unfortunately for us KT has gone Unified like the other international Kernels and the international base and compass drivers are from the other side of the world, which cause ours to go backwards on East/West.
I have been looking through KT kernels on the Github and trying to make sense of the drivers and compile configs trying to figure out if a dev could ever come up with a patch.
But I am still new to it all when poking through the KT's source files.
I have oneplusone and it shows the same symptom. Installed magneticsensor app and found out that Bz is inverted. Bz is the direction orthogonal to screen such that it is the most important in navigation ! I would like to see the kernel source for the sensor but haven't set it up yet. If you are/know kernel dev, a help would be appreciated.
pastime1971 said:
I have oneplusone and it shows the same symptom. Installed magneticsensor app and found out that Bz is inverted. Bz is the direction orthogonal to screen such that it is the most important in navigation ! I would like to see the kernel source for the sensor but haven't set it up yet. If you are/know kernel dev, a help would be appreciated.
Click to expand...
Click to collapse
You are not going to to find much help for the Oneplus One here. It was definitely a kernel issue though, as for the Verizon Galaxy S4 it was fixed thanks to updates to the Hulk and Alucard kernels that compensate for the flip.
MehStrongBadMeh said:
You are not going to to find much help for the Oneplus One here. It was definitely a kernel issue though, as for the Verizon Galaxy S4 it was fixed thanks to updates to the Hulk and Alucard kernels that compensate for the flip.
Click to expand...
Click to collapse
Actually, I was able to fix it via /system/etc/sensor_def_qcomdev.conf and deleting /data/misc/sensor/sns.reg without touching kernel or hw-lib
see http://forum.xda-developers.com/one...tic-sensor-t3176956/post62301573#post62301573
Theoretically, we're due for a magnetic pole shift. Every 23,000 years our planet pole shifts. I know, sounds crazy doesn't it?
I bought the S5 phone a few weeks before Xmas. The first one there was issues so I took it back and got the one I have now. Everything worked fine until one day the gyroscope stopped working. I was so angry because of course there is no store warranty anymore and it's a new phone! I know people say this, but I didn't drop it, no water, no over heating. It just stops working.
I read all the stuff that I could online, nothing worked for the long haul. Was told that I would have to replace the motherboard, because it was a hardware issue.
I finally one day I got really frustrated. It worked before all the updates, then as soon as Lollipop was on, the gyroscope stopped working. It made no sense to me that it's the device. So I rooted it and put Resurrection Remix N. It worked wonderfully. No issues with the Gyroscope at all for the week I ran RR N. But then there was this green flashing thing that was happening that was equally annoying. It would do it just before the phone went to sleep. Drove me nuts. Didn't do it in stock rom, but I read that it means I need to replace the screen??? Tinkering around a bit, I think it's the SD card. At least I hope its the SD card, because that ROM rocks! I have reformated the SD card and the phone works great, then it starts flashing green stuff again at the bottom of the screen. I have a few entries on the forum for the ROM but until I can figure other factors it may be
So, then I have to go back to Stock ROM. Thought I could just flash 4.4.2 on it and call it a day until my SD card comes in. But there are system stop errors that leaves the phone unusable. So I have update the phone all the way up to Marshmallow.
So until I can get a good SD card in and try out RR N again. Could anyone give me ideas on why the gyroscope works flawlessly on RR N but not on the stock ROM? I don't get it?
Thanks in advance for any ideas.
I am cerrtain its not a gyroscope issue, its something in the Stock ROM, because it does work great on RR N
That was my thinking but it's happening. It works perfectly on RR N rom but stops working on Stock rom.
Updating.
Flashed the stock ROM again, just to prove a point that yes indeed the gyroscope stops.
In the stock ROM the screen does not flash at all. But the gyro was ticking me off.
I ended up trying Lineage OS 14.1 and the gyroscope has worked flawlessly. But now the green flicker on the bottom screen is happening.
So recap
Stock ROM: gyro stops working, screen works great
Custom ROM: gyro works and is very responsive green flicker happens before the phone sleeps.
So this does show that yes gyro can have issues in the stock ROM and that its not a hardware issue.
Does anyone have any other ideas.
Thanks.
i'd try BNH5 stock rom from sammobile (4.4.2)