[Q] Note 2 loses GPS at screen off - Galaxy Note II Q&A, Help & Troubleshooting

Howdy!
I'm using a Samsung Verizon Note 2 SCH-I605, rooted with Adams CASUAL tool (you can read all about it here: http://forum.xda-developers.com/showthread.php?t=2272066)
I'm still running the stock rom, I deleted the Verizon Bloatware crap, and now i'm having a repeat issue:
When the screen goes off, the GPS fix is lost. The only way i've found to bring it back is to turn it off, and turn it back on.
I've been using GPS toolbox (https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2&hl=en) to verify the GPS fix.
I think the next step is to unroot, run factory, and make one change at a time until I find the trouble maker, but I wanted to get your thoughts, opinions, or experience about or with this issue.

Related

Compass,magnetometer doesn't work!

Hi all! I had my Nexus since New Year and I'm so pleased with it. The last 2 weeks have I just noticed that my compass doesn't work anymore. I have checked several calibration apps but nothing works(twisting it around it's axis etc) . I then tried "advanced tools" application. Here could I see that my phone got zero signals from the compass and the magnetometer! I have switched from stock to m5 just to see if it was software related but the problem is the same. It is like the sensors is out... So my question to you all: Is it any way (through root for example) that I can force reset the sensors or is maybe service next?
Skickat från min Galaxy Nexus via Tapatalk 2
Did you flash any custom ROMs at any point?
I got a fresh Sprint Nexus. Compass worked fine. Flashed some custom ROMs, and compass didn't work with any of them. Next step recommended by CM9 folks is to revert to full stock to see if it works again to troubleshoot, but I won't have time for a while to do this.
As noted elsewhere in other posts, compass just doesn't work. It's not just N/S being reversed, it just goes haywire with any tilting, etc. Calibrating doesn't work from Compass or GPS Status.
That's the thing. I was on stock when I noticed the problem, that was why I switched to M5. But the compass is totally still for me. It doesn't move at all. It's totally non functional..
Skickat från min Galaxy Nexus via Tapatalk 2
Try to calibrate the compass. I am on AOKP and compass is also not working proberly. After calibration it does. Here is how to do it (I'm not a native speaker, try to explain it):
Start an app which is activating and using the compass. Stand free and hold the Nexus parallel to the floor facing the screen to the ceiling. Draw an 8 several times with the phone keep this orientation. Then, hold the phone upright to the floor facing the screen to your face and draw an 8 serveral times, again.
Salem24 said:
Try to calibrate the compass. I am on AOKP and compass is also not working proberly. After calibration it does. Here is how to do it (I'm not a native speaker, try to explain it):
Start an app which is activating and using the compass. Stand free and hold the Nexus parallel to the floor facing the screen to the ceiling. Draw an 8 several times with the phone keep this orientation. Then, hold the phone upright to the floor facing the screen to your face and draw an 8 serveral times, again.
Click to expand...
Click to collapse
Did exactly that with Compass app and GPS Status. Neither works.
Anyone have any progress with fixing this?
This is posted in the Sprint Nexus CM9 thread, might provide some information. Same compass problems happened with other CM9-based ROMs I've tried in the past.
I popped into the [CM9] IRC channel a little while ago and talked about how the compass was broken. It was suggested that I do a complete flash back to stock and report back. Trying to document as best as I can:
1. Complete flash back to stock under "[ACS] Return to stock" thread in this forum, used the first big link for FC12 Stock .tar (md5: 638d9b052b45396be345727ec0eedd64), which curiously is linked to "http://www.shabbypenguin.com/ACS/devices/Samsung/Sprint/GNexus/Stock/FC12/code_i9250xxsph-l700fd01.tar" and not *fd12.tar, like the mirror links to.
2. First reboot, downloaded Catch.com's Compass, compass works.
3. Baseband version lists as L700.05 V.FD01 / L700.FD02. I had previously flashed "toroplus_full_radios-FD02" a while ago.
4. Used Galaxy Nexus ToolKit v6.1, did option 7 for "all in one," though bootloader was already unlocked. Powered off, powered on, compass still works.
5. Copied over backed up zips, etc, flashed "toroplus_full_radios-FD02," rebooted. Compass still works. For kicks, updated to latest Google Maps, and Compass still works, GPS locks, location is correct. Baseband version lists L700.05 V.FD02 / L700.FD02.
6. Wiped system/cache/Dalvik & did factory reset. Flashed latest CM9 nightly (20120509-NIGHTLY-toroplus), GApps (20120429-signed), rebooted. AAAAND compass is broken again, as before.
Hope this gives you guys some information for a fix.

Root or stay stock?

I still haven't rooted my note 2. I want to root and get custom roms but scared the roms might not have good battery like stock. I'm not sure what's you guys opinion?
Sent from my SGH-T889V using xda app-developers app
Everything gets better with custom roms
Sent from my SGH-T889 using xda app-developers app
Stock.
Sent from my SGH-T889 using Tapatalk 2
I have rooted every Android I ever owned including ny Note 2... This is the only phone I have unrooted and went back to fully stock. I am very happy with the way this phone runs stock.
Sent from my SGH-T889 using xda premium
I absolutely had in my mind I wasn't going to root etc. but im running the latest jedi rom and it is phenomenal!
Sent from my SGH-T889 using xda app-developers app
There are some cool features tied in with touch wizard specific to our pen capability. If you go custom you may lose that. So I would look more at rooting like such. Do I want root to bypass tethering lockdown from the vendor or to make backups with Titainium? Do I really need to overclock or undervolt? Do a new ROM's features negate the potential loss of pen related features
Sent from my GT-N7105
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
zellroot said:
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
Click to expand...
Click to collapse
I was running stock rooted since I got my phone late last December. But today I finally decided to run a custom rom and jedi 10 was it. Flashed with no problems and do not see the problem you have. The rom is really nice. Here are some features I would suggest rooting for:
1. Free wifi tethering (it's a must for me since T-mobile charges $15 for me to use data that I'm already paying for).
2. Wifi calling (good option to have in case I do not have signals) - the jedi 10 rom offers this.
3. Multi-windown (any app) - a cool feature. I don't think I will use it much though. But it's good to use to show off.
4. Samsung keyboard with auto-correct. I wanted to keep the samsung keyboard so that I can use the s-pen sometimes. But the jedi rom has the auto-keyboard switcher embedded.
??????
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
SAMOANBK47 said:
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
Click to expand...
Click to collapse
Before you do anything else, search "nandroid" learn all about it, and make one.
Sent from my SGH-T889 using xda premium
I was stock until about 3 days ago. I moved into the Jedi ROM. I used CWM, the non-touch version. I don't know if I'm old school or worried about a non responsive screen but eh.
Originally I'd just thought to stay stock and not rooted so I could get OTA'S. Though with a ROM, I'm already miles ahead of the game.
As another person stated, using the tethering has really been good for me. I'm paying $70 a month, $15 more for the hot spot would of been ridiculously overkill.
Also, I've never seen or witnessed a phone become so buttery smooth and perform so well. I'm happy. ^_^
Just make sure you do back ups through TiBu and do nandroids.
Sent from my SGH-T889 using Xparent Green Tapatalk 2
I rooted, went to Jedi ROM, but had issues, like screen tearing, slow response (probably aggressive underclocking) and some other weirdness. Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Meanee said:
...Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Click to expand...
Click to collapse
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Fyi...noting what I said before, I am currently running one of Tesh's rooted stock ROMs for the international version. I can run backups, do tethering (no carrier lockdown for international), and run another kernel if I wish. It also allows me to use some of the Exposed installer tweaks to keep the Note2 touchwiz benefits and still use things like per app resultions and all apps in multiwindow.
Sent from my GT-N7105
dwitherell said:
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Click to expand...
Click to collapse
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Meanee said:
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Click to expand...
Click to collapse
Hmm... my thoughts:
- That may have just been wonkiness in the CNN app - not sure if anything I did could impact something in the way you described (but of course I could be wrong).
- Yeah that is way slow - and uncharacteristic from my experiences at least
- That plus the music issue makes me wonder - are you just using the stock kernel? If so you can't do much in the way of clock rate tweaking, but I also find it curious as I've heard little in the way of issues regarding the stock kernel.
- Did you do a full data wipe before installing?
Regardless - I am sorry to hear about the poor outcome - feel free to PM me if you want any suggestions/help troubleshooting. I'm not the best at it (especially remotely), but I'll try
Sorry for the off-topic stuff OP!
The question doesn't make sense.
Rooting just means you unlock the root account on the phone to have superuser access. This is required by some useful apps (ProxyDroid, Paragon NTFS & HFS+ which lets you mount any USB stick or hard drive using an OTG cable, backup programs...). You can very well keep the stock firmware and just root it, which is what I ended up doing on the Note II.
On my previous Galaxy S2 CM10 was working like a champ, so I figured I would try it on the Note II... I think at this point it's a total disaster and completely unusable, just not ready for prime time. Bluetooth is completely broken, the camera doesn't work, the video driver has problems, and most of all you lose a lot of the cool things you get with the stock firmware (multi-windows, stylus-specific features, etc...). Good enough if you're contributing to the ROM development and testing for bugs and missing features, but painfully not ready for prime time. The big problem is that you just don't know what feature will break next and will let you down right when you need it.
So for me, it's stock until CM10.1 goes RC. But of course I rooted it because I want to be able to use some apps that require rooting.
Note that some Samsung apps (Readers Hub) detect SuperSU and refuse to run. Uninstall SuperSU and use Superuser instead, and use Voodoo OTA Rootkeeper to temporarily unroot the phone if you need to use them.
Rooted on Stock Rom is the way to go.
I stay on stock ROM for Wi-Fi calling, but I had it rooted in order to transfer application data.
Backup your efs as well, because there has been several people that have lost their imei.

Call&Note Recorder disables when screen is turned off

Hey guys, im kinda new here, i've lurked and gotten help but this is my first post.
I was using Call&Note Recorder for a few days, everything worked super well was recording everything and all that, but last night i noticed that the icon wasn't in the notification bar up the top. So i went into it, reactivated it, but everytime the screen goes off, it disables it again, whether its from locking, or putting it up to my ear.
This (of course) is really annoying, i don't know if anything else is broken as this is just the start, but i don't know what i did in the last few days that i could of broken it. I did install Xposed framework and Keepchat, which didn't seem to work for me, so i've since uninstalled it. Besides that i can't think for the life of me what could be causing it.
So i am hoping someone here knows, and might be able to help without having to restore it.
Thanks in advance. Scott.
EDIT: ok it happens with Dropsync as well, if i start a sync and lock the phone, it shuts it compleatly down. I really need help
EDIT 2: Was unable to get into recovery either, the Galaxy Note II logo would come up and then fritz out and reset, and just keep doing that over and over. So currently re-installing stock firmware with odin, in the hopes that i fix it.
EDIT 3: When i flash the stock firmware, everything works as it should, if i reroot it, the same problems arise. Things turn off when locked and no able to enter recovery. I really hope someone has an answer for this, as its driving me insane working it out.
Is there ways to check what i've installed root wise and uninstall it?

New Note 3 very glitchy ... is this common?

Hey guys. I moved up from a Verizon Note 2 to a T-Mobile Note 3 two weeks ago (and switched carriers obviously).
Since then, it has happened that the phone gets stuck and then reboots.
Three times it's happened while scrolling in the 9Gag app, once while in the Play Store and once as I was unlocking the phone using a pattern an e-mail came in and the vibration got stuck for a while and then rebooted.
I've also noticed that if I have WiFi on, Skype logs in fine, if I leave the house so I go on 4G and then come back to WiFi, Skype refuses to see a connection unless I turn off WiFi or reboot the phone.
Then yesterday the entire phone was in landscape mode even though I had auto-rotate enabled, and whether I turned it off and back on, it stayed on landscape mode until I rebooted the phone.
My wife also has a T-Mobile Note 3, bought at the same time. For her it's rebooted only once so far while using Google Maps.
I've had S3, Sprint Note 2, Verizon Note 2, and my wife has had S3 and S4. Now we both got these Note 3s and man, this is way too glitchy. On the Note 2 I went over 2 months once without rebooting the phone. This one has rebooted itself 5-6 times in 2 weeks!
We're updated to KitKat 4.4.2 (OTA) and not rooted or modified in any way (yet). So I'm wondering if it's KitKat that is glitchy, since our phones before weren't on KitKat, or the Note 3s in general, or just my specific Note 3.
Would love any info on this. Thanks.
I would do a master reset. Worst case Odin stock rom. Avoid send in for refurbished one
Def don't root yet. Try and get phone stable first.
TWEAKED N3
If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
EDIT: if you don't mind me doing the noob thing and just asking, what's the easiest way to get root? I don't particularly care about a customized rom, but definitely want system access to get rid of all this bloat and install my customized video ringtone program.
Max_Pain said:
If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
Click to expand...
Click to collapse
It not harder it more steps and Odin is best. But if you have hardware issues on stock u need to know before root
TWEAKED N3
Yeah, doing it now. Going to go stock but rooted so I can have some control. Maybe later on i'll flash a custom rom when I have time to go through them and see which one suits my style.
Thanks.
I'd suggest doing a factory reset b4 anything, then if that dose not work, use odin and flash kit kat... then if ur issue persist, maybe contact samsung.
Sent from my SM-N900T using XDA Premium 4 mobile app
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Also one u have root, go to the play store and check out greenify. I swear by it. C:
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
Hibernating battery hogging apps and their associated services when they aren't being used.
Sent from my SM-N900T using Tapatalk
Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
I be honest I don't use it and this kk really doesn't drain the battery like job did stock
TWEAKED N3
I haven't noticed any sort of glitches since I've had my N3. Even after putting the jedi ROM on it seems fine. As far as the battery goes, I know there are alot of complaints that kk has killed alot of the life out of it. I haven't noticed a difference in battery life either. It holds a charge all day and some. And greenify is to stop or freeze certain apps that run constantly in the background that could drain the battery. I personally didn't really like the app nor did I need it.
Sent from my SM-N900T using Tapatalk
Well, I went on a stock deodexed rom and got on lean kernel for a while... but it's still doing the stuck-and-reboot thing. It's always related to the touch screen, so i'm either scrolling or clicking to open an app or settings within an app. The phone gets momentarily stuck, then full reboot.
How long do I have to get it exchanged in store? I wonder if i'm within that time frame. It's definitely not normal and getting very annoying.
If i'm outside the time to get exchanged in store, what's my next best option?
I have to say that this experience with the Note III has been nothing short of disappointing and nothing like the two Note IIs I had before (different carriers for each, neither broke or gave any problems).
Here's an update for anyone who finds this and is in the same boat.
I had two issues: 1) the power button became so recessed that it's a hassle to turn on/off the screen, 2) the phone kept turning on and off, by the end almost constantly, without any obvious pattern beyond it getting stuck after me touching the screen (i.e. never just up and turned off while being idle).
Because of the recessed power button, T-Mobile shipped me a replacement phone. Should arrive tomorrow.
I still tried troubleshooting the rebooting issue. I think it came down to one or a couple of the following:
1 - Go Weather EX
2 - Freeza's CRT mod
3 - flashable 1% battery mod
4 - bootanimation.zip support flashable script
5 - something in the Deodexed version of the stock KitKat rom
In prepping to take the phone to T-Mobile, I did the return to stock thing with Odin, putting back stock kitkat odex non-rooted rom. The entire afternoon I got not a single reboot. Since I came back home with the phone, I restored a backup I had made before doing the Odin stuff. Back to rebooting.
So I thought, let's go back to the stock experience like I had earlier, and restore my apps through the play store and manually hunt it down.
Now i'm running the stock odexed kitkat rom, rooted, with lean kernel, with a whole bunch of stock apps frozen, and virtually all my apps and not a problem. I avoided 2-4 since those mess with the framework and I thought it could have something to do with it. I removed Go Weather EX because I experienced a reboot once while setting it up as a live wallpaper.
When the new phone arrives tomorrow I'll try to duplicate my current setup and hopefully won't have any more rebooting issues. I hope this helps anyone experiencing the same thing. I know it's kinda convoluted and not very concise, but then again this experience has been nothing short of annoying and confusing.

Can't seem to get a GPS lock on any 5.1 rom

Ever since the transition from kk to lp, I've been struck on my GPS never locking on properly. Even tho the rom says it works, it hasn't for me. What have any of my other brothers and sisters with a note 2 done to fix this problem?
People read this and can't seem to respond. Hmmmm
Great community
Same problem here... GPS dead even after going back to 4.4. Did you fix this?
note2usr said:
Same problem here... GPS dead even after going back to 4.4. Did you fix this?
Click to expand...
Click to collapse
same thing here, GPS won't lock, I even unrooted and went back to stock and it's still not working for me after installing custom roms.
tenacres said:
same thing here, GPS won't lock, I even unrooted and went back to stock and it's still not working for me after installing custom roms.
Click to expand...
Click to collapse
It actually fixed itself for me. I have no idea how this happened but after ca. 2 weeks without GPS it started working.
It's not working reliably, though: I used to be able to get a fix every time i turned on my Note, now sometimes I don't get fix for hours. On other times, the fix happens immediately.
For me, i find a this way helps, not sure why it suddenly become like that :
- reboot phone
- after rebooted, turn off location first
-run "gps test" app with location off
-turn on location and let gps test do is thing to get 3d fix
-once you can get 3d fix on location, exit the apps and you can start using Google map, Waze or any by other gps apps
-as long as you dun turn off location after this, the GPS lock should work
-repeat step 1 if gps lock is not working again
Hope this helps, it's not a permanent fix... hope someone can come up with a permanent one.

Categories

Resources