Update:
I have used Pocket Earth 3.5 to help show what I believe is my GPS running appropriately.
When setting up and detecting an operational port, my GPS detects and runs on Com5 with a rate of 1200, even when manually set to use the following configuration (GPS program port set at comm 8 and hardware port set at comm 4, with baud rate of 34800).
It both show:
Waiting for GPS data...
PSRFTXT,CHNL: 1273
GPRMC,235947.035,V,,,,,,,120806,,,N48
GPRMC,235948.044,V,,,,,,,120806,,,N41
another running capture shows:
GPRMC,000152.032,V,,,,,,,130806,,,N46
GPRMC,000153.032,V,,,,,,,130806,,,N47
GPRMC,000154.042,V,,,,,,,130806,,,N47
I believe this information shows that my device is functioning appropriately (but according to the reference below it looks like I am getting incomplete word groupings / sentences), but at the same point in time I can't get any other application to show a gps fix or even signal. I have used several radio stacks and left my device in the open for more than 20 minutes without so much as a small degree of signal showing up from any of the birds. I do get listings of the birds that are in the air, but not enough to lock or provide positioning. Does anyone have anythoughts or ability to translate the running feed shown above? I can get my tilt to function without issue, but my athena running PK 3.0 isn't happy...
Lastly, Googlemaps seems to provide a blue flashing dot from time to time, but won't give me anything better than a 5km ring of accuracy. The other apps don't even do that :-(
Any help, understanding, decoding, or tools would be greatly appreciated.
v/r
Bob
+12404756858
Reference: http://www.cis.udel.edu/~mills/ntp/html/drivers/driver20.html
$GPRMC,POS_UTC,POS_STAT,LAT,LAT_REF,LON,LON_REF,SPD,HDG,DATE,MAG_VAR,MAG_REF*CC<cr><lf>
$GPGLL,LAT,LAT_REF,LONG,LONG_REF,POS_UTC,POS_STAT*CC<cr><lf>
$GPGGA,POS_UTC,LAT,LAT_REF,LONG,LONG_REF,FIX_MODE,SAT_USED,HDOP,ALT,ALT_UNIT,GEO,G_UNIT,D_AGE,D_REF*CC<cr><lf>
POS_UTC - UTC of position. Hours, minutes and seconds [fraction (opt.)]. (hhmmss[.fff])
POS_STAT - Position status. (A = Data valid, V = Data invalid)
LAT - Latitude (llll.ll)
LAT_REF - Latitude direction. (N = North, S = South)
LON - Longitude (yyyyy.yy)
LON_REF - Longitude direction (E = East, W = West)
SPD - Speed over ground. (knots) (x.x)
HDG - Heading/track made good (degrees True) (x.x)
DATE - Date (ddmmyy)
MAG_VAR - Magnetic variation (degrees) (x.x)
MAG_REF - Magnetic variation (E = East, W = West)
FIX_MODE - Position Fix Mode ( 0 = Invalid, >0 = Valid)
SAT_USED - Number Satellites used in solution
HDOP - Horizontal Dilution of Precision
ALT - Antenna Altitude
ALT_UNIT - Altitude Units (Metres/Feet)
GEO - Geoid/Elipsoid separation
G_UNIT - Geoid units (M/F)
D_AGE - Age of last DGPS Fix
D_REF - Reference ID of DGPS station
CC - Checksum (optional)
<cr><lf> - Sentence terminator.
Alternate GPS sentences (other than $GPRMC - the default) may be enabled by setting the relevent bits of 'mode' in the server configuration line
* server 127.127.20.x mode X
bit 0 - enables RMC ( value = 1)
bit 1 - enables GGA ( value = 2)
bit 2 - enables GLL ( value = 4)
multiple sentences may be selected
If you have a ring.... you aren't using your GPS, you are using the built-in GMAPS feature that rely on cell position...
There is a 3d here in ATHENA>ATHENA section on GPS optimizzation.
http://forum.xda-developers.com/showthread.php?t=375959
Also, COM 5 is the actual GPS hardware port. If you have anything talking to COM5, nothing else will be able to get to the GPS chip.
GO to start>settings>system>external GPS.
Set the software tab to something other than 5. COM4 or COM9 are usually pretty reliable
Set the hardware tab to (None) and the baud to 4800
Tick the box on the access tab.
tap ok.
Then set all your GPS programs to use the one you specified on the Software tab.
I find that Google maps on mine always uses the ring if i set it to com 5, but if i let it go through the MS driver as above, it then seems to be able to get the lock quite well.
rhedgehog said:
Also, COM 5 is the actual GPS hardware port. If you have anything talking to COM5, nothing else will be able to get to the GPS chip.
GO to start>settings>system>external GPS.
Set the software tab to something other than 5. COM4 or COM9 are usually pretty reliable
Set the hardware tab to (None) and the baud to 4800
Tick the box on the access tab.
tap ok.
Then set all your GPS programs to use the one you specified on the Software tab.
I find that Google maps on mine always uses the ring if i set it to com 5, but if i let it go through the MS driver as above, it then seems to be able to get the lock quite well.
Click to expand...
Click to collapse
You sir are a star (a sirf-star?) , using my other settings it's been struggling to get a signal today, just tried what you suggested and 6 sats locked in under 4 mins only difference is that the baud rate is 38400
Related
Have anyone got the GPS on the Titan to work when you don't have network service?
I have even tried this:
http://www.rimweb.in/forums/index.php?showtopic=13024
I can get my Titan to pick like around 10 sats but it's very unlikely that I will get a lock (1 of 20 times I get a lock).
Cliff notes: What do you have to do to get the GPS on the Titan to work in Europe?
Thanks
Without data, as long as you don't enable aGPS it will work in offline mode, however it's very intermittent on sync. The best method is to turn it on, give it a clear view of the sky either outside or in your car and just wait. If you are driving it will almost never sync up.
Get a tool like Bafs GPS Toggle. As it won't "time out" like Google Maps and Live Search will do. If you just wait it should eventually sync up.
As for outside the country, I am not sure if any of the primer tools like QuickGPS will help, not sure if they will download the ephemeris data for those areas. The first satellite your phone can link onto will then transmit ephemeris data to your phone and tell it what other satellites should be visable at the moment and the upcoming schedule for the upcoming time periods. It then attempts to connect to the others. If it can never make that initial connection then you may never get a sync.
Just give it some time. Mine never took more than 15 minutes while standing still, tho while driving I drove for over 30 minutes once with no sync, however I came to a long stop light 2-3 minutes, and bam it synced. So the trick is to just sit still.
I've never been to Europe, so I can't guarantee that my advice will help.
BTC
BillThyCat said:
Without data, as long as you don't enable aGPS it will work in offline mode, however it's very intermittent on sync. The best method is to turn it on, give it a clear view of the sky either outside or in your car and just wait. If you are driving it will almost never sync up.
Get a tool like Bafs GPS Toggle. As it won't "time out" like Google Maps and Live Search will do. If you just wait it should eventually sync up.
As for outside the country, I am not sure if any of the primer tools like QuickGPS will help, not sure if they will download the ephemeris data for those areas. The first satellite your phone can link onto will then transmit ephemeris data to your phone and tell it what other satellites should be visable at the moment and the upcoming schedule for the upcoming time periods. It then attempts to connect to the others. If it can never make that initial connection then you may never get a sync.
Just give it some time. Mine never took more than 15 minutes while standing still, tho while driving I drove for over 30 minutes once with no sync, however I came to a long stop light 2-3 minutes, and bam it synced. So the trick is to just sit still.
I've never been to Europe, so I can't guarantee that my advice will help.
BTC
Click to expand...
Click to collapse
Thanks but I already tried all that, it doesn't seem to work when you're outside the US, I have left the phone for hours under clear sky, sometimes it will even reboot and I will need to start priming the GPS again.
There must be some special setting that I need to do in the phone.
Daved+ said:
Have anyone got the GPS on the Titan to work when you don't have network service?
I have even tried this:
http://www.rimweb.in/forums/index.php?showtopic=13024
I can get my Titan to pick like around 10 sats but it's very unlikely that I will get a lock (1 of 20 times I get a lock).
Cliff notes: What do you have to do to get the GPS on the Titan to work in Europe?
Thanks
Click to expand...
Click to collapse
i don't know for sure if the following will work outside the US.
open up a registry editor, i use PHM Registry editor
go to this key
HKLM/SOFTWARE/HTC/supl agps
change the following, if they need it, to:
EnableAGPS 1
EnableGPSSmartMode 1
GPSMode 4
click ok, quit the reg editor, do a soft reset and go back to make sure the settings took.
this will allow you to use the stand alone gps without the need of being in cell tower range. google maps will not work, since it uses the data connection to load the maps.
GPS Mode 4?
g2145 said:
i don't know for sure if the following will work outside the US.
open up a registry editor, i use PHM Registry editor
go to this key
HKLM/SOFTWARE/HTC/supl agps
change the following, if they need it, to:
EnableAGPS 1
EnableGPSSmartMode 1
GPSMode 4
click ok, quit the reg editor, do a soft reset and go back to make sure the settings took.
this will allow you to use the stand alone gps without the need of being in cell tower range. google maps will not work, since it uses the data connection to load the maps.
Click to expand...
Click to collapse
Isnt GPS Mode 4 only for Sprint users?
i don't know myself if it is carrier specific.
i do know it works on my sprint mogul.
Hi everyone, first I want to apologize for my bad english, I will try to explain my problem. I'm from Venezuela, my cell phone carrier is Movilnet, my Titan setup is ROM DCD 3.3.4, Radio 3.2.50, PRI 2.03. The problem is: when I'm on cell phone service area my GPS never gets a lock, unless I let the phone all night with the GPS software trying to lock.
But, when I travel out of the city to an area whitout cell phone coverage, I can get a lock within 2 minutes, consistently, even after a soft or hard reset.
I'm using VisualGPSce to monitoring and priming the GPS, but I also had tried GPS Test, GPS Viewer, GPS toogle, etc. I had noticed that, when I'm trying to lock with VisualGPSce, the software give me a initial position that is 180º wrong, i.e. If the right coordinated is N8º 20,91 W62º 39,14, the software shows N8º 20,91 E62º 39,14. I had tried in flight mode with no success, also disabling aGPS in the registry, may be I will try a QPST config, but I don't know what config can I change.
My thery is that the cell phone towers create some kind of "conflict" and messed up all the GPS syncronization, may be the time syncronization, I don't know.
Thanks for your help.
g2145 said:
i don't know for sure if the following will work outside the US.
open up a registry editor, i use PHM Registry editor
go to this key
HKLM/SOFTWARE/HTC/supl agps
change the following, if they need it, to:
EnableAGPS 1
EnableGPSSmartMode 1
GPSMode 4
click ok, quit the reg editor, do a soft reset and go back to make sure the settings took.
this will allow you to use the stand alone gps without the need of being in cell tower range. google maps will not work, since it uses the data connection to load the maps.
Click to expand...
Click to collapse
Won't get a lock with those settings... I will pick a lot of sats but will never get a lock.
Seems the GPS on the Mogul won't work in Europe or anywhere outside NA.
anddy78 said:
Hi everyone, first I want to apologize for my bad english, I will try to explain my problem. I'm from Venezuela, my cell phone carrier is Movilnet, my Titan setup is ROM DCD 3.3.4, Radio 3.2.50, PRI 2.03. The problem is: when I'm on cell phone service area my GPS never gets a lock, unless I let the phone all night with the GPS software trying to lock.
But, when I travel out of the city to an area whitout cell phone coverage, I can get a lock within 2 minutes, consistently, even after a soft or hard reset.
I'm using VisualGPSce to monitoring and priming the GPS, but I also had tried GPS Test, GPS Viewer, GPS toogle, etc. I had noticed that, when I'm trying to lock with VisualGPSce, the software give me a initial position that is 180º wrong, i.e. If the right coordinated is N8º 20,91 W62º 39,14, the software shows N8º 20,91 E62º 39,14. I had tried in flight mode with no success, also disabling aGPS in the registry, may be I will try a QPST config, but I don't know what config can I change.
My thery is that the cell phone towers create some kind of "conflict" and messed up all the GPS syncronization, may be the time syncronization, I don't know.
Thanks for your help.
Click to expand...
Click to collapse
What GPS settings do you have in your registry?
daved+
what rom are you using?
g2145 said:
daved+
what rom are you using?
Click to expand...
Click to collapse
I am using a rom made by myself with BuildOS but I also tried DCD and other ROMs with the same result.
If you have any suggestions, please let me know.
i had an idea of you trying to get a gps lock without installing the carrier cab..just to see for the heck of it.
g2145 said:
i had an idea of you trying to get a gps lock without installing the carrier cab..just to see for the heck of it.
Click to expand...
Click to collapse
Well, that's exactly the point, getting a gps lock when you don't have a carrier (no network service at all).
GPSMode
Daved+ said:
Won't get a lock with those settings... I will pick a lot of sats but will never get a lock.
Seems the GPS on the Mogul won't work in Europe or anywhere outside NA.
Click to expand...
Click to collapse
Try GPSMode 2. That is what I use.
oneders65 said:
Try GPSMode 2. That is what I use.
Click to expand...
Click to collapse
Believe me, I've tried all modes.
I supposed mode 2 would work because that's the factory mode on the GSM models that works on networks with no aGPS, yeah, I have even copied the settings from a GSM TyTN II and a Touch Cruise, they won't do the trick on the Titan.
Daved+ said:
What GPS settings do you have in your registry?
Click to expand...
Click to collapse
After the hard reset, the default registry settings was:
EnableAGPS 1
EnableGPSSmartMode 1
GPSMode 2
That works in the no cell phone service area, but in the city, doesn't work.
you can use standalone gps with some of the radio versions:
3.35.04: gps mode 2: no lock, no reboot
3.39.10: gps mode 2: one lock, 1x reboot effect
3.41.00: gps mode 2: 3x constant locks, good navigation, no proven reboots
3.41.00: gps mode 1/disabled smart, disabled agps 0x constant locks, 2x proven reboots
3.42.02: gps mode 2: 1x reboot effect
3.42.30: gps mode 2: no lock, no reboot
3.42.40: running: 3x lock, 0x reboot (disabled smart, disabled agps, gps mode 1)
3.42.50: gps mode 2:1x reboot effect
i used own cooked rom with ppckitchen 20931, a gps software to initialize it (Sirftech, free) reprogrammed the phone with qpst (all gps checkboxes on like recommended somewhere in the forum) and much patience... a lock need sometimes up to 2 hours from window (had to connect the phone on the glass in 2nd floor), outdoor it locks while remaining in the car and myself going shopping for some time.
Sometimes with working configuration it never locks, sometimes it does, no matter how much sattelites in view (mostly 5 to 10)
The reboot occurs in my opinion in the moment the phone gets a lock - some user assumed it only happends if you stay outside usa.
I am in germany (no network available) and have disabled phone, wlan, bluetooth.
Try 3.42.40, use gps mode 1, disable agps, and use sirftech - if that doesnt help, post again...
cyclon1978 said:
you can use standalone gps with some of the radio versions:
3.35.04: gps mode 2: no lock, no reboot
3.39.10: gps mode 2: one lock, 1x reboot effect
3.41.00: gps mode 2: 3x constant locks, good navigation, no proven reboots
3.41.00: gps mode 1/disabled smart, disabled agps 0x constant locks, 2x proven reboots
3.42.02: gps mode 2: 1x reboot effect
3.42.30: gps mode 2: no lock, no reboot
3.42.40: running: 3x lock, 0x reboot (disabled smart, disabled agps, gps mode 1)
3.42.50: gps mode 2:1x reboot effect
i used own cooked rom with ppckitchen 20931, a gps software to initialize it (Sirftech, free) reprogrammed the phone with qpst (all gps checkboxes on like recommended somewhere in the forum) and much patience... a lock need sometimes up to 2 hours from window (had to connect the phone on the glass in 2nd floor), outdoor it locks while remaining in the car and myself going shopping for some time.
Sometimes with working configuration it never locks, sometimes it does, no matter how much sattelites in view (mostly 5 to 10)
The reboot occurs in my opinion in the moment the phone gets a lock - some user assumed it only happends if you stay outside usa.
I am in germany (no network available) and have disabled phone, wlan, bluetooth.
Try 3.42.40, use gps mode 1, disable agps, and use sirftech - if that doesnt help, post again...
Click to expand...
Click to collapse
THANKSSSSSSSSSSSS!!!!!!!!!!!!!!!
That's exactly what I needed to know!!!!
I'm using 3.42.50, now I know why I can't get a lock.
I will flash the 3.42.40 radio, I hope I can do the same on the Vogue.
Thanks again!!!!!
cyclon1978 said:
Try 3.42.40, use gps mode 1, disable agps, and use sirftech - if that doesnt help, post again...
Click to expand...
Click to collapse
Posting again... After around 40 min, the phone rebooted, no lock at that moment but it was seeing 4 sats.
Do I try with a different radio or different settings?
Thanks
I now have 100% gps reception after letting the device ~20 minutes in the car. So i will post my configuration and hope it helps:
ROM Version: 3.08.666.1 (ppckitchen selfmade, nothing special included)
Radio Version: 3.42.40
Hardware Version 3
PRL 60613
PRI 2.03_003 (these doesnt really matter in airplane mode)
I use the "10 items" communication manager with all disabled except of flight mode.
Registry: Default from rom plus the following changes:
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:EnableAGPS = 0
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:EnableGPSSmartMode = 0
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:GPSMode = 1
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:QoSAccuracy = 25
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:QosPerformance = 89
HKEY_LOCAL_MACHINE\SOFTWARE\HTC\SUPL AGPS:TimeBetweenFixes = 1000
All values are decimal, not hex!
i think that changing QoSAccuracy from 50 to 25 and TimeBetweenFixes from 1 to 1000 had absolutely no effect. So you should try to change only the first 3 values...
in QPST service programming i have disabled "Allowed" because i read it will not disable the gps but the agps - thats true. I have checked and unchecked all boxes, checked only Autonomous and GPS/AFLT Hybrid.
... in all times i got a lock i started the device from power off mode (pressing power button long time)!
GPS Mod Driver (From original post in Diamond thread Ending Here)
This Driver installs between your gps application and the GPS driver that reads the hardware gps.
- Lag is compensated, by guessing your position 'some number' of milliseconds in the future, current course and speed changes are included in the guess.
- Driver corrects for invalid data in the gps strings, Out of range DOP values, and Heading values of 'NaN' (Not A Number). Position, Speed, and course are reported, even though the distance traveled is less than 30 meters.
- Cell Tower location is used when GPS is unavailable
- Altitude is corrected from/to WGS84/ASL
- Hardware Compass Support
- Allows selction of many input sources, including MSApi (GetPosition api)
- Suports GPS applications on any COM port, as well as GPSApi (GetPosition api)
Hardware Compass Support information is in Post Number two
QueStub support is in post Number Six, Garmin can now use GPS Intermediate Driver, so no longer needs QueStub
Newest Version:
3.4.4
Add back in the detection of dead input port
3.4.5
Fix GpsApi when calling app is stupid
- Caller asks for V1 data with V2 dwSize (I return V1 as version with V2 size, and V2 data in the return
FixGpsApi GPSGetDeviceStatus
Change ReadNewData to detect, and call GPSGetDeviceStatus, and set the waiting handles (if there are any)
3.4.6
Remove trap on stuck GPS from msapi, only COM ports are detected (TP2)
Rename gpx and csv files to: "ModDriver_{date}_{time}{In or Out}.{gpx or csv}"
3.5.0
Add GPX tracklog 'ending' to each log write, fseek back to overwrite.
Change time sync to CellInit, since clock is functioning when service loads.
- Detect when Cell service not loaded, and sync on GPS open port
3.5.1
Created a new device MsClock, provides current device time with millisecond resolution
Created and linked MachClock.dll (uses MsClock)
- Provides SystemTime and FileTime with 1 m/s resolution
- Uses device clock for base time
- Re-Sync time on device wake-up from sleep
Used MachClock to keep time in sync (all apps and drivers)
Fixed a bug in appending GPX tracks to existing logs
3.5.2
Move DeviceStatus maintenece to ModDriver
- Modify COM_Read, COM-Write to support transfer of data to caller (GPSApi.dll)
Remove Power up/down redundentcies from ModDriver and MachCell
Add Thread open count to MsClock
Fix Power up notify in MsClock
Fix Extra calls to UpdateDeviceStatus in ModDriver, when no-one is listening
Create Named event in GPSapi.dll to track mutiple instances of dll
3.5.3
Include AutoLog, RegUtil, and CardPath into MachClock.dll
- Should save some ram since the code will only load once (shared for all apps and drivers)
- On my device running GpsModSetup saves 20kb of ram
MachCell should have saved another 20kb too, but since it is a service I can't prove it
- Fix a COM port read issue when GSV is not sent regularaly (some BT recievers)
3.5.4 - 3.5.6
Fix EnableLogs Registry read error issue
Remove close COM port on PurgeCom (bug)
Fix time error
Fix GPX logging
- Could stop/delay output data
3.5.7
ModDriver could be sending data to the application way too often
MsClock driver was not being used by ModDriver
MsClock bit of tweeking, and was made faster too
could have stayed running 'awake' when nothing was using it.
GPX log files was still broken sometimes, another tweek there too.
reset the device clock to the GPS time (+500m/s)
added some logging to MsClock, but only for testing
3.5.8
Logging Owner Process Name in ModDriver and MsClock
Extra Delay removed reading some COM input devices
When input port times out, reader thread could stay active (or even duplicate)
MsClock, only reset device clock if it needs resetting (read current clock, and compare first)
Changed timing on EnableSmooth
- Used to return data at 600, 400+, 600...
- Now 500, 500+, 500, 500+,
Better handling when reader app crashes without closing the ports
- System sends me Ioctl_Psl_Notify
- I force close reader port, SetLastError( 6 )
- In GPSApi I react to GetLastError() == 6, by exiting the reader thread.
3.6.0
- Fixed a minor issue with sudden loss of BT com port
Version 3.10 and newer: Added Direct support for reading cell tower location.
See the change log and Cell Tower features starting on post 1346 here
External Card Storage
- If the card is removable, installing a device driver to it is just a BAD idea, don't do it!
- My attached shortcuts don't work, make your own or edit mine.
- Your card may not be avalable during early boot, so driver may not autoload.
- Driver will take londer to load, so phone will take longer to boot.
- ModSettings will take longer to load
- Uninstall is not as perfect, but still works fine, except it is possible that the dll on the card may not be removed if it is in use at the time.
- Did I say don't install to a card unless you have to?
- Install the driver cab, change your GPS application to the indicated port or to use Gps Intermediate Driver, instead of the original internal com port.
- Run GpsModSetup (found in start), you will see live gps data from the ModDriver on the main page. Tapping the screen will toggle to a sattelite view screen.
Menu/[Profile] (driving or Walking): to use a preset setup, Save will update driver to use new profile. If auto profile is enabled you will not be able to make this selection, but can still edit the profile's values.
Menu/System: to change the values used by ModDriver.
- Log File: Creates a debug log in \Mach2003 of the device.
- Extended: Adds more information to the logs.
- Track Log: Creates a GPX and CSV file to card\Mach2003 that can be viewed in Google Earth, or many other applications.
- Raw Data: Includes an extra GPX and CSV file for the raw input readings from the GPS source.
- Smooth: Allows Mod Driver to insert an extra GPS output at half the sleep time, so that some map displays are less jumpy.
GpsModDriver section
- Sleep Time: Amount of time that Mod Driver will wait for a new GPS reading. Default devices are 1000 ms.
- ComTimeOut: Passed on to the windows com driver when using a COM input port, amount of time readfile will wait for ANY data to arrive on the port.
- Keep Alive: Driver will keep reading raw data for this many milliseconds after the last reader port is closed. Allows for switching GPS applications without loosing fix.
Be very careful changing the following port, you may need a factory (HARD) reset if you change a port to one that is already in use!
- Com Port: The output port Mod Driver will use to send data to your GPS Application.
- Enable: Enable (or disable) All Mod Driver functions.
Internal GPS Device section
These settings are written to the internal GPS device registry, and MAY be used by the original driver
- Sleep Time: Time to Wait for data when no data is available ro read.
- Poll Rate: How often to check for new data from the internal driver.
- Input Buffer: Amount of phycical RAM to reserve for READING the internal GPS device.
- Output Buffer: Amount of RAM to reserve for communication to MS GPSID driver.
Be very careful changing the following port, you may need a factory (HARD) reset if you change a port to one that is already in use!
- Com Port: Com Port for GPSID data, same as using the 'External GPS' control panel 'software port' item.
- Enable: Enable (or disable) the internal GPS, same as "allow windows to manage device" under external GPS settings.
Menu/Extras: To configure additional settings.
Altitude Table section
- Altitude Fix, To enable driver to correct altitude to true (ASL)
- Prefer GPS, To use GPS altitude when avaiable instead of the table values
- Kill Feature Remove Table, Use to remove the altitude correction feature, and the table file from your card.
Auto Profile Selection
- Gsensor Angle, angle from vertical when to switch to/from walking profile.
- Enable portrait, To autoswitch profile when in portrait mode
- Enable landscape, To autoswitch profile when in landscape mode
Cell Tower Location
- Service is Running Now, Reports current service status, tap to update
- Enable Cell Service, ...
- Enable Service, Only with GPS, starts and stops cell service when Mod Driver is used/closed
- Enable Internet Cell Data, Allows Servicer to use data connection to resolve location of unknown cell towers
- Entries To Save, restricts the size of the cell tower database
- Default MCC, Can be set to YOUR Mobile Country Code for when your RIL does not have this vital information
- ReStart, Stop/Start Buttons.
- Export, To export known cell tower locations to a GPX file
- Update, Used to resolve all unknown cell tower locations, ignores Enable data Flag (use while connected through A/S)
- Kill Feature Remove Service, Use if you don't want cell tower location features.
Menu/Ports: To enable Mod Driver to use other input ports.
Port Scan Mode
- Scan On Power Only, default, allows scanning for a better input port only when the device is plugged in.
- Scan on Battery Too, allows port scan at all times, regardless if device is plugged in or not.
- Never Scan, disables the port scan feature.
- Scan Only Once, does an imediate scan, then sets itself to "never scan".
Input Port section
- Port (MSAPI, or Com Ports from 1 to 9)
- Enable, allows Mod Driver to read this port
- Fix, applies Mod Driver Lag, speed, and heading fixes to this port (some devices might not need these fixes)
- Order, Mod Driver tries to find GPS data on the Enabled ports in this order, 0 first, then 1, 2... (99) is auto entered for the "output" port, as it can not be used for input as well.
All screens have an 'Undo' and 'Save' button. Undo will revert all changes made to the screen, save will update the driver to use the new settings.
Profile Screens
- Name: Used for profile selection and display (alters the names on menu and selection screens)
- Set To Defaults button: Sets all profile fields to factory default values, as installed from the latest CAB.
To Insert Speed and Course section
- Distance Moved: Meters times 10 to update course and speed (30 = 3.0 meters)
- Zero Speed Time: Milliseconds to speed when distance above is not exceeded, your speed will "stick" until this time passes when not moving.
- Minimum Speed: Any speed below this value will be considered as "zero" to filter out erratic slow readings.
To Calcualte Lag Position section
- Speed Threshold: kph times 10 to update LagAdvance position (50 = 5.0 kph), readings with speeds below this value will not have lag applied.
- Lag Advance (ms): Number of milliseconds to project your position into the future to compensate for delay in GPS readings
Toggle Enable section
- Speed Fix: Allow the driver to correct speed
- Prefer GPS: If GPS raw data has a valid speed, use it instead of calcualting speed from position.
- Course Fix: Allow the driver to correct Course
- Prefer GPS: If GPS raw data had a valid course, use it instead of calculating course from position.
- Dop Fix: Allow the driver to correct bad dop values
- Compass: Allow hardware compass with this profile
Auto Input Selection
Mod Driver allows you to select more that one source port for reading GPS data. No matter what input port is used, your GPS application can read Mod Driver to get GPS data.
- You can enable Bluetooth GPS devices as well as MSAPI, and the internal COM port devices.
- 'Order' assigns the preferred port to use, 0 is the most prefered, 1 is next...
- When first started (any GPS application opens Mod Driver port), driver scans ports starting from 0, to find input data.
- If the scan mode is enabled, it tries lower order ports every 30 seconds or so, and switches 'up' to a better port if fixed data is there.
- If the current port looses connection, Driver will try any enabled port to get good data (regardless of scan mode).
- To install a BT device, pair it with your phone, and add an external com port to it.
Altitude Fix
The NMEA standard requires GPS altitude to contain Altitude above sea level (standard was made by boat people), and seperation from the WGS84 ellipsoid used in calculating the ASL. Sea level varies on the planet by up to +- 100 meters from the ellipsoid due to gravitational force changes. Using data from NGA (2008), a table was created (stored on CARD under \Mach2003, 64kb), and is used to determine the seperation value for the current GPS position. In testing, we found that the table value was more current (a more accurate value) then even the devices' driver was using. Prefer GPS will override the table value, and use what the device thinks is correct only if the GPS data actually has the seperation value. You CAN disable this feature and save a bit of card memory by deleting the Altitude*.RAW file. (if card memory can not be found, the file is retained in the devices \Windows folder).
There are also a couple of shortcuts attached here to auto-select a profile. You can copy them to start menu, or to app keys to assign to a hardware button. There is also a shortcut for running the "scan once" selection without "starting up" mod settings.
KillDriver.exe
Used to remove a stuck un-install of the driver instead of using SKTools.
Copy the un-zipped file to the device and run it. It will remove all the files, registry entries, plus the Mod Driver entry in the uninstall database.
It may leave behind some registry entries, and does leave behind the files under \Windows\App Install. You may delete these files manually after running the kill driver application.
GPS Mod Driver - Hardware Compass Support
Mod Driver supports the hardware compass on the HTC, and Samsung devices that have a hardware compass.
- Mod Driver uses Compass Heading below Delta Speed for the current profile in place of GPS heading.
- Compass speed is configurable, default is 2.5 kph (works with Garmin Mobile XT)
- Not all GPS applications will use the heading without a speed, your results will vary.
Samsung Devices need to have the SDK 2.0 cab installed (attached here).
When a hardware Comapass is detected an additional menu item is available for presetting the difference between the hardware compass and actual heading. This is required because your phone may be mounted slightly off angle, and it also reports a 'magnetic' heading instead of the GPS 'True' heading.
Compass hardware does NOT detect landscape rotation properly, but Mod Driver adjusts for this automatically.
Calibration factors are retained for each profile, so mounting (or holding) position is accounted for.
Hardware compass is quite useless in an automobile because of the huge amount of metal around you, and teh EMI that the car generates. You can disable the compass under "Driving" profile, and when using auto profile selection, the compass will only be used when you have the phone out of it's car cradle. Or if you don't use auto-profile, when you select walking profile.
The best way to calibrate the driver's compass value to to just edit the value directly, note that you can not enter a negitive value, but just add 360, and enter that (ie: -21 degrees = 339 degrees).
To calibrate the compass
Choose compass from the menu button.
Be prepared to exceed your current 'Delta Speed' Value for at least 10 seconds, and travel in a relatively straght path.
Compass Screen:
- Num Averages: The number of compass/g_sensor readings to average together
- Landscape Angle: For HTC only, the amount of rotation to determine that landscape is triggered.
- Poll Time: How often to read the sensors.
- The portrait and Landscape buttons are not selectable, but will show the current orientation of the device.
- Values for the current calibration from GPS to COmpass heading can be enetered manually, or viewed here.
- Reset to Zero, allows a simple reset function for each orientaion.
- Calibrate button enters self calibarate mode (see below)
- Help?, condensed version of this post
Calibration
There are three 'status' messages displayed. One for speed, averages, and overall status.
Each message has a check box that will tell you if that item has been satisfied.
Press Calibrate button,
Notice that count (at the bottom) will count down the number of seconds until you get to Delta Speed.
Once at speed, the count will change to teh number of readings included in the calibration average.
Compass and GPS heading are updated as messages arrive from the driver (about once a second).
Once 10 readings are taken for the average value, the updated value will be shown.
any advantage for using this?
Hi Mach2003,
nice work! Awaiting unpatiently your test results!
Mach2003 said:
Edit: Math is done, I found a formulla that works! I am testing it now with a fixed 1 second "De-Lag" time.
Click to expand...
Click to collapse
That's good news, well done!
If the formula 'decreases' lag this way, it should be easy to adjust the components to compensate for any amount of lag.
And for those without lag, who just want a more accurate GPS driver, the formula could be optional.
Now that Mod Driver supports GPS Intermediate Driver as a port, QueStub is no longer required. In fact GPS Intermediate Driver works better as it re-connects after a sleep cycle
Garmin Moble XT (and Others):
Garmin Mobile XT, refuses to use the GpsModPort to read gps data, it insists on using the original com port. QueStub is an application that changes the reg entries for the default gps port to the GpsModDriver port, runs the Que program, and restores the values back when Que exits. It is only 5 kb when sitting in memory.
Make sure at least one of these is set/exists before running QueStub.cab!
Code:
1) The 'QuePath' REG_SZ here: [HKLM\Software\Garmin\Que] the complete path to your gps program, "\Internal Storage\Garmin\QuePPC.exe" for example.
2) "\Garmin\Que.exe",
3) "\Internal Storage\Garmin\Apps\WM\QuePPC.exe",
4) "\Internal Storage\Garmin\WM\QuePPC.exe",
5) "\Storage Card\Garmin\Apps\WM\QuePPC.exe",
6) "\Storage Card\Garmin\WM\QuePPC.exe"
7) "\My Storage\Garmin\Apps\WM\QuePPC.exe",
8) "\My Storage\Garmin\WM\QuePPC.exe"
QueStub can be used for ANY ONE application, not just Garmin Mobile XT. Use it if your application insists on opening the original COM port, even when set to use GpsModDriver's port. Just insert your application into one of the registry as above.
Sure, good thinking.
I just have to say that this is going to pretty awesome! Be sure to have a donate link if this actually works to reduce/eliminate the percieved lag in gps software
0.4 version added to first post.
I liked the result overall with 2.8 seconds LagAdvance.
I have my mapping (Garmin Mobile XT) set for actual GPS position, and not stick to roads.
When turning, you appear to make a wide turn, going off the road a bit.
You appear to jump back a few meters when slowing while on a curve.
The perfect time of advance is not consistant, some times 2000 would be better than 2800. Find a good balance that works for you. Your phone may require a much different setting. Too big, and you appear to pass an intersection before you actually get there, too little, and you pass the interection before you appear to get there. Drive at a consistant speed, and straight during the adjustments.
Note that you must close your mapping program (realy close it, not let it run in the background), or change the port from the GpsModPort, before editing the registry, or any changes will not take effect.
Please report your results here.
Next up (besides fixing anything that goes wrong): Create a UI for the registry settings.
i try to install that and edit all of the registry and its success..
but, every time i change enable the com 6 in my garmin, it always change back to COM 4.. is it normal?
look my attachment for the video..
Garmin Mobile Xt requires a trick.
Make sure your external GPS settings are correct, I'll assume COM4, and the ModDriver at the default COM6.
Close XT, and then change this key:
Code:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Multiplexer]
"DriverInterface"="COM6:"
Unfortanatly you need to reset the external GPS settings to COM4, and then modify the key ater each soft reset. I have this 'patch' on my list of things to automate.
Would this work on the kaiser and titan?
It *should* work on ANY device, but see the CDMA Diamond comment on post 1...
Mach2003 said:
It *should* work on ANY device, but see the CDMA Diamond comment on post 1...
Click to expand...
Click to collapse
a bit confusing. for cdma users, hard reset, then install the driver? or install the driver, then hard reset?
sadthai said:
a bit confusing. for cdma users, hard reset, then install the driver? or install the driver, then hard reset?
Click to expand...
Click to collapse
No if you install this you will have to hardreset, or this does not work for cdma
Two users reported after installing this driver on a CDMA Diamond, they had to Hard Reset their phones. The driver did not load properly and CAUSED the need to hard reset the phone. They HAD to reset to 'factory' due to the driver appearing to lock up the device entirely on first boot.
Mach2003 said:
Two users reported after installing this driver on a CDMA Diamond, they had to Hard Reset their phones. The driver did not load properly and CAUSED the need to hard reset the phone. They HAD to reset to 'factory' due to the driver appearing to lock up the device entirely on first boot.
Click to expand...
Click to collapse
Now...
GSM Diamond,
CDMA Diamond,
other GSM phones, anyone ???
I use i-Mate ULTIMATE 9502 and this fix is AWESOME!!!!
altought it was returning to COM4..
it works great.. my gps signal is 0, but no lag at all in my diamond.. nice work..
I tried installing it for tomtom. but it did not work.
can someone post a short tutorial how to install this on tomtom?
Hi,
Since we alwas have to go into settings to make bluetooth visible for 120(?) seconds i was wondering if it is possible to make bluetooth always visible.
I found this guide: http://blag.tsukasa.net.au/2009/08/25/always-discoverable-on-android/
But it seems like hcid.conf is not present on 2.1 roms.
Can we get this to work on 2.1 roms?
Ty!
are you speaking from the pov of the hero being needing to be discovered by another device?
that isn't the sort of thing one needs to do more than one time per device though. once you've done it, the other device should remember the hero's info. just enable bt next time on both devices and voila, it should connect. right?
and there is the power control widget to enable/disable bt (along with other alternatives on the market and the sense toggle widgets if you're on a sense rom).
If you want your bt to be set to "discoverable" constantly then your battery will disappear really fast and it's a security risk as well (hence this feature doesn't exist in any bt device I've used including android). that's why apps like "bump" enable it only when, well, bumped, and in a way that both devices can talk briefly without user configuration necessary (but still user approval and instructions are needed before any file/secure info transfers can occur).
there's a difference between these three modes:
bt off (saves most power, bt is battery hungry...),
bt on (icon in display; can connect to devices that it has previously been paired with such as your bt handsfree or your computer for file transfers just be enabling the other device's bt - this puts it in sort of a receive mode where it will ack the other device to show itself but doesn't use a TON of battery, however it's still better for battery to turn off bt when not in use)
bt on and discoverable (which is, by bt design, only going to run for a short period such as 2 minutes because it opens up your device to others seeing it and trying to add it and also is transmitting over bt constantly so uses the most signal... 2 minutes seems pretty long to me actually, I've seen shorter in other devices).
I'm sorry, but that is just rubbish.
I've had Nokia's since bluetooth was first released, and they have always been discoverable. Their battery hasn't been worn down by that either.
If bluetooth is on but not discoverable, then your device is constantly looking for those devices that it has been paired with before. If it is discoverable, then other devices can pick up on this and locate your phone - same battery usage, surely.
Take for example now, I'm sat in a public area and I can search for devices. The devices that show up are therefore discoverable, no? In that case, plenty of devices are discoverable.
To be discoverable and hidden behind a password is no issue, and it amazed me that Android missed this out. It was infact one of the things I disliked about Blackberry.
It doesn't kill battery (any more than having undiscoverable bluetooth on), and it is a useful service - if a friend (who hasn't accessed my device before) wishes to send me a file, I don't expect to have to pull out my phone, tell it that it can expect a file, before accepting the password and waiting for said file. It's just an extra, unnecessary step.
What is the point of having bluetooth on, if no other device (other than those with previous access) can see it?
"Someone is trying to send you a file" is all you need. That is what happens in 'discoverable' mode. That is what Android is missing.
yes its a shame on x10 too is smart phone weakness. x10 kick a//
The setting you're searching for is in /system/etc/bluetooth/main.conf
DiscoverableTimeout = 0
The default is 120 (2 minutes). 0 will stay on forever.
Actually I found that in /etc/bluez/main.conf with root explorer but how to edit that value to 0?
VandaL^ said:
Actually I found that in /etc/bluez/main.conf with root explorer but how to edit that value to 0?
Click to expand...
Click to collapse
mount the folder as r/w and if you long press, choose to open in text editor
Tnx dude, I forgot to long press on file, what I did was open the file and than try to edit. But I've edited the value now to 0 or 600, reboot phone and when bt is on discoverable again shows only 120 seconds?
VandaL^ said:
Tnx dude, I forgot to long press on file, what I did was open the file and than try to edit. But I've edited the value now to 0 or 600, reboot phone and when bt is on discoverable again shows only 120 seconds?
Click to expand...
Click to collapse
Could you check if the value in the file also has been reverted?
I check instantly after I saw that he shows 120 seconds and the value was 0.
hi all
will you please show a step by step how to configure the bluetooth discoverable time.
thank you
Hello,
Like some of the other users, I had GPS problems after installing these two ROMs: connecting to the satellites took a very long time, if at all. Below I describe my fix, gathered from searching on the web, including here on XDA, and by using trial-and-error testing. Hope it helps others.
Install GPS Test by Chartcross. This helps monitor the GPS activities. There are other similar apps out there, but I like this one for the purpose of monitoring the GPS.
Install FasterGPS, by Dominik Schürmann. This is to edit the file /system/etc/gps.conf. You could edit it manually, but I like the GUI of this app.
Check if your /system/etc/suplcert/cacert.txt is "MIIDazCC......neEj8Nq/", then under the advanced settings, make sure SUPL_HOST is "supl.sonyericsson.com", SUPL_PORT=7275. Each cacert corresponds to a particular SUPL server. The above cacert is for the Sony server. If the host doesn't correspond to the cert, then you will not benefit from a quick retrieval of GPS info via the internet. Instead your GPS will download the info from the satellites themselves at a very slow rate (50 b/s according to Wikipedia). Your GPS would still work, but it won't acquire a fix quickly. Sorry I don't know what the cert for Google is.
Set NTP server to something close to you. Some people suggest to enter several servers (more can't hurt), some people suggest not to do that (more does hurt, if the previous ones fail.) I imagine that, at the higher level, the ntp pool servers don't usually fail. Thus I choose a single server that is close to me. In addition, I stay at the "country" level instead of going down to the numerical prefix level. (I.e. I don't bother with 0.uk.pool.ntp.org.) I figure going down to the numerical prefix level would more likely expose me to server failures.
Set INTERMEDIATE_POS=1 (enabled), then set ACCURACY_THRES=0 (passing all positions). With this value GPS Test usually reports satellites "in view" very quickly [<= 1 sec]. [Note: "in view" not "fix".] When I set the threshold to something non-zero (even a large value like 5000), it takes several seconds to see them.
Set ENABLE_WIPER=1, which supposedly turns on wifi positioning. Not sure what that does, but sounds like it can help . I assume the GPS system reads info from the wifi to get a rough estimate position. GPS Test probably isn't affected by this, although something like Maps might.
Set REPORT_POSITION_USE_SUPL_...=1. Again this sounds like a useful thing. My trial-and-error testing didn't discover anything conclusive about this. If anyone know more, please let me know.
Set DEFAULT_AGPS_ENABLE=TRUE, DEFAULT_USER_PLANE=TRUE. These are probably already true by default, but I figure it doesn't hurt to be explicit.
Reboot your phone if you had to change the SUPL setting. I had to do this to see the change. Would love to hear your experience on this.
With the above settings, GPS Test usually reports about 10 satellites in view in about 1 sec; satellites signals popping up above 10 db in about 5 sec, and the GPS acquiring a fix with about 4 satellites in less than 30 sec. All this _inside_ my house, which is a timber frame house with tile roof. I get this even with airplane mode on, i.e. no network connection!
If I use GPS Test to download AGPS data first, then the fix could be even faster, at less than 15 sec. And once the GPS has acquired a fix then, within a short time span, it will do so again very quickly (< 5 sec). Thus I have no problem as I switch from app to app and the GPS sensor turns on and off.
If my AGPS data is several days old, I still can get a fix in about 1 min.
Still, sometimes no matter what I do, the GPS would take more than 1 min to acquire a fix. Not sure why this happens, but it usually occurs after I haven't used the GPS in a while. In those cases I might have to wait up to 5 min for a fix.
Notes:
I assume you have root (since you managed to install ROMs )
According to the official ntp pool website,
As pool.ntp.org will assign you timeservers from all over the world, time quality will not be ideal. You get a bit better result if you use the continental zones (For example europe, north-america, oceania or asia.pool.ntp.org), and even better time if you use the country zone (like ch.pool.ntp.org in Switzerland)
Click to expand...
Click to collapse
More about my choice of accuracy threshold: if a threshold is active, it seems like the GPS would wait for the signal of a satellite to be of a certain strength before reporting it as in view. I figure it is better to just grab all the satellites possible, even if there is no signal yet.
The app GPS Status & Toolbox, by MobiWIA - EclipSim is also a very useful monitoring tool. I like the feature that reports how "stale" the AGPS data is. Wish GPS Test had this as well.
Toggling on the GPS from the settings menu simply allows apps to turn on the GPS. This doesn't use any battery. Only when an app starts using the sensor does it take energy. I recommend having this on. Having said that, do make sure you don't have any rogue app keeping your GPS engaged.
Install NTPSync, by Dominik Schürmann again. This helps set your clock. Not sure if this is necessary, but it gives me a good feeling that my clock is accurate
gps
its still not working
zivalarasa said:
its still not working
Click to expand...
Click to collapse
After running GPS Test out in the open for, say, 1 min, does it report any "in view" satellite at all? Any satellite have signal > 10db?
GPS Test
HHest said:
After running GPS Test out in the open for, say, 1 min, does it report any "in view" satellite at all? Any satellite have signal > 10db?
Click to expand...
Click to collapse
GPS test runs and doesnt find any sattellite. It ran for around 10 minz
zivalarasa said:
GPS test runs and doesnt find any sattellite. It ran for around 10 minz
Click to expand...
Click to collapse
I assume you had GPS working at some point prior to installing the ROM? If you've done all the steps (particularly steps 3, 5, and very importantly 9), then I'm afraid I'm out of suggestions.
spelling?
On the off chance... perhaps you have a spelling error?
I find it quite easy to spell "sonyericsson" wrong, especially the ericsson part. Now I have a way to memorize it: "Eric" (that's easy), "Eric's" (as in something belonging to Eric), ericsson = "Eric's son"
Hi!
This is a real problem making the phone almost unusable. It seems people had this kind of problem with older versions, but particularly with Oreo.
When my screen turns off (or is turned off) wifi seems to disconnect. I have a phone app working with my local PBX that immediately disconnects from the PBX system - although sometimes it doesn't. (It doesn't actively disconnect, but stops talking to the PBX and thus if you try calling it leads to an error unreachable in the PBX).
All other messaging apps like Whatsapp and Skype have similar problems - I get to the phone and turn it on only to get messages and missed calls from hours ago. Unusable.
Sometimes I can even see a little X next to the wifi symbol that disappears within a few second, sometimes the wifi symbol is missing altogether for a few seconds.
There is no more setting "keep wifi on during sleep" in Oreo. I disabled Battery optimisation for affected apps, I allowed background usage for them. The only thing I can't do is disable battery optimisation for wifi - which is displayed in the battery stats - but there is NO app "wifi" in app manager where I could flip this switch....
Any other ideas? I'm running AEX on the Note 5+. Thanks!!!
Seems like problem with kernel or maybe gapps, try different versions of gapps or kernel.
Oh, really? Gapps could affect that? How, why? It's getting insane. I wish there was an alternative to android phones - every time I need a new one it's months till it is fully usable and all for no good reason.
So far it sounds its the same problem many people report related to doze. "adb shell dumpsys deviceidle disable" should help as all the problems I have are described here:
http://forums.androidcentral.com/android-pie/904647-notifications-delayed-stopped-4.html
Unfortunately it doesn't seem to work on my system.
Just blurting this out here because matters have improved at least for the first minutes of screen off now...
I changed from "no notifications" on lockscreen to "show but hide sensitive info" and that seems to have improved things.
Really, a new phone system that doesn't work for what it's supposed to do - I'm not just speaking of delayed notifications - the worst part is that 3 voip apps and 3 messenger apps did not receive any calls when people tried calling me. The ONE thing a phone is supposed to do. UN-BE-LIEVABLE. It's so time somebody makes a proper Linux phone without focus on surveillance and spying. If it just worked as I need it to I'd pay up to 400 for it or 100 annually (just the OS!) - especially if I get requested features implemented and bugs removed.
Molvol said:
Hi!
When my screen turns off (or is turned off) wifi seems to disconnect. I have a phone app working with my local PBX that immediately disconnects from the PBX system - although sometimes it doesn't. (It doesn't actively disconnect, but stops talking to the PBX and thus if you try calling it leads to an error unreachable in the PBX).
Any other ideas? I'm running AEX on the Note 5+. Thanks!!!
Click to expand...
Click to collapse
Surprisingly, on Xiaomi devices some bugs are fw specific, means you face some weird bugs which are related to your firmware and not the system you are on. Try the latest 9.3.24 firmware from latest China, as I personally had the issue, I tried fixing it with different implementations but the bug was persistent, but I guess that issue seems to disappear every now and then when I use different firmwares. So give it a try!
AmulyaX said:
Surprisingly, on Xiaomi devices some bugs are fw specific, means you face some weird bugs which are related to your firmware and not the system you are on. Try the latest 9.3.24 firmware from latest China, as I personally had the issue, I tried fixing it with different implementations but the bug was persistent, but I guess that issue seems to disappear every now and then when I use different firmwares. So give it a try!
Click to expand...
Click to collapse
So you mean I should flash the latest MIUI China developer? And it will rewrite special partitions (like Modem) that other ROMS don't touch and therefore afterwards I may not have issues any more? Can I flash this with TWRP or something else and do I have to re-unlock afterwards or re-install TWRP? Thanks!!
Facing the same problem and can't fix the issue with anything.
I have a similar problem with the factory rom and firmware, so if I read it right, I have to flash another firmware?
i have the same problem, even flashing fastboot rom and going back to pie didn't fix it.
Same, it happened sometimes in Oreo, but is all the time in Pie.
Tried everything, but seems like a Xiaomi wide modem problem.
any updates? i have this issue too.. is "hide sensitive info" thing still works on yours?
So I have somewhat improved my problem with editing the wifi configuration file. People have this problem on the Pixel as well - it's partly an Android problem. It's so time somebody forks that **** from Google - they don't know what they are doing - and makes something stable for a phone to work like a phone should.
https://forum.xda-developers.com/oneplus-5/themes/magisk-pixel-2-wifi-mod-t3752321
For me the solution there didn't work at all, kept crashing. My current WCNSS_qcom_cfg.ini i copied from my LG G3 and it works much better, it now takes about 15min until it's dead, but the first call will wake it up now, so that a second one makes it ring. Still unusable and ridiculous, but at least it doesn't turn off with the screen.
This is how mine looks now:
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
# 0 implies no periodic wake up from IMPS. Periodic wakeup is
# unnecessary if Idle Scan is disabled.
gImpsModSleepTime=0
# Enable BMPS or not
gEnableBmps=1
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
# Phy Mode (auto, b, g, n, etc)
# Valid values are 0-9, with 0 = Auto, 4 = 11n, 9 = 11ac
gDot11Mode=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# Assigned MAC Addresses - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
Intf0MacAddress=000AF58989FF
Intf1MacAddress=000AF58989FE
Intf2MacAddress=000AF58989FD
Intf3MacAddress=000AF58989FC
# Set/Clear UAPSD mask
UapsdMask=0
# UAPSD service interval for VO,VI, BE, BK traffic
InfraUapsdVoSrvIntv=0
InfraUapsdViSrvIntv=0
# Flag to allow STA send AddTspec even when ACM is Off
gAddTSWhenACMIsOff=1
# Make 1x1 the default antenna configuration
gNumRxAnt=1
# Beacon filtering frequency (unit in beacon intervals)
gNthBeaconFilter=50
# Enable WAPI or not
# WAPIIsEnabled=0
# Flags to filter Mcast abd Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast abd Bcast
McastBcastFilter=0
#Flag to enable HostARPOffload feature or not
hostArpOffload=1
hostnsoffload=1
#SoftAP Related Parameters
# AP MAc addr
gAPMacAddr=000AF589dcab
# 802.11n Protection flag
gEnableApProt=1
#Enable OBSS protection
gEnableApOBSSProt=1
#Enable/Disable UAPSD for SoftAP
gEnableApUapsd=1
# Fixed Rate
gFixedRate=0
# Maximum Tx power
# gTxPowerCap=30
# Fragmentation Threshold
# gFragmentationThreshold=2346
# RTS threshold
RTSThreshold=2347
# Intra-BSS forward
gDisableIntraBssFwd=0
# WMM Enable/Disable
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=0
# CCX Support and fast transition
EseEnabled=0
FastTransitionEnabled=1
ImplicitQosIsEnabled=0
gNeighborScanTimerPeriod=200
# default value of this parameter is zero to enable dynamic threshold allocation
# to set static roming threshold uncomment below parameter and set vaule
#gNeighborLookupThreshold=78
gNeighborScanChannelMinTime=20
gNeighborScanChannelMaxTime=30
# Legacy (non-CCX, non-802.11r) Fast Roaming Support
# To enable, set FastRoamEnabled=1
# To disable, set FastRoamEnabled=0
FastRoamEnabled=1
#Check if the AP to which we are roaming is better than current AP in terms of RSSI.
#Checking is disabled if set to Zero.Otherwise it will use this value as to how better
#the RSSI of the new/roamable AP should be for roaming
RoamRssiDiff=5
# SAP Country code
# Default Country Code is 2 bytes, 3rd byte is optional indoor or out door.
# Example
# US Indoor, USI
# Korea Outdoor, KRO
# Japan without optional byte, JP
# France without optional byte, FR
#gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
gShortGI40Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
# SAP auto channel selection configuration
# 0 = disable auto channel selection
# 1 = enable auto channel selection, channel provided by supplicant will be ignored
gApAutoChannelSelection=0
# Listen Energy Detect Mode Configuration
# Valid values 0-128
# 128 means disable Energy Detect feature
# 0-9 are threshold code and 7 is recommended value from system if feature is to be enabled.
# 10-128 are reserved.
# The EDET threshold mapping is as follows in 3dB step:
# 0 = -60 dBm
# 1 = -63 dBm
# 2 = -66 dBm
# ...
# 7 = -81 dBm
# 8 = -84 dBm
# 9 = -87 dBm
# Note: Any of these settings are valid. Setting 0 would yield the highest power saving (in a noisy environment) at the cost of more range. The range impact is approximately #calculated as:
#
# Range Loss (dB) = EDET threshold level (dBm) + 97 dBm.
#
gEnablePhyAgcListenMode=128
#Preferred channel to start BT AMP AP mode (0 means, any channel)
BtAmpPreferredChannel=0
#Preferred band (both or 2.4 only or 5 only)
BandCapability=0
#Beacon Early Termination (1 = enable the BET feature, 0 = disable)
enableBeaconEarlyTermination=1
beaconEarlyTerminationWakeInterval=8
#Bluetooth Alternate Mac Phy (1 = enable the BT AMP feature, 0 = disable)
gEnableBtAmp=0
#SOFTAP Channel Range selection
gAPChannelSelectStartChannel=1
gAPChannelSelectEndChannel=11
#SOFTAP Channel Range selection Operating band
# 0:2.4GHZ 1: LOW-5GHZ 2:MID-5GHZ 3:HIGH-5GHZ 4: 4.9HZ BAND
gAPChannelSelectOperatingBand=0
#Channel Bonding
gChannelBondingMode24GHz=1
gChannelBondingMode5GHz=1
gEnableModulatedDTIM = 3
gMaxLIModulatedDTIM = 3
gEnableDatainactivity = 200
#Enable Keep alive with non-zero period value
gStaKeepAlivePeriod=30
#Say gGoKeepAlivePeriod(5 seconds) and gGoLinkMonitorPeriod(10 seconds).
#For every 10 seconds DUT sends Qos Null frame(i.e., Keep Alive frame if link is idle for last 10 seconds.)
#For both active and power save clients.
#Power save clients: DUT set TIM bit from 10th second onwards and till client honors TIM bit.
#If doesn't honor for 5 seconds then Driver remove client.
#Active clients: DUT send Qos Null frame for 10th seconds onwards if it is not success still DUT try on
#11th second if not tries on 12th and so on till 15th second. Hence before disconnection DUT will send 5 NULL frames.
#Hence in any case DUT will detect client got removed in (10+5) seconds. i.e., (gGoKeepAlivePeriod +gGoLinkMonitorPeriod)..
#gGoLinkMonitorPeriod/ gApLinkMonitorPeriod is period where link is idle and it is period
#where we send NULL frame.
#gApLinkMonitorPeriod = 10
#gGoLinkMonitorPeriod = 10
#gGoKeepAlivePeriod/gApKeepAlivePeriod is time to spend to check whether frame are succeed to send or not.
#Hence total effective detection time is gGoLinkMonitorPeriod+ gGoKeepAlivePeriod/gApLinkMonitorPeriod+ gApKeepAlivePeriod.
gGoKeepAlivePeriod = 10
gApKeepAlivePeriod = 30
#If set will start with active scan after driver load, otherwise will start with
#passive scan to find out the domain
#gEnableBypass11d=1
#If set to 0, will not scan DFS channels
gEnableDFSChnlScan=1
gEnableLogp=1
# Enable Automatic Tx Power control
gEnableAutomaticTxPowerControl=0
# 0 for OLPC 1 for CLPC and SCPC
gEnableCloseLoop=1
#Data Inactivity Timeout when in powersave (in ms)
gDataInactivityTimeout=200
gEnableLpwrImgTransition=1
# Scan Timing Parameters
# gPassiveMaxChannelTime=110
# gPassiveMinChannelTime=60
# Enable Tx LDPC
#gTxLdpcEnable = 1 for HT mode, 2 for VHT mode,3 for both HT and VHT
gTxLdpcEnable=3
# gActiveMaxChannelTime=40
# gActiveMinChannelTime=20
# Valid values are 2048,4096,8192 and so on
# Please don't use values other than the ones mentioned above
gMaxMediumTime=4096
# 802.11K support
gRrmEnable=1
gRrmOperChanMax=8
gRrmNonOperChanMax=8
gRrmRandIntvl=100
#Scan offload
gEnableDirectedScanOffload=0
#FlexConnect Power Factor
#Default is set to 0 (disable)
gFlexConnectPowerFactor=0
gVhtChannelWidth=2
# VHT Tx/Rx MCS values
# Valid values are 0,1,2. If commented out, the default value is 0.
# 0=MCS0-7, 1=MCS0-8, 2=MCS0-9
gVhtRxMCS=2
gVhtTxMCS=2
# Enable Tx beamforming
gTxBFEnable=1
#Enable/Disable TDLS Feature
gEnableTDLSSupport=1
#Enable/Disable TDLS Implicit Trigger
gEnableTDLSImplicitTrigger=0
#Enable/Disable TDLS WMM Mode
gEnableTDLSWmmMode=1
#Enable/Disable TDLS Buffer Sta
gEnableTDLSBufferSta=1
#Enable/Disable Mgmt Frame Logging
gEnableMgmtLogging=1
#Enable/Disable MAc Spoofing
gEnableMacAddrSpoof=1
#Set RPS CPU mask
rps_mask=0f
# wifi ping test
gEnableDynSplitScan=0
gEnableLLStats=1
#Enable Power Save offload
gEnablePowerSaveOffload=1
isandroidpsen=1
END
# Note: Configuration parser would not read anything past the END marker
I have the same problem
Is there any fix j had tried to flash fm but nothing
The problem still not fixed
i wonder if it's related with router. What are yours? Mine is huawei hg630a and i also didn't try another wifi yet. But it's working good with miui roms..
Mine is ZTE and I don't think it's related to router
I think it related to fm or rom or modem
I don't know
mahmoud ayman said:
Mine is ZTE and I don't think it's related to router
I think it related to fm or rom or modem
I don't know
Click to expand...
Click to collapse
i tried almost every aosp pie rom and firmwares but nothing changes. (redmi 5 plus)
And I tried most Oreo Roms I could find. I did get different behavior with different routers/Wifi APs, but that only proves that the phone really has a problem. ALL other devices I tried have no problem whatsoever with any of these (Samsung, LG, Sony...). It's is not a hardware problem (in the sense that it can't be fixed by a setting). The problem is known to thousands of people struggling with android phones - although some are just similar, not identical.
We only need to find the right setting, maybe in the WCNSS_qcom_cfg.ini or possibly related to kernel/power management. Unfortunately I have not found proper documentation about either of these. Could also be a modem setting, but that is even more obscure and less documented. We either need incredible luck randomly trying things or someone who knows their way around android qualcom hw interaction.
i enabled gps and no problems with wifi while screen is locked. Tested it for 2 days. (9.4.11 firmware, twrp 3.3.0, gapps mini, resurrection remix and viper both works fine so other ones should too.)
hi, i actually have the opposite problem. i want to my wifi to go off auto when the phone goes off (the screen) not the mobile data but the wifi so i can always have connection but save battery with the wifi.
My phone's battery seems to barely get to 12 or 14 hs in a normal (to low) use. and ending the day with no battery at all, i had a samsung that get me to the night with 50% or even more most days. and i remember to have the option on wifi setting to turn wifi off when phone sleeps to save battery. any suggetions?
Hi, I have a Samsung S5, however, I think that it's a problem universal to a lot of Android phones (6 months+ googling on issues that ultimately seem to be caused by the wifi being switched off and going through xda threads for so many different phones). Eventually I found that my (CM based) ROM installation (Resurrection Remix 7.02) seems to be missing (or more likely has dispersed the relevant files into other locations) the /system/csc folder.
I found a thread on android central from a user alexceltare2 suggesting a line to add to /system/csc/others.xml (or features.xml if that exists) which is:
<CscFeature_Wifi_SupportAutoReconnect>TRUE</CscFeature_Wifi_SupportAutoReconnect>
I added this folder from an old ROM installation I happened to have (and modified the file content to remove the old ROM references) with a root file explorer to get the csc folder, added that line to my now existing features.xml file, rebooted and found I went from wifi sleeping after ~15 minutes or so to 7+ hours of wifi stability.
I don't know whether this helps anybody but I haven't found many references to missing csc folders or the features/other.xml files.