Related
Dear all,
i have a Dell Streak 5, with following specs:
Android Version: 2.2.2
Kernel Version: 2.6.32.9-perf
Build Nr: 15609
The issues are:
- If i use the phone on my pocket with screen to my leg, when i need to unlock screen, i usualy can't, its kind of crashed...
- If i have the wireless ON, and go out from home, usually phone crashes , and when i go to use it, i see there was a reset. Seems that this wireless is kind of instable and make mobile phone crash.
I would like to upgrade something to try to solve this small issues, can anybody help me?
Thank you
Tiago
I forgot:
Baseband Version: GAUSB1A135100-EU
thanks.
I don't know what to tell you as far as wifi crashing your phone. That's never happened to me. As far as the other issue, seems pretty common. I think the recommended "fix" is to not carry it with screen facing your leg. I'm sure that's not what you want to hear....but its the best I got.
i can't explain why you wifi makes your phone crash, but for the impossibility to unlock the screen. i had the same problem, and somebody told me the problem was the heat of the leg that makes the screen tilt. so i bought an otterbox case with a belt clip, so with the screen untouched it works perfectly.
for the screen against leg issue, I just toggle the power off then on and it works.
yes, i agree to lordmorphous, don't face your screen to your leg..
just in case, you may try to calibrate it, or if the problem still, maybe you can re-flash to another latest stock rom.
I have never experienced the screen issues involved with facing the screen towards my leg, and I always put my Streak in my pocket with the screen facing my leg. I guess so far I've gotten lucky.
Strephon Alkhalikoi said:
I have never experienced the screen issues involved with facing the screen towards my leg, and I always put my Streak in my pocket with the screen facing my leg. I guess so far I've gotten lucky.
Click to expand...
Click to collapse
+1......never had screen issue
Guendaline said:
+1......never had screen issue
Click to expand...
Click to collapse
+1 same here..
I had got such issue that can't unlock the screen when I used the official ROM.
But there is not such problem when I use the Power Rom V1.1 now...
Masterzer0 said:
+1 same here..
Click to expand...
Click to collapse
+1 same here
briantamhk said:
I had got such issue that can't unlock the screen when I used the official ROM. But there is not such problem when I use the Power Rom V1.1 now...
Click to expand...
Click to collapse
The ROM makes no difference. I run 360 on my Streak.
I met a guy in a train station, and since there are not a lot ppl with such mob, i decided to ask. In fact, with screen faced outside, the issue finished. Strange..
Related with stock ROM, i think this is my next step: upgrade! the process dell.com.blablabla is always crashing, and sometimes i need to wait to use the phone. awww, not to say that i can't synch with my outlook
I am a bit disappointed with this phone/tab, i was expecting that it could work better.
Any tips on ROM? I am actually trying to use titanum backup to backup data, but it says again cannot root! How i root it?
Thanks again.
Tiago
Everything You Always Wanted To Know About The Streak But Were Too Busy Bricking It
That link there is your first step, for it explains how to root and how to do various other things. Now...I tend NOT to recommend using Titanium Backup since in my experience it screws up when restoring items. Your mileage may vary.
As to a ROM, stick with a stock ROM for now until you are comfortable with the rooting process. I have attempted to use GingerStreak but had a problem with the camera app so I had to go back. Flashing a ROM could fix your issues since a bad flash has been known to be source of the force closes.
Hi again,
finaly i tried a simple method: the gingerbreak, and rooted. Now that is rooted, i want try a diff Android version (from 2.2 to 2.3?).
Is there any recommendation?
Of course first i would like to backup all the data (already from the SDCard) but i am talking about the ContactList (i tried to use the simple: export, but onde again i got an error :/)
Any tips?
Thanks for all the help.
KR
Tiago
I've been having lots of little problems too.
My device randomnly decideds to restart time to time. There doesn't seem to be a pattern to it that I've worked out yet. But it's crashing right now and I have to soft reset it.
Another thing, if I have it in normal landscape mode but turn it on while holding it portrait mode or the screen isn't in the same orientation that it was before the screen turned off, Dell Stage often crashes.
SuperKeeper said:
I've been having lots of little problems too.
My device randomnly decideds to restart time to time. There doesn't seem to be a pattern to it that I've worked out yet. But it's crashing right now and I have to soft reset it.
Another thing, if I have it in normal landscape mode but turn it on while holding it portrait mode or the screen isn't in the same orientation that it was before the screen turned off, Dell Stage often crashes.
Click to expand...
Click to collapse
Exactly, mine restart very often too, but i think i know why. Try disable wireless before leaving your "home network"... in my case, it solves that crashings... only crash if dell stage crashes too... but most of times, its solved.
The only "bugs" i have are: camera button does not work, and when i turn screen on, the "unlock slide button" is ALWAYS in the portrait position.
I wonder, if this is solved with a new android version, or dell "libraries" update?
Thanks.
Tiago
for all those who think the problem does show up when u put it in the pocket facing your leg ..... i had the same view two weeks ago when suddenly i ran into this problem. i think best solution is calibrating the screen .....
zeeshan2341 said:
for all those who think the problem does show up when u put it in the pocket facing your leg ..... i had the same view two weeks ago when suddenly i ran into this problem. i think best solution is calibrating the screen .....
Click to expand...
Click to collapse
Calibrating the screen was what i've done when i could not unlock my mob phone for 1 week, i was desperate
After that, i solved all the screen issues using screen outside and not against leg.
Tiago
In the top left corner of my KF there seems to be a sensor. Anyone know what it is for? It doesn't seem to do anything when I cover it.
It is a light sensor that could be used to automatically adjust the screen backlight for example.
Yea but it doesn't seem to do that. I cover it and the screen brightness doesn't change. Is there a setting I am missing?
interesting - i think to remember there was a setting in settings->display called "auto brightness" in stock 6.2 and it was not activated by default - not shure but i think so
this setting seems to be gone in 6.2.1
found that:
http://forum.xda-developers.com/showthread.php?t=1351077
and
http://forum.xda-developers.com/showthread.php?t=1366894
and
http://www.amazon.com/forum/kindle?_encoding=UTF8&cdForum=Fx1D7SY3BVSESG&cdThread=Tx1A25EP3Z5BWB9
maybe i got mine with 6.0 ...
and here a picture of old times:
http://attachments.xda-developers.com/attachment.php?attachmentid=791845&d=1321998472
It should be a light sensor, but on my cm7 fire...it seems not functioning.
-Zeta- said:
It should be a light sensor, but on my cm7 fire...it seems not functioning.
Click to expand...
Click to collapse
It does not work currently on CM7, see post from whistlestop...
http://forum.xda-developers.com/showpost.php?p=21300591&postcount=820
I dont think Ive seen auto brightness work on any of the ICS ROMs or the MIUI port. Am I right about that? Might be kinda useful
nateware said:
I dont think Ive seen auto brightness work on any of the ICS ROMs or the MIUI port. Am I right about that? Might be kinda useful
Click to expand...
Click to collapse
See same post I listed above. It says that they haven't got the light sensor working in ICS either.
It worked originally in the Kindle Fire 6.0 release but was removed in the 6.1 update and has not been re-enabled in any version ROM that I know of.
Those that had the KF with 6.0 said it didn't work well which is why the most likely disabled it.
The Amazon "Basics" case covers up the sensor with the elastic straps. Maybe that's why they disabled it...
Thanks everyone, that explains it!
fallingcowdude said:
The Amazon "Basics" case covers up the sensor with the elastic straps. Maybe that's why they disabled it...
Click to expand...
Click to collapse
Doubtful. One the KF doesn't come with a case and many cases have the hole for it. Mine does. More likely, there is a hardware issue.
I also note that many phones which have the same thing work better by turning the auto off. Using auto uses more battery on my Dinc, so I just turn it off.
They removed it because it was like watching a bad monitor with a low flicking refresh rate.... it was sampling like 3-5 times a second and adjusting. I thought I was going to have a seizure until it updated
Sent from my Kindle Fire using xda premium
So that's what's driving me nuts with the auto on and off for my new Nexus and poetic cover. I don't really understand why I can't find a way to disable the feature entirely. I don't want to remove the magnet because it keeps the bluetooth keyboard in place. What I'd like to know is a way to stop screen from being turned on or off by magnet entirely. Is there a way to do it?
thanks.
kgptzac said:
So that's what's driving me nuts with the auto on and off for my new Nexus and poetic cover. I don't really understand why I can't find a way to disable the feature entirely. I don't want to remove the magnet because it keeps the bluetooth keyboard in place. What I'd like to know is a way to stop screen from being turned on or off by magnet entirely. Is there a way to do it?
thanks.
Click to expand...
Click to collapse
Hi,
I'm having the exact same problem too! i bought a generic case tho, same crap, diff pile...
Not sure why it would be an issue. It is a nice feature IMO.
Sent from a galaxy far away!
JesseMT4G said:
Not sure why it would be an issue. It is a nice feature IMO.
Sent from a galaxy far away!
Click to expand...
Click to collapse
Well I dislike this feature too (while I like my tablet case). People are different ...
Yup, true. However, it seems few care about doing it.
It must be a specific to tablet feature (i.e. only on/1 for tablet ROM). Therefore, searching your sys for potential autowake may get you further.
Otherwise, you could cut out or cover the magnet in your case.
Neither are ideal, but both are possible solutions.
Sent from my Nexus 7 using xda app-developers app
The driver for this switch is in the kernel source code at drivers/input/lid.c. By default, it only puts up one parameter, which is basically read-only. /sys/devices/platform/LID/lid_status will report you a 0 or 1 based on if the "lid" is closed or open. You can try your luck disabling this driver completely, or even adding in a parameter to enable/disable it at your liking. I haven't tried it myself, but I'd say commenting out the bulk of lid_interrupt_handler() may get you what you're after.
gianptune said:
The driver for this switch is in the kernel source code at drivers/input/lid.c. By default, it only puts up one parameter, which is basically read-only. /sys/devices/platform/LID/lid_status will report you a 0 or 1 based on if the "lid" is closed or open. You can try your luck disabling this driver completely, or even adding in a parameter to enable/disable it at your liking. I haven't tried it myself, but I'd say commenting out the bulk of lid_interrupt_handler() may get you what you're after.
Click to expand...
Click to collapse
Thanks, its great there is way to solve this. :good: Im way under experience level required to do this, but maybe a friend will know.
For anyone experiencing frozen/lag on Kitkat, especially after lockscreen, please check the memory and CPU consumption when the lag is happening (e.g. Watchdog Lite on Playstore).
Suspect :
[SystemUI memory leak]
In 4.4 Kitkat this SystemUI service is launched in the same package of S-View Cover services and Keyguard (Lockscreen) services.
This problem was known in 4.2.2 and fixed on 4.3 JB but seems resurrected on Kitkat.
Some components were not de-registered from memory after created and no longer being used especially by using lockscreen (and S-View cover) this object recreation seems to be overloading the memory and also eating CPU slice time.
Known Workaround
- Restart cellphone
- Restart SystemUI
- Refrain to use Lockscreen + SView cover together until further updates
Old Ref (applicable for 4.2.2 not Kitkat) :
http://forum.xda-developers.com/gala...i-4-2-t2178962
I managed to isolate the problem, it is S-View cover used with Lockscreen that caused this. Dont know i this is closely related to TouchWiz or not. I'm currently still investigating.
[Workaround]
Use S-View cover without Lockscreen .. or use Lockscreen without S-View cover.
Thanks for letting us know this my good man.
I have been suffering from the same symptoms and have been investigating this, but since i do not have root, it seems to be very hard to track this.
please let us know if you find any answers to this nlatifolia.
ckhurana said:
Thanks for letting us know this my good man.
I have been suffering from the same symptoms and have been investigating this, but since i do not have root, it seems to be very hard to track this.
please let us know if you find any answers to this nlatifolia.
Click to expand...
Click to collapse
For now, it is the Lockscreen that is suspected. Original Google Lockscreen is fine such on Nexus, on Samsung it has been modified to work together with S-View cover and to show Music Art.
Most symptoms are reproduceable if using S-View cover and Lockscreen at the same time though sometimes Lockscreen alone can cause this (apparently doing ****ty stuff in background on screen wake up).
To check ****ty stuff I use this : https://play.google.com/store/apps/details?id=com.zomut.watchdoglite
This happens to me also, i don't want to root the phone or downgrade it to 4.3 because it might trigger Knox and I already sent the phone back to them with an overheating problem, i don't want any more surprises from a very expensive phone that can't be covered by warranty.
I tried removing the password from the lockscreen and it's still having problems: i close the S view, push the power button and the screen stays off whilst the buttons light up. It's stupid cuz it's original Samsung software with original cover.....
Is there any way to downgrade without losing warranty or do you know if Samsung is thinking of pushing a fix?
I tried without success:
turning off all the sensors
turning off power saving
uninstalling a bunch of apps
I did not try factory reset yet, I'm afraid i'll kick the phone to pieces if i to a factory reset and nothing is changed, and i have to sent it to warranty again...
dumitrudan608 said:
This happens to me also, i don't want to root the phone or downgrade it to 4.3 because it might trigger Knox and I already sent the phone back to them with an overheating problem, i don't want any more surprises from a very expensive phone that can't be covered by warranty.
I tried removing the password from the lockscreen and it's still having problems: i close the S view, push the power button and the screen stays off whilst the buttons light up. It's stupid cuz it's original Samsung software with original cover.....
Is there any way to downgrade without losing warranty or do you know if Samsung is thinking of pushing a fix?
I tried without success:
turning off all the sensors
turning off power saving
uninstalling a bunch of apps
I did not try factory reset yet, I'm afraid i'll kick the phone to pieces if i to a factory reset and nothing is changed, and i have to sent it to warranty again...
Click to expand...
Click to collapse
I have the S View from Spigen (slim armor) After trying everything, I am negotiating a refund/or a cover replacement. Don't know why a stupid thing like the phone cover is now a big deal with Samsung.
I sure do hope that Samsung would release a fix for the issue though. Let's see.
I have tried 3rd party apps for this too... And Sipgen advised me to install them! Imagine!
does anybody know if this problem occurs also with the original Samsung Chip from the original Sview Cover?
because otherwise it might be also a problem with the chip from Spigen.
duttla said:
does anybody know if this problem occurs also with the original Samsung Chip from the original Sview Cover?
because otherwise it might be also a problem with the chip from Spigen.
Click to expand...
Click to collapse
Hi, I have an Original S Case bought from Orange Romania, with Samsung warranty and everything. The S-view function does not work with third party cases unless there is a specific software for it. Mine worked on 4.3 and on 4.4 with no added software, and i still have problems with the Screen not turning ON.
I did find a workaround however: turn of your lockscreen, any password, any swipe everything, and your screen will turn on with no delay. I had to remove my work email to get rig of the password....
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.
no Sview works with the spigen armor view case @ Android 4.4.2
but I have the same problem like Ckhurana
ckhurana said:
Hi
I had the issues of screen not getting switched off on cover close and vice versa.
I got the replacement chip from spigen. Installed it 3 days back. Now the cover runs fine for 2 to 3 times only and after that it gives up.
The s view is more or less unusable now. It only gets launched if I either restart the phone or reinstall the cover.
Moreover I got the issue of screen getting switched on by itself when locked and thus a massive battery drain.
My phone is not rooted and I need to check if the s_view process is getting some issues. Any way I can do that?
And also if I can check if the chip is the issue or the low power magnet on the front flap. Let me know if anyone can help please!
Many thanks
Ckhurana
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Dear all,
the only way i have been able to get rid of this issue was by removing exchange mail/calendar and pin lockscreen. My note 3 has now low level of security ( swipe) but i can enjoy my samsung sview and docking station as i had issues with that one too.
Quite disappointed from a top device such as the NOTE 3
dumitrudan608 said:
Hi, I have an Original S Case bought from Orange Romania, with Samsung warranty and everything. The S-view function does not work with third party cases unless there is a specific software for it. Mine worked on 4.3 and on 4.4 with no added software, and i still have problems with the Screen not turning ON.
I did find a workaround however: turn of your lockscreen, any password, any swipe everything, and your screen will turn on with no delay. I had to remove my work email to get rig of the password....
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.
Click to expand...
Click to collapse
dumitrudan608 said:
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.
Click to expand...
Click to collapse
Touchdown works with Exchange and PIN enforcement. The policy will make the app enforce the PIN rather than the entire phone.
I do not know much about its compatability with Office 365, but it works well with exchange address book/calendar/email functions.
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 03:24 PM ---------- Previous post was at 03:19 PM ----------
I use a pattern unlock and in the beginning it would occasionally freeze with my Original Samsung Charging S View cover after the Kitkat update. In my case, removing all security and reapplying the pattern unlock lockscreen worked for me and I no longer have freezes. I have not tried with PIN or password unlock lockscreens however. Your mileage may vary.
Sent from my SM-N9005 using XDA Premium 4 mobile app
ckhurana said:
Thanks for letting us know this my good man.
I have been suffering from the same symptoms and have been investigating this, but since i do not have root, it seems to be very hard to track this.
please let us know if you find any answers to this nlatifolia.
Click to expand...
Click to collapse
dumitrudan608 said:
This happens to me also, i don't want to root the phone or downgrade it to 4.3 because it might trigger Knox and I already sent the phone back to them with an overheating problem, i don't want any more surprises from a very expensive phone that can't be covered by warranty.
I tried removing the password from the lockscreen and it's still having problems: i close the S view, push the power button and the screen stays off whilst the buttons light up. It's stupid cuz it's original Samsung software with original cover.....
Is there any way to downgrade without losing warranty or do you know if Samsung is thinking of pushing a fix?
I tried without success:
turning off all the sensors
turning off power saving
uninstalling a bunch of apps
I did not try factory reset yet, I'm afraid i'll kick the phone to pieces if i to a factory reset and nothing is changed, and i have to sent it to warranty again...
Click to expand...
Click to collapse
duttla said:
does anybody know if this problem occurs also with the original Samsung Chip from the original Sview Cover?
because otherwise it might be also a problem with the chip from Spigen.
Click to expand...
Click to collapse
dumitrudan608 said:
Hi, I have an Original S Case bought from Orange Romania, with Samsung warranty and everything. The S-view function does not work with third party cases unless there is a specific software for it. Mine worked on 4.3 and on 4.4 with no added software, and i still have problems with the Screen not turning ON.
I did find a workaround however: turn of your lockscreen, any password, any swipe everything, and your screen will turn on with no delay. I had to remove my work email to get rig of the password....
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.
Click to expand...
Click to collapse
Labron said:
Dear all,
the only way i have been able to get rid of this issue was by removing exchange mail/calendar and pin lockscreen. My note 3 has now low level of security ( swipe) but i can enjoy my samsung sview and docking station as i had issues with that one too.
Quite disappointed from a top device such as the NOTE 3
Click to expand...
Click to collapse
I'm currently using original Samsung chip (removed from original case and put into Spigen SAV) and the problem persists.
After a bit of more tests, I can safely conclude that the problem occured if we use S-View cover together with any type of stock Lockscreen.
[Current Workaround]
Use S-View cover without Lockscreen .. or use Lockscreen without S-View cover.
Note :
I'm currently trying to hack into the SystemUI code but no promise here as even if that suceeded I'm afraid we have to root to install the patch.
I'm currently using the original Sview Cover with no lock screen and it works without any troubles.
The phone has Android 4.4.2 and ist not rooted.
duttla said:
I'm currently using the original Sview Cover with no lock screen and it works without any troubles.
The phone has Android 4.4.2 and ist not rooted.
Click to expand...
Click to collapse
Yes, and what do you do if you have work mail with exchange enforce security that makes you have a password...? seriously Samsung did this and nothing official about this? i cannot believe this..
nlatifolia said:
For anyone experiencing frozen/lag on Kitkat, especially after lockscreen, please check the memory and CPU consumption when the lag is happening (e.g. Watchdog Lite on Playstore).
Click to expand...
Click to collapse
Btw, how much can be called leak?
Mine floating around 73Mb - 155Mb across several days (usually about 1 week)...
I use stock PIN lockscreen + xposed maximize widget + S-View cover from you
And I experience no lag/freeze after lockscreen.
What I noticed: S-Planner not displaying any dismis/snooze like Alarm on S-View, I have to open the cover to dismis it.
But when I use S5 S-Planner, it displayed, but I dont want S5 version, it got no handwriting feature...
Crescendo Xenomorph said:
Btw, how much can be called leak?
Mine floating around 73Mb - 155Mb across several days (usually about 1 week)...
I use stock PIN lockscreen + xposed maximize widget + S-View cover from you
And I experience no lag/freeze after lockscreen.
What I noticed: S-Planner not displaying any dismis/snooze like Alarm on S-View, I have to open the cover to dismis it.
But when I use S5 S-Planner, it displayed, but I dont want S5 version, it got no handwriting feature...
Click to expand...
Click to collapse
Hehe u don't need use expose sview mod for that. Try use original S View stock app and see if that is the culprit.
Sent from my SM-N900 using Tapatalk
Thanks, Touchdown/no Pin workaround worked for me!
Hi all
I was having similar issues to dumitrudan608 in particular. Huge hang on the lockscreen of up to a minute and normally above 10 seconds on Note 3. We recently acquired 2 of these to be used as company phones and BOTH were experiencing this.
I tried wiping the cache, factory reset, no S view cover, S view cover and turning on and off all sorts of settings but none of this worked. I managed to pinpoint this down to the native e-mail app which had been configured to use Exchange. Similar to dumitrudan608 we were forced to use a PIN (which shouldn't really be an issue, it should just work!).
I also rooted both devices in order to use BetterBatteryStats (can't use without root on KitKat) and to try to determine which wakelocks were causing the device to freeze up. There wasn't a massive battery drain though so this doesn't seem to be the issue. Plus, one of the phone's had nlpwakelock as the most common process however for the other one it was AlarmManager so there was no consistency.
I've now just removed the exchange account from the e-mail app, changed the lockscreen PIN to a pattern & wiped the cache. I've then installed Touchdown thanks to the advice from monomer888 & set it up with the same PIN as was previously on the lockscreen. There is absolutely no lag whatsoever, the phone is now flying. I've yet to try on the other device however I will when I get the chance (unfortunately I believe it's been dropped into Samsung...) and report back here.
A note on Touchdown, so far so good, it does all we want it to so far, so seems to be a viable replacement.
Also, the S view cover is now being used and so I can assume that, at least for us, this was not the cause of our issue. I have read that Samsung have acknowledged that there is an issue surrounding 3rd party covers however due to a chip in the device.
The only issue with this workaround is that you need a pattern to unlock the phone and then a PIN to unlock the app which is a bit tedious.
This is really basic stuff that Samsung should be getting right though. I'll be unwilling to test if the issue is fixed in a future update as having this working is more important to us.
Thanks guys, hope this helps you!
Hi again
I have done the same process on the other Note 3 and am happy to confirm that the issue has also been fixed by the method I used above, so this definitely seems to confirm the problem we were having.
Dissapointing .. we need to contact support
I have Note 3 SMN-900 (kitkat 4.4.2) with original sview cover
this is very disappointing !
thanks for the workaround , which is fine, but a fix is essential to be able to use google deivce policy
How to file a ticket to Samsung support regarding this ?
AminoNote3 said:
I have Note 3 SMN-900 (kitkat 4.4.2) with original sview cover
this is very disappointing !
thanks for the workaround , which is fine, but a fix is essential to be able to use google deivce policy
How to file a ticket to Samsung support regarding this ?
Click to expand...
Click to collapse
Have the same problem with my samsung note 3 after upgrade to android 4.42. I m using cloud magic as exchange mail for my company email. Just log ticket to samsung support malaysia but they claim this issue is related to google android 4.42 which have bug. So all the problem they throw it to google as this is not related to their device. How can samsung so not responsible for this issue.
I am relatively new to this device, coming from Samsung. So different hardware, newer Android. Trying to work through everything. The phone is rooted and I have been making some mods including Xposed.
My latest problem is that the compass seems to be stuck pointing North (at least on some apps). This affects GPS Status and HereWeGo, both of which I have used for years now without problems. Interestingly, this does not seem to affect GPS Test app which I have also used for years.
I have seen a few posting elsewhere mentioning this same problem. Those were for Verizon models, if I recall. But even those posting said it happened before rooting, etc.
Anyone have any suggestions? Thanks!
Try this?:
Another method I've used is to lay the phone on a flat surface face up and rotate it slowly 3-5 times clockwise and counterclockwise. Then do the same with it face down (on a cloth to avoid scratching).
I've only had to do this when I noticed my magnetic sensor picking up a false reading (I use a sensor reading to launch a Tasker profile when it reaches a certain level).
Good luck.
pistacios said:
Try this?:
Another method I've used is to lay the phone on a flat surface face up and rotate it slowly 3-5 times clockwise and counterclockwise. Then do the same with it face down (on a cloth to avoid scratching).
I've only had to do this when I noticed my magnetic sensor picking up a false reading (I use a sensor reading to launch a Tasker profile when it reaches a certain level).
Good luck.
Click to expand...
Click to collapse
Sorry, should have mentioned that I did all the calibration stuff. It is as if the nav apps do not see there is a compass available. On my old phone, for example, Here Navigation shows a compass icon. On the LG V20 it does not. Cheers
whitedavidp said:
Sorry, should have mentioned that I did all the calibration stuff. It is as if the nav apps do not see there is a compass available. On my old phone, for example, Here Navigation shows a compass icon. On the LG V20 it does not. Cheers
Click to expand...
Click to collapse
I know this sounds stupidly simple and you have prolly already done it but there seems to be a bug in my H918 where sometimes my phone doesn't detect certain sensors like proximity and accelerometer hence no compass and screen won't turn off during a call also can't use phone in landscape since it can't detect when phone is sideways but basically the only solution I've found is to just reboot phone and it solves it. It does it very rarely but figured I'd suggest it just in case.
Also can't remember if you said in OP but does this happen without Xposed? Xposed had quite a few bugs still and it's suggested to remove entirely when troubleshooting issues.
KUSOsan said:
I know this sounds stupidly simple and you have prolly already done it but there seems to be a bug in my H918 where sometimes my phone doesn't detect certain sensors like proximity and accelerometer hence no compass and screen won't turn off during a call also can't use phone in landscape since it can't detect when phone is sideways but basically the only solution I've found is to just reboot phone and it solves it. It does it very rarely but figured I'd suggest it just in case.
Also can't remember if you said in OP but does this happen without Xposed? Xposed had quite a few bugs still and it's suggested to remove entirely when troubleshooting issues.
Click to expand...
Click to collapse
Hi and thanks. I am not sure of other sensors but if true, that makes things even worse. I do notice, however, that after several reboots, the compass is back and working again. Obviously, rebooting is NOT a solution for most folks. I am in the process of removing xposed to see if that has any impact. Cheers!
whitedavidp said:
Hi and thanks. I am not sure of other sensors but if true, that makes things even worse. I do notice, however, that after several reboots, the compass is back and working again. Obviously, rebooting is NOT a solution for most folks. I am in the process of removing xposed to see if that has any impact. Cheers!
Click to expand...
Click to collapse
When it happens test to see if you can rotate your phone into landscape mode. Mine rarely happens for me and it only happens upon rebooting. It won't just happen while the phone is on