GPS on 4.3 rom issue - T-Mobile Samsung Galaxy S 4

Not sure if its just a issue I am experiencing or does happen to to others. This issue only happen on 4.3 roms let it be cm Roms or gpe Roms. Also I have tried different developer Roms and same issue. The issue that I'm having is GPS randomly stops and locks and is more noticeable when in long trips. This has led me to revert back to any 4.2.2 ROM and all is well. Has anyone else had this issue? I've tried wiping and formating internal drive different restore recoveries such as clockwork mod and twrp and same issue. I feel I don't miss much from 4.2.2 and 4.3 and why I don't mind staying on 4.2.2 but just find it very odd.
Sent from my GT-I9505G using XDA Premium 4 mobile app

megareyes said:
Not sure if its just a issue I am experiencing or does habecause ppen to to others. This issue only happen on 4.3 roms let it be cm Roms or gpe Roms. Also I have tried different developer Roms and same issue. The issue that I'm having is GPS randomly stops and locks and is more noticeable when in long trips. This has led me to revert back to any 4.2.2 ROM and all is well. Has anyone else had this issue? I've tried wiping and formating internal drive different restore recoveries such as clockwork mod and twrp and same issue. I feel I don't miss much from 4.2.2 and 4.3 and why I don't mind staying on 4.2.2 but just find it very odd.
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes ive also expirenced this with 4.3 roms. I also reverted back to the 4.2.2 roms because navagation is important to me. So you are not alone in this experience. Im not sure why this problem occurs however I can confirm it is happening. I do wish I had a resolution to this issue as ive tried many things with out success. Hopefully someone can resolve this issue in the future. hope this helps. Best wishes.

realsis said:
Yes ive also expirenced this with 4.3 roms. I also reverted back to the 4.2.2 roms because navagation is important to me. So you are not alone in this experience. Im not sure why this problem occurs however I can confirm it is happening. I do wish I had a resolution to this issue as ive tried many things with out success. Hopefully someone can resolve this issue in the future. hope this helps. Best wishes.
Click to expand...
Click to collapse
Sorry for the necro, but I've been having this problem for a long time as well and cannot figure it out whatsoever.

realsis said:
Yes ive also expirenced this with 4.3 roms. I also reverted back to the 4.2.2 roms because navagation is important to me. So you are not alone in this experience. Im not sure why this problem occurs however I can confirm it is happening. I do wish I had a resolution to this issue as ive tried many things with out success. Hopefully someone can resolve this issue in the future. hope this helps. Best wishes.
Click to expand...
Click to collapse
I've had this problem on a 4.2.2 ROM as well... after flashing a 4.3 ROM it went away, but I'm on another 4.2.2 ROM now and the GPS is fine. I'm not sure it's related to 4.2.2/4.3 in my experience.

Mralexander006 said:
I've had this problem on a 4.2.2 ROM as well... after flashing a 4.3 ROM it went away, but I'm on another 4.2.2 ROM now and the GPS is fine. I'm not sure it's related to 4.2.2/4.3 in my experience.
Click to expand...
Click to collapse
Yea, I've now noticed it happens on both. Quite sparatic. I have no idea what to do about this. Thinking about just getting a new one from tmobile.

Related

Having Wifi problems

Hey guys, I'm just wondering if anyone else has had problems with their wifi not wanting to turn on,
I've switched roms, I've went back to factory. Everything i can think of. So If anyone has some experience with this,
Or ANY clue whats wrong, Please let me know.
Thanks!
Why don't you tell us exactly what did you did when it stopped working
Nothing really, Just normal use on Stock when poof it didnt work anymore. I rooted and used custom kernels/roms to
try and get it back working. But it hasnt worked yet. I think It may have been after an OTA update from ATT. But that shouldnt linger after a full wipe, would it?
reboot your modem and router at home..
That Didnt work, It doesnt work on any wifi network. The phones wifi will not enable.
what does your baseband say?
Baseband is I317UCAMC3
ok, that is ok...what rom and kernel are you on?
Rootbox's 4.2.2 Rom with its default kernel. But this issue started happening on Stock, non rooted. And has persisted all the way through 3 different roms so far.
Ok, this is supposed to be only for the gt-n7100 version but it sounds real familiar and if it's a bug in jelly bean it could be your problem. Either way it shouldn't hurt to try.
http://galaxynote2root.com/galaxy-n...o-fix-wifi-hanging-problems-on-galaxy-note-2/
-Wade
Sent from my SGH-I317 using xda app-developers app
Since we do not have a stock UCAMA3 Build to flash via odin, what build are you flashing to return the stock build ??
Are you downgrading and taking the update ??
We need more information..... as a step is missing I believe. ..g

[Q] Touch is Auto Responding without touching

Hey guys I have white galaxy nexus maguro.
The problem I facing is quite strange and I want help.
I have been using my phone from more than 6 months my phone works fine with stock rom i tried installing rom before months back a custom rom and it was CM 10.1 my phone touch starts to respond after sometimes clicks are happening everywhere i changed rom back to stock and problem goes.
So now after many months i came to know about this amazing rom for gnexus CrDroid based on Cm10.2
I just installed it and the problem i faced before is here again.
So conclusion to all this is my screen touch response is extra sensitive or i dont know what happens with it when i install a custom rom on it,
On stock rom its fine,
So what you guys think i should do or anyone else had the problem like that if they solved it please help thanks
Nuke_- said:
Hey guys I have white galaxy nexus maguro.
The problem I facing is quite strange and I want help.
I have been using my phone from more than 6 months my phone works fine with stock rom i tried installing rom before months back a custom rom and it was CM 10.1 my phone touch starts to respond after sometimes clicks are happening everywhere i changed rom back to stock and problem goes.
So now after many months i came to know about this amazing rom for gnexus CrDroid based on Cm10.2
I just installed it and the problem i faced before is here again.
So conclusion to all this is my screen touch response is extra sensitive or i dont know what happens with it when i install a custom rom on it,
On stock rom its fine,
So what you guys think i should do or anyone else had the problem like that if they solved it please help thanks
Click to expand...
Click to collapse
You didn't do anything wrong while flashing? Or maybe a mod? Maybe even an app? You could try to flash the ROM and don't install apps and see how that goes for some days. If that doesnt work maybe you could flash stock via fastboot and then flash the ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You didn't do anything wrong while flashing? Or maybe a mod? Maybe even an app? You could try to flash the ROM and don't install apps and see how that goes for some days. If that doesnt work maybe you could flash stock via fastboot and then flash the ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for replying
No I didn't do anything wrong its not my first andriod phone even tho that post was first one on xda never ran into problem.
I think its problem with gnexus many people have different issues with roms but mine is just that its giving me issues on custom roms tried many things flashing again dirty flashed everything.
on stock problem is gone but on the ones i mentioned i am getting this bug that i cant even use my phone i unlock it and touch starts to respond all over the screen
Hey guys since i am testing i just installed slimbean and its working perfectly just like how stock behaves so can someone tell me what slimbean 4.3 and Stock 4.3 have in common and what CM10.2 has not and giving me issues?

Wifi issue on AOSP Roms

Hi guys,
I have had the s2,s3,galaxy nexus,original note and i am used to flashing and modifying,but i have a serious issue with the note 2.
The problem is whenever i flash AOSP rom(cm,aokp,pa) my wifi would not connect.It shows the name of the network and when i click conenct nothing happens.Flashing back TW rom fixes it,wifi works like a charm. I've done full wipes but it doesn't seem to resolve the issue.I tried different kernels,but that doesn't help either.
So I am stuck at TW roms and i hate that.Anyone has any ideas?
You can try options 2 and 3 from this thread.
Thanks for your reply,but i tried this and it didn't solve my problem.
Anyone?
spookhc said:
Anyone?
Click to expand...
Click to collapse
I Have the same problem...
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Primokorn said:
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Click to expand...
Click to collapse
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
With my Note2 this is not the solution. I've tried everything. What you said, move file "pit" ..... but nothing. I can not connect wifi. The connection does not appear region Spain, and have opted to choose europe, but neither. I do not know to do. CM 10.1 also does not work WIFI. In Stock ROM or Custom ROM works fine fine, but in ROM CM 10.1, 10.2, AOKP don't work.
spookhc said:
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
Click to expand...
Click to collapse

[Q] d2tmo 4.4.2 Accelerometer Issue

Ok so ever since I updated to any of the 4.4.2 rom (i.e. Cm11, Cyanfox, SlimKat and Carbon Rom) my accelerometer won't work correctly.
At first I thought it was a GPS issue but after looking into it more the GPS locks fine. It's only the direct in google maps or any other GPS like app that is messed up. For instance, when I'm using google maps and I'm facing north it will show me facing east, then when I change directions it can't figure out which direction I'm facing and spins around in circles and maps will crash. Same thing happens when I use GPS Status, the app will say I'm facing the wrong direction and when I move direction it starts to spin out of control.
I defiantly don't think its a hardware issue since everything was working fine with the touchwiz rom and 4.3 roms. If anyone has any clue on how to fix this I would greatly appreciate it. This is pretty much the only thing that is wrong for me with any kitkat roms.
I have a tmobile galaxy s3 and current running SlimKat build 3. :crying:
Try FasterFix app
Perseus71 said:
Try FasterFix app
Click to expand...
Click to collapse
I gave it a shot but no luck. I have also used GPS status and FasterGPS but like I said before I don't think its a GPS issue because it does lock on to my location fine. It's just my compass doesn't work correctly.
I believe CM has a Advanced Option to Re-Calibrate Accelarometer. Settings > Advanced is where the option is I think. I use Slim Bean so I don't have CM details.
Oh yeah I forgot about that but it still didn't work. I appreciate all the ideas though.
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Perseus71 said:
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Click to expand...
Click to collapse
Do you mean odin to stock or just flash a stock rom? If it's odin I'll definitely try it when I get home. The thing I find weird is that when I flashed the S3Rx rom, everything was working fine.
I'd do Odin before trying anything else.
So I odin back to stock and like before everything was working properly. Then when I flashed back to carbon rom, is back to pointing in the wrong direction and spinning out of control.
I'm surprised that I'm one of the only if not the only one with this problem. Is there an app that I can manually calibrate which direction I'm pointing?
I'm out of ideas...
Can you flash a different kernel on top of Carbon ?
Perseus71 said:
Can you flash a different kernel on top of Carbon ?
Click to expand...
Click to collapse
I flashed KT kernel, BMS, Harkness and DKP. For a little while it seemed like BMS had fixed it but then went back to the same ol' sad story. :crying:
Try Another Rom please. Not just Carbon. This time try a 4.3 rather than Kitkat.
I have tried other roms and I stated that this didn't happen till I started using Kitkat roms. When I was on carbon 4.3.1 there weren't any problems as well as on S3Rx 4.3 rom. Not sure why this only happens on Kitkat roms and what seems like only to me. I'll continue to look for solutions cause I really like the look and feel of Kitkat.
So after searching and searching I finally found a fix! I was about to give up hope but decided to try one last kernel, Quantum kernel. At first it seemed like it wasn't working but I had to calibrate my accelerometer with GPS Status. After that everything was gravy! I hope this helps others that have the same problem I did!

NF1 Issues Answering Phonecalls

On NF1 based roms, does anyone have issues answering calls like I do? I keep swiping to answer and it won't work, most of the time I miss the call. I didn't have this issue on an older build of TW.
No problems here. Bad flash, maybe?
Sent from my SM-N900T
Have rebooted your phone anytime lately? Also, if you have lots of tweaks you may be slowing down your phone responses.
Weird issue. I download two different ROMs from different threads, with the same issue. I don't known what the problem could be. I don't usually run a lot of tweaks on TW, I keep it mostly stock most of the time, except, that it could be related to a custom kernel. I'll try a stock kernel
Haven't had that issue. That's including experiences from 2 different note 3's. Stock and rooted.
Tried stock kernel. Same issue. I'll have to try to go completely stock and see if the problem returns. I don't know what it could be. Everything else is fine otherwise. Am I able to run the older kitkat ROMs with the newer stuff? If I can, I'll try to confirm that I don't have an issue with those.
EDIT: happened to try the Canadian S5 port, and I have no issues with answering calls. I will just use it for the time being.
I'm still having this issue and I'm completely stock. I don't know what's wrong. It doesn't exist when I'm running the S5 port or an AOSP rom. Anyone have an idea?
EDIT: Found out my baseband was outdated. It didn't update with the firmware update from Kies. I rooted the stock rom, and used Triangle Away, then Odin flashed the modem, things are well now.

Categories

Resources