Hi,
I upgraded my S9 to stock Android 9 Pie and applications that read mobile cellid stopped working. I tried several different applications to no avail. Does it work for you? I am using CellId to switch profiles home/work. Could you test for instance https://play.google.com/store/apps/details?id=com.signalmonitoring.gsmsignalmonitoring for me? Do you see CID and LAC?
Thank you for your time, Jan
Hmm, it works when Location service is on. With Android 8 Oreo it worked even when Location service was off. In fact it worked this way on S2, S4 for long time. I don't like to reveal my exact position just to see cell id.
Jan
Related
There's a problem with gps on my phone Samsung FOCUS ,Gps is not working even in the open sky, tried several app like -> gpsinfo,wingps and others like RunKeeper,RunSat etc
Phone is Dev unlocked as well as Interop Unlocked with internet sharing enabled.
The update was done using forced method.Updated from stock firmware->7008->7032->7043->7720.68.
Versions ->
Diag app-> 0103
firnware - 2103.11.8.1
hardware rev. no. - 3.1.0.7
Bootloader ver. - 5.8.0.2
radio software ver. - 0.0.0.3
Please help?
Microsoft released a statement saying they don't blame people or doing the forced update... it doesn't do anything bad to the phone so I don't think that's the issue. You might want to try rolling it back to nodo, checking your gps and then reloading mango. if still no go. Hardware issue maybe??
Issue solved,thanks anyway
So, what was the problem?
Don't know, flashed mango again.That's it.
Gps locked in under 10 sec inside the room.
Hmm. My GPS will find my location fine but getting directions is terribly slow now and turn-by-turn will always just say "can't connect to satellites." Now I'm wondering if a rollback and updating again to Mango will fix this.
I'm on official Mango on an AT&T Focus (and I didn't force the update), and I'm having problems just like the previous posters with GPS fixes and 'can't connect to satellite' errors when trying to get directions.
I found a solution by going into another application that uses GPS, getting a GPS fix in there, then going back into the maps. The program I use is "GPS & GPX Logger." After that finds the satellites, the maps work as they should.
For background info, my phone went from NoDO->Mango Beta 2 (7661)->Mango Beta 2 Refresh (7712)->Unforced official Mango including "Samsung Update"
I tried the turn-by-turn again this morning and it actually worked. This is the first time it has since updating last wk. I didn't change a thing, so I have no idea why it work suddenly.
GPS works on Samsung Focus even after Tango update
I own samsung focus 1.3 (AT&T). I purchased it in the beginning of Sep. 2012 (quite late). As soon as I got the phone, I connected it to Zune for updates. After having updated to 7.10.7720.68, I started using the phone. The GPS did not work. I then updated it to 7.10.8773.98 with the hope that updates may make GPS working. I tried all possible tricks available on XDA as well as other forums. I tried following tricks with various permutation & combination:
(i) Pulling out the battery for 30 minutes.
(ii) Changing the MOLR CP/UP setting in GPS diagnostic to UP and CP (one by one),
(iii) Rebooting the phone with location off & again rebotting with location on
(iv) Apps like GPS info & others
& few more which I do not recall now.
After having tried for about a month, I reverted back to original OS version 7.0.7004.0 just to ascertain the availability/ functionality of GPS hardware as on some of the forums I read that their GPS stopped working after No-Do updates. The GPS did not work even after trying all above tricks on 7.0.7004.0 version of OS.
Finally I accepted my GPS to be faulty or not being there and again updated to latest OS version.
One day I read on some forum that putting off the location service & then switching on makes GPS working. Wow, I tried it today, IT WORKED. On bing map it locked, initially with a bigger circle & then reducing down to a dot. In areas covered with thick trees or high-rise buildings, the circle used to become bigger but again in clear sky area it used to reduce down to dot. I am keeping my fingers crossed. Let me observe for some more days to ascertain that this trick actually works.
Those who have not been able to make their GPS working with other tricks, please try this & let us have your feedback on this forum/ thread.
GPS not reliable
In continuation to my previous post, the working of GPS is not reliable. It sometimes works very fine & some times doesn't work at all during the entire journey of 15 Km. You cannot depend on this GPS for navigational aid. It appears to be some software issue. But anyway, I am happy that my GPS is not faulty. Hoping for some fix in future which will make GPS work reliably.
A. K. Jain said:
In continuation to my previous post, the working of GPS is not reliable. It sometimes works very fine & some times doesn't work at all during the entire journey of 15 Km. You cannot depend on this GPS for navigational aid. It appears to be some software issue. But anyway, I am happy that my GPS is not faulty. Hoping for some fix in future which will make GPS work reliably.
Click to expand...
Click to collapse
GPS working perfectly for me with my Nokia 800 with Nokia Drive.
Some cars have some sort of coating on the windscreen which sometimes blocks GPS, although I wouldn't expect that to be on US cars.
gilesjuk said:
GPS working perfectly for me with my Nokia 800 with Nokia Drive.
Some cars have some sort of coating on the windscreen which sometimes blocks GPS, although I wouldn't expect that to be on US cars.
Click to expand...
Click to collapse
The issue is not related with car glasses as I have tried a lot in clear sky on foot. The issue seems to be specific to Samsung focus drivers.
I am surprised that after months and fifteen pages of Galaxy Tab S discussion no one has asked this question yet. On a 16GB wifi-only T800 model running the stock 4.4.2 Kit Kat OS, where is the option for the automatic network time synchronization?
I am looking under Settings > General > Date and Time
There is no option for automatic or network time sync. There is only a possibility to set time manually. I could post a screenshot if you wish.
Akopps said:
I am surprised that after months and fifteen pages of Galaxy Tab S discussion no one has asked this question yet. On a 16GB wifi-only T800 model running the stock 4.4.2 Kit Kat OS, where is the option for the automatic network time synchronization?
I am looking under Settings > General > Date and Time
There is no option for automatic or network time sync. There is only a possibility to set time manually. I could post a screenshot if you wish.
Click to expand...
Click to collapse
Ya I noticed this too on my sm-t700 I just set the time and forgot about it :laugh:
Well afaik network time sync refers to synchronising the time with a local network cell tower. If you only have wifi you cant possibly sync with the network.
However i do agree that it could easily be achieved via an internet ntp server, but that would be a different option to select and seeing as you can do this by simply installing an app, i guess the choice is left to the user.
Just got my 8.4 wifi yesterday. Opened it up, booted up, and once I connected to my home wifi the time & date auto set. I didn't have to do anything.
ingenious247, perhaps the 8.4 model comes without this issue.
ashyx,
I am personally think that the lack of option for NTP time setting should be treated like a bug. A lot of network protocols and applications rely on time being set accurately. I think nearly every network connected OS for the last 20 years had an NTP client (don't know about Win 95, but NT4 should have certainly had it). Installing a third party app does not correct this issue because you still need to root the device to make this work. I will try to break through Samsung technical support in order to report this as a bug.
Moved to Q&A
Please post questions in the correct section.
After having a few quick searches, it seems like Android does now use NTP for time synchronization, and so this is not a Samsung specific issue. Supposedly the models with GPS receivers can query the NTP servers, but I don't know if they use that information for setting time or something else. Oh well. I guess I might root my device to install a third party app for NTP support.
Hi guys, I've already tried to find a solution to my problem in other threads, but no one fits it.
Basically without no system updates (I'm using this https://forum.xda-developers.com/g4/development/rom-h-rom-v30-port-t3672567 rom with Android 7.0 on my G4) if I set my fake gps (it's set correctly in developer settings) to any place, Google Maps will show my fake location, but while making a double check with Opera browser on whereiamrightnow.com website I get my real location. That's really weird because since yesterday it was working fine.
So I thought to myself "Maybe it is caused by an update of Opera", so I took my old Galaxy S2 with Lineage Os on (running Android 7.1.2), I updated all the applications (Fake gps, Opera browser and Maps), I set the fake gps app in developer settings and then I turned on only the Gps (without network positioning, as I used to do on the G4 when it was working), then I set a random place in Fake gps and checking on Maps and Opera both of them show me the fake position.
So I found out it is not an app update problem.
Any clue?
Thanks in advance!
Hello all, I've had a long Moto G devices track, and since my old Moto G 3 for each new device I used the "restore from another Android" feature successfully.
Now I purchased 2 different Moto G 5G Plus (XT2075-3) coming from 2 different marteks I guess, one shipped with Android 10 and the second one shipped with Android 11 already.
At the end, the procedures only restored the Google account and the installed apps, but they missed at least the home screen configuration (background, icons and groups of icons in the screens) and the known Wi-Fi networks.
in facts I got a standard stock Android home screen without any personalization, and no wifi networks already set.
My last previous phone was a Moto G Pro with Android 11 stock.
In both the new 5G Plus phones, for the first time ever the procedure to automatically configure the new phone using the Google backup settings didn't complete the job.
In the first 5G Plus (the one shipped with Android 10) before the start it said that the destination device had an operating system version older than the source one and some settings could be not restored (without specifying which).
In the second 5G Plus (the one with Android 11) the alert was only that some settings could not be restored.
Another difference in the procedures: in the Android 10 one, at the time of initial configuration I could set the first Wi-Fi network by using the QR code, whilst in the Android 11 one this could only be done by typing the long WiFi WPA password, because the button to scan the QR code was not present at the time of first initialization. So I completed the initialization without setting the wifi, and only after I could scan the QR code with the camera to configure the first wifi.
I miss the restore of the home screen configuration and the known Wi-Fi networks.
Is there a way to "force" the restore of the home screen configuration and the networks?
Thank you
Ale
I'm looking for some help in finding a workaround for the pixels (6 pro, 7) dropping 5g nr connection due to lack of ims registration on Android 13.
My device is running build: tp1a.221105.002
Pixel 7 was a friends device running the latest.
Pixel 6 is working fine on Android 11. (I wish I could just roll back like we could in the old days...)
Test setup:
Ubuntu 22.04 desktop
Open5gs core
SRSRan_Project running on a b210, transmitting inside a faraday cage
USB C connect to phone through Faraday Cage USB port
Running scrcpy to monitor phone visually in parallel with "logcat -b radio"
So far I've tried using the *#*#0702#*#* ims menu. I futzt around with a menu called, "Edit Ignored CarrierConfig Filter".
Tried a few registrations with a handful or ims registration related toggles.
The most promising was: ims.ims_registration_required
But it didn't fix the issue. Still getting PDU sessions and just losing connection after a few minutes.
For more details check the attached logs, but in human speech; The device registers just fine according to the amf. The UE is even assigned a PDU session and I can access the internet to watch YT or ping around the network. But after 1~5 minutes (always random) the UE will use drop connect. The amf logs don't show an reregistration or UE-idle messages either.
For comparison sake I used a gold standard pixel 5 and pixel 6 running Android 12 and they work fine. Additionally, I found an S22 to try running Android 13 and that phone stays connected for hours when testing.
Before I set out to build the ims server using Kamailio, I wanted to make sure the phone didn't require it. When I move to 5g handovers I'd like to isolate the test using the RSRP to trigger by itself and not have to get lost in the ims networking handover also.
Thanks in advance for all the help!
P.S. I wrote this in a bit of a hurry. I'll make some edits around lunch.
Edit: Mixed up my android versions. Corrected.
stans_hands said:
Pixel 6 is working fine on Android 11
Click to expand...
Click to collapse
Didn't the 6 series launch with 12? Maybe I'm delirious but I'm pretty sure that's the case.
Also the 12 bootloader has been compromised. Is there a reason you avoid 13 (and coming later this year 14).
Good Call, Thanks for pointing that out. I mixed up the android versions. Correct now.
These phones are only for test networks I run as a hobby. I'm not hurting to use them so upgrading isn't a priority. For me learning is the goal, how the phones work and some of the more niche options hidden from regular users.
I'm hoping to make Android development my passion.
Update:
Rerooted the Pixel 6 with tq2a.230505.002
Problem persists.
Borrowed a friends Pixel 7 running android 14 and the problem still exists on even the newest Android.
Samsung and Sony might be the only good test phones at this point.