Related
Hi Guys,
I am currently using a Cell Pro Rom and I find that my it keeps flipping to landscape too often when I have my phone in portrait.
I always have to give it a shake to fix itself and it does get a bit annoying.
Does anyone know how to fix this?
(I remember I may have (not certain) that I might have changed the Sensor registry when I first got it, but I am not certain, does anyone know the default measurements?)
Any ideas are welcomed.
Many thanks in advance!
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
kimtyson said:
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
Click to expand...
Click to collapse
I'm fearing the fact that I may have changed something in the registery as I got all excited the day i got the phone and went through the tweaks in the wiki.
I am not certain if I made any changes regarding the g sensor so I was wondering if anyone knows the defaults or if there is a .cab or ROM to flash to system restore.
Any clues?
Many thanks in advance
To me the g-sensor is a gimmick. I find it annoying and totally useless so I've turned mine off altogether. If I want the screen to rotate I push the keyboard out. I really don't see any use for it.
I did think the only use I had for it was the face down hands free thing but have since decided that I'd be quite happy to push a button for that. Hardly a hassle.
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
AidanBell said:
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
Click to expand...
Click to collapse
BY default I thought in all roms the proximity sensor would turn the screen off when its pressed against our heads so buttons wouldnt get pushed?
If that doesnt work you can always just push the power button... which I sort of do by default for some reason anyway. But... yeah there is a way so the screen turns off when its close to your face. Someone else will chime in with it I'm sure.
AidanBell said:
There is just one disadvantage I have found of not using HTC's TouchFlo UI: when holding the phone to my ear there is no protection from my (large!) ear's pressing the touchscreen and causing havoc opening programs, etc. Does anyone know of a reg tweak or a third-party app that addresses this, utilising the G-sensor and light sensor and protecting the screen during calls?
Click to expand...
Click to collapse
I'm using the Titanium version without TouchFlo or Sense, and my screen turns off.
This is absolutely a feature of all versions of the TP2, and works regardless of whether TF is used of not. Have you tried a hard reset? Also, does flipping the phone onto its face during a call activate the speaker phone? This involves the proximity sensor (along with G-Sensor), so it might give you a clue if your proximity sensor is somehow disabled, etc.
I dug around the registry for a second, and found the following values under:
HKLM\Software\HTC\Proximity
Name: ProximityDetectStatus
Value: 0
Base: Decimel
Name: ProximitySensorOn
Value: 0
Base: Decimel
Name: PSensorDebounceTime
Value: 300
Base: Decimel
Name: UnexpectedWakeup
Value: 0
Base: Decimel
Some of the values seem counterintuitive (I would think the "ProximitySensorOn" would be 1, not 0). But in any case, it might help to check your registry settings.
Many thanks for your response.
To answer your questions: I've recently upgraded to WM6.1, but didn't like that and so flashed 6.1 back again, and in fact re-flashed that again the other day, so the machine has been through quite a series of hard resets of late, however to the best of my knowledge I have never had a working during-calls-screen-protect other than the brief period during which I was trying out TouchFlo when I first had the phone.
Yes, flipping the phone to activate the speaker works flawlessly, I use it often.
In my registry under HKLM\Software\HTC\Proximity; "ProximityDetectStatus" "ProximitySensorOn" and "UnexpectedWakeup" are indeed all set at "0". However I do not have an "UnexpectedWakeup" setting. Could this be the problem? If so, I'm afraid I'm a bit of a novice with reg tweeking, so would you mind talking me through setting that value?
AidanBell said:
Many thanks for your response.
In my registry under HKLM\Software\HTC\Proximity; "ProximityDetectStatus" "ProximitySensorOn" and "UnexpectedWakeup" are indeed all set at "0". However I do not have an "UnexpectedWakeup" setting. Could this be the problem? If so, I'm afraid I'm a bit of a novice with reg tweeking, so would you mind talking me through setting that value?
Click to expand...
Click to collapse
If you are using Total Commander, go to the appropriate location on the registry, and the first entry is "Add value". Select that, then pick "DWORD", type the name of the value (UnexpectedWakeup). Hit OK, then enter 0 for the value and select OK again.
If you are using another editor besides Total Commander, the process should be the same. I use TC, so I only know that exact process.
Are you flashing to an "official" 6.1 ROM, or a cooked ROM?
Did you run Task29 before flashing the new ROM? This will wipe/format the memory completely, and will sometimes clear up random problems. Its recommended to do this before flashing a cooked ROM, but I don't know if using an "official" ROM is a problem with Task29 or not.
http://forum.xda-developers.com/showthread.php?t=649191
I'ver never heard of Task29!
However, firstly they were both "official" ROMs, from Vodafone, but secondly it seems the reg tweak has done the trick; the screen now Blanks when in call, as it should do. So all is well.
Many thanks indeed for that.
No problem. Happy to help.
But it was the "UnexpectedWakeup" entry that fixed it? That name/description doesn't really seem to fit. In fact, I can't even imagine what that description even refers to, lol!
AidanBell said:
I'ver never heard of Task29!
However, firstly they were both "official" ROMs, from Vodafone,
Click to expand...
Click to collapse
I don't know if there are any potential issues with using Task29 and official ROMs, I've only used it with cooked ROMs. Although, it seems like it would work and serve the exact same purpose. Task29 just guarantees that no fragments of the remaining ROM will interfere with the new ROM. It seems to help prevent random issues with cooked ROMs.
They say honesty is the best policy, so let me share with you what I have embarresingly discovered was actually the reason for my problem - especially remembering what this forum is for and that it might perhaps help anyone else with a similar issue:
I was told that a good way of testing the proximity sensor is to press your thumb against the loudspeaker during a call while looking at the screen. This did not work ... until I removed the plastic protection case! I have always had my phone protected by a two-piece plastic\silicon casing, and I've only now discovered that when this is on the phone the proximity sensor fails, but when removed it works perfectly! Thinking back that makes sense because when I first got the phone and was using TouchFlo the phone had no protective casing.
As it happens I've just bought an expensive cradle for the phone for my new car, which requires that I remove the plastic casing in order for it to fit, therefore the timing is good as it means I can now use the phone with a fully-working proximity sensor.
However, having dropped the phone only once in the year that I've owned it, don't you just know that the moment I start using it without the protective casing .... !
Hello there,
My Flo-Device keeps locking me out, resulting in a short black screen and throwing me back to the lockscreen. Based on the behaviour it seems that this is related to the sensor that is use for magnetic cases.
Unfortunately, I never used such a case, most threads I found are talking about cheap cases with a poor placing of the magnet itself - which does not help me out here.
Any hints on overriding that sensor by software or hardware? Any way of fixing the sensor or even a hint on the location on the Motherboard? I have read about an exposed module disabling it, but to configure the module it may be neccesary to be able to use the tablet in the first place. Currently it is still completely stock.
I appreciate your help or any reference to a solution that I may have overseen in my search. Thanks!
AeroplaneMode said:
Hello there,
My Flo-Device keeps locking me out, resulting in a short black screen and throwing me back to the lockscreen. Based on the behaviour it seems that this is related to the sensor that is use for magnetic cases.
Unfortunately, I never used such a case, most threads I found are talking about cheap cases with a poor placing of the magnet itself - which does not help me out here.
Any hints on overriding that sensor by software or hardware? Any way of fixing the sensor or even a hint on the location on the Motherboard? I have read about an exposed module disabling it, but to configure the module it may be neccesary to be able to use the tablet in the first place. Currently it is still completely stock.
I appreciate your help or any reference to a solution that I may have overseen in my search. Thanks!
Click to expand...
Click to collapse
Hall effect sensor's location is on the first attachment. I can assure you that there is no need to fix it directly because this and many other sensor problems are caused by the LCM connector. Disconnect the battery and just re-seat the LCM connector but be careful, watch this first https://www.youtube.com/watch?v=C9PwK9eGrCY
k23m said:
Disconnect the battery and just re-seat the LCM connector
Click to expand...
Click to collapse
Thanks for the fast reply and for pointing out the sensors' location on the PCB. Unfortunately, this did not solve the problem. Do you have any other ideas?
AeroplaneMode said:
Thanks for the fast reply and for pointing out the sensors' location on the PCB. Unfortunately, this did not solve the problem. Do you have any other ideas?
Click to expand...
Click to collapse
Please also re-seat the other end of LCM cable.
Check if a magnet placed over the sensor's position (top or bottom) has any impact.
Perhaps ROM builders know if something can be changed in /system/build.prop
Remove lock password - start ADB and do:
rm /data/system/locksettings.db
rm /data/system/*.key
Finally, we'll consider a hardware mod.
:good:
I already reseated both end of the ribbon cable to be sure - and again after the first unsuccessful test run. I never used a magnetic case on the device and there ar no other magnets near - my other Nexus 7 is fine though
What exactly does the locksettings.db do? I deleted It and rebooted, but no change in behaviour.
btw, as I am unable to properly use the touchscreen, I tried to enable usb debugging via an usb-otg cable and an attached mouse - which worked fine so far. It seems that there might be some interference or mechanical problem. Maybe the first thought with the hall sensor was wrong track I repaired a lot of devices over time, but (un)fortunately none of them showed that behaviour before, so I'm somewhat out of ideas in this case.
AeroplaneMode said:
What exactly does the locksettings.db do? I deleted It and rebooted, but no change in behaviour.
....
I repaired a lot of devices over time, but (un)fortunately none of them showed that behaviour before, so I'm somewhat out of ideas in this case.
Click to expand...
Click to collapse
It removes the lock password and makes it go into LOCKSCREEN-NONE mode, but you have to also remove all files with the ".key" extension from the folder.
Since you repair such devices, then measure voltage on the output pin of the sensor, and measure it again with a magnet over it.
Good idea. Without the magnet I get 2.98 V and with the magnet 0.001 V between GND and out. So I guess the sensor itself may not be the problem? As I recognized that it might be a mechanical problem, I got a friend to use the touchscreen and measured output at the sensor again, it seems to work as intended.
As the lockscreen does not have any further protection set up after a factory reset, I guess this could be the reason that I did not find any *.key files in that directory? So currently it is just 'swipe to unlock'.
Problem with the lockseetings file is: The device is all stock, locked and has no root - and to get a bit more weird, is not recognized when in recovery. My other Nexus 7 with twrp already on it is recognized instantly. I may have to fix that first, as in a weak moment I may have overseen the "access denied" while trying to delete that file and already typing the nex command. My bad - it was already late.
Honestly, I wonder what the problem really is and really appreaciate your help so far.
AeroplaneMode said:
Good idea. Without the magnet I get 2.98 V and with the magnet 0.001 V between GND and out.
.....
As the lockscreen does not have any further protection set up after a factory reset, I guess this could be the reason that I did not find any *.key files in that directory? So currently it is just 'swipe to unlock'.
.........
Problem with the lockseetings file is: The device is all stock, locked and has no root - and to get a bit more weird, is not recognized when in recovery.
Click to expand...
Click to collapse
The sensor is OK indeed.
As you did factory reset, there is no issue of user data loss anymore, so just unlock it and do factory flash https://developers.google.com/android/images
This should fix the recovery recognition problem too.
Yeah, so I unlocked it, reflashed it with the stock rom, installed twrp and su...and finally got to delete the mentioned files. But still - the issue continues to exist. Also, I see no difference after deleting the files. Does something else prevent that no locksreen-mode?
Do you have any more ideas? I could wildly start changing parts, but unfortunately the device isnt worth that much anymore :-/ As mentioned, using the device with the Mouse hooked up via otg, the screen behaves normal.
AeroplaneMode said:
the issue continues to exist. Also, I see no difference after deleting the files. Does something else prevent that no locksreen-mode?
....
Do you have any more ideas?
Click to expand...
Click to collapse
No worries, we'll fix it, but it seems that my opening statement "this and many other sensor problems are caused by the LCM connector" still holds true. On the schematic, R150 and R151 are presumably located next to the sensor on the daughterboard, so if LCM cable connection to main mobo is open, the CPU will constantly sense 0V level, right? And as you measured earlier, 0V means that magnetic flux is detected. Now, about the ribbon cable... you did re-seat it, but this thing is awful and tends to fail repeatedly because of contact oxidation and weak connector lock pressure. Two solutions:
spray with https://www.amazon.com/CRC-5103-Quick-Electronic-Cleaner/dp/B000BXOGNI/
apply a thick tape/spacer over the lock so N7's back cover will add extra pressure on it
Finally, here is a brute-force workaround fix, go: settings - system profiles - default - lock screen - disable :highfive:
I'll test the points you mentioned.
I have to get a can of cleaning spray in the workshop, as I only have other fluids here which leave a oily coating. Or Brake Cleaner Fluid Thanks so far, I'll keep you updated.
Disabling the Lockscreen still gives me blackouts but okay, i dont have to swipe anymore - that will do for the moment. I haven't had similar problems in a while, so I tend to forget some points as repairing phones from time to time is only some sort of occupational therapy for me besides my other work ^^
k23m said:
[*]spray with https://www.amazon.com/CRC-5103-Quick-Electronic-Cleaner/dp/B000BXOGNI/
[*]apply a thick tape/spacer over the lock so N7's back cover will add extra pressure on it
Click to expand...
Click to collapse
I was finally able to continue here. I cleaned the connection and applied some tape to thicken up the spacers. Still, I am not able to resolve the problem. I also tried to manually apple more pressure on the back, still not getting better unfortunately.
AeroplaneMode said:
I was finally able to continue here. I cleaned the connection and applied some tape to thicken up the spacers. Still, I am not able to resolve the problem. I also tried to manually apple more pressure on the back, still not getting better unfortunately.
Click to expand...
Click to collapse
I know you're not happy about it but this is the best N7 hardware issue to resolve we've had so far this year
I opened up my N7 to check the sensor's connection to main PCB - it goes to LCM pin #41 - note the attached pictures. Disconnect the battery and use an ohmmeter to measure the two points - I get around 8 oHm. If you measure open circuit, then look for broken or corroded track somewhere along the way. If you measure proper connection, then the problem is on the motherboard and there is nothing else we can do - case closed unfortunately.
/EDIT
Here is a software workaround:
install ElementalX kernel
during installation select the "Disable magnetic cover on/off" option
:victory:
k23m said:
I get around 8 oHm.
Click to expand...
Click to collapse
I get 3 Ohms, so I flashed the suggested Kernel. It seems to solve the problem, won't get any better I guess. Thanks for your support!
k23m said:
I know you're not happy about it but this is the best N7 hardware issue to resolve we've had so far this year
Click to expand...
Click to collapse
Now is that a good thing? :silly:
I just got the note 5 Global edition and have a few questions:
-I noticed I can't see the screen while wearing my polarized sunglasses while in portrait, reading online it seems people fixed this problem by using a screen protector. Has anyone used the nillkin glass screen protector? Did this fix the polarization issue? Or do I need to use a plastic screen protector?
-Without rooting (still waiting for my unlock code), can I adb remove the default dialer and replace it with the google patched one with no issues?
Edit: I installed a patched google dialer version 24 off xda and set it as a default dialer with every permission, notification setting enabled. I have 2 sim cards in my phone, I changed the default sim for calls to 1 of them. But when placing a call it still asks which sim to use. I didn't have this problem with my rooted axon 7 using google dialer.
Thanks!
zolo111 said:
I just got the note 5 Global edition and have a few questions:
-I noticed I can't see the screen while wearing my polarized sunglasses while in portrait, reading online it seems people fixed this problem by using a screen protector. Has anyone used the nillkin glass screen protector? Did this fix the polarization issue? Or do I need to use a plastic screen protector?
-Without rooting (still waiting for my unlock code), can I adb remove the default dialer and replace it with the google patched one with no issues?
Thanks!
Click to expand...
Click to collapse
-For the first issue: my best guess is that the orientation of the polarization filter is wrong within the display assembly itself, but how did the manufacturer not realize that, I don't understand. You can just slightly tilt the phone left or right and you'll be able to see without problems. As for the glass protectors, mine doesn't help, though there are claims that some protectors do help, don't know about Nillkin. Chances are that glass would help rather than plastic, but you can try.
-You would need unlocked bootloader for ADB commands, so that would be a no.
Cirra92 said:
-For the first issue: my best guess is that the orientation of the polarization filter is wrong within the display assembly itself, but how did the manufacturer not realize that, I don't understand. You can just slightly tilt the phone left or right and you'll be able to see without problems. As for the glass protectors, mine doesn't help, though there are claims that some protectors do help, don't know about Nillkin. Chances are that glass would help rather than plastic, but you can try.
-You would need unlocked bootloader for ADB commands, so that would be a no.
Click to expand...
Click to collapse
We don't need unlocked bootloader to debloat MIUI apps using adb commands
Yeah, I managed to remove a bunch of stock apps with no issue (mi browser, feedback, mi notes..etc). I didn't remove the default dialer though, but set google's dialer as default. But why does it keep on asking which sim card to use for every call I try to make, even though I set 1 sim card for calls in the settings?
As for the polarization issue, I guess I'll try different screen protectors and see which works. I hope other people can post their experience.
SunilSuni said:
We don't need unlocked bootloader to debloat MIUI apps using adb commands
Click to expand...
Click to collapse
Yep, my bad, I mixed up that withediting build.prop file, don't know why, it was late when I replied
zolo111 said:
Yeah, I managed to remove a bunch of stock apps with no issue (mi browser, feedback, mi notes..etc). I didn't remove the default dialer though, but set google's dialer as default. But why does it keep on asking which sim card to use for every call I try to make, even though I set 1 sim card for calls in the settings?
As for the polarization issue, I guess I'll try different screen protectors and see which works. I hope other people can post their experience.
Click to expand...
Click to collapse
My guess would be that Google dialer may need to be system app, or may not function properly without dialer framework, not sure since I'm using one sim only.
Unfortunately this !!ANCIENT!! Samsung bug appears also on A72 now ..... Does it work at all on your A72? Any ideas per the issue?
Lenux7066 said:
Unfortunately this !!ANCIENT!! Samsung bug appears also on A72 now ..... Does it work at all on your A72? Any ideas per the issue?
Click to expand...
Click to collapse
Do you mean the setting in display - accidental touch protection?
This will only work when it's very dark ... like in a pocket.
Best to use a secure unlock method such as password, pin or biometric.
I also experience this issue. And actually an that specific scenario. Wvery time I put my phone in my pocket. It turns on and the first thing that press is the widgets in the lockscreen. I notice when my leg is really hot. I gotta say it's annoying