Related
I just want to warn everyone the 2003 rom has many problem, since it is an internal development version. Here is the bugs I found right now.
1.Maybe it's not a "BUG". It miss the Wireless Modem which many people asked for a long time.
2.I tried Windows Media Player and Pocket Music 1.5, both can't turn off the display, which means you have to leave the display on when you listen the music. If any one can turn off the display , please tell us, may be I got some software conflicted.
3. 2 "Power" Logo on the setting menu, but the have different content. It looks like one is the new power setting tab, but it didn't provided some old fuction in the old power setting tab, so O2 kept the old one.
4. The SIM Contacts (Sim utility provided by PPC 2003) is horrible.It has NO fuction except copy the SIM card address to the phone.
5. YOU MUST NOT install Batterypack 2003 on the phone. It looks like working after you install, but your machine will never boot up after a soft-reset except hardreset the phone. (It is PPC 2003 / Battery Pack 2003 problem, not O2 / HTC's fault).
6. You will never know if the current signal support GPRS or not. It will not display the G logo in the "signal bubble".
Please add the list if you got any problem with the new rom.
If the bug I listed can't stop you install the new rom, go ahead :twisted: .
Moreover, it's not an official / final version rom, if you want stable rom, stay with XDA SE 1.1 rom.
Sorry for my horrible english~
1.Maybe it's not a "BUG". It miss the Wireless Modem which many people asked for a long time.
Click to expand...
Click to collapse
Not a bug. it was a feature added by xda-developers.
2.I tried Windows Media Player and Pocket Music 1.5, both can't turn off the display, which means you have to leave the display on when you listen the music. If any one can turn off the display , please tell us, may be I got some software conflicted.
Click to expand...
Click to collapse
tried it with windows media player and got the same thing. Pocket music 2.0 refuses to work at all
6. You will never know if the current signal support GPRS or not. It will not display the G logo in the "signal bubble".
Click to expand...
Click to collapse
when i have grps signal i have G displayed in my bubble.
Alex
kalex said:
1.Maybe it's not a "BUG". It miss the Wireless Modem which many people asked for a long time.
Click to expand...
Click to collapse
Not a bug. it was a feature added by xda-developers.
Click to expand...
Click to collapse
No, it was added in the new ROMs by Qtek and O2. Whether it's a Microsoft or HTC tool I don't know, but it's definitely not ours...
XDA developer Peter Poelman,
didn't know that. i thought it was urs.
PPC 2003
Hi all
Only autentization to VPN over cetificates is good feature for me.
Another features :?
XDA-dev ROM 1.1 is best solution
It seems the "screen toggle" bug (can't switch off the screen probelm) can be fixed by install the PocketMusic 2.0 Bundle plus the 2.0_4_3 fix.
I can see a hotkey to turrn off display with 2.0 version.
Moreover, the "auto turn off display" fuction still works on the PocketMusic 1.5 Bundle version, and 2.0 too.
It's so strange the PocketMusic 2.0 works but WMP 9.0 doesn't work.
I'm happy with the PPC2003 now. If we have to wait to long beforce the official release, will XDA-Developer release an extra SE version based on the current version of PPC2003?
It still suffers fron some sms issues, i cant get a delivery receipt, and also the time sent stamp is actually the time received.
The auto config does not work, so as a result i can't get gprs working...
(Anyone know the settings for o2 uk ?)
All in all though a good upgrade !!
i loaded the 2003 rom and only have minor issues.
1. when connecting the network says voicestream instead of t-mobile.
2. connection seems slower even with the accelerator proxy turned on. the connection used to be as high as 40k according to spb gprs monitor. now i haven't seen it break 20k.
Unit no longer powers-on when placed in sync cradle; In order to sync the unit I now have to either (a) make sure unit is turned-on before placing it into cradle, or (b) place powered-off unit in cradle, then turn power on.
Not a major issue, but certainly a back-step in functionality. Anyone else notice this?
I'm using a TMobile XDA with updated ATT radio stack and PPC2003.
To Dondi :
I have your issue too, but I didn't think it is a problem for me, since I hate the machine suddenly power on itself when I am charging it.
i guess it s even better for the screen not to be lighted all the time when plugged on the cradle
Hey all. I just installed WM2003 PE. It looks and feels great. I only have the following comments:
I have installed the ROM on my Qtek 1010.
1. I can't seem to see any MIDI ringtone support on this one (probably because it's not a final release)
2. I'm still running on my old Radio Version 3.23 and my GPRS resumes connection seamlessly after calls - which is great.
3. I've read somewhere that applications will be visible on the 'taskbar' when running, but do not get this functionality also. No worries on this though, because 'Switch' works fine with WM2003.
4. Still no ability to add custom Operator Logos.
5. Hooray for the 'Busy' tone and indication!
SPB GPRS Monitor works fine with 2003. I also wanted to know from the rest of you guys: Do you have to manually initiate GPRS connectivity after a soft-reset? Or does it pick up your default connection and auto-connect?
To killercheung and Cyberb0b: You've given me a new perspective on the XDA not automatically switching on when placed in the cradle in the off state -- I appreciate the benefits you pointed out.
Also, I did notice that when I initially loaded the Ozone beta (prior to upgrading radio stack) the GPRS symbol was being displayed regularlyand I had no problem connecting with GPRS and getting decent performance (> 20 Kbps). However, after I convinced myself to "go all the way" and also perform the Radio Stack update, I now rarely see the GPRS symbol, and GPRS perfirmance has dropped to the 1Kbps level.
Now I wonder if Ozone also updated the radio (which I perhaps subsequently "downgraded" by loading the ATT RSU). Can anyone shed some light on this?
for what i ve seen Ozone does not modifiy the radio stack, you have to upgrade it yourself useing for exemple the O2 upgrade version 4.21.
As far as i m concern using GPRS in France with Orange as operator with SE 1.1 or with ozone i have the same brandwith capacity depending on the network trafic and my position, between 10 and 30 Kbps, i use SPB GPRS manager to monitor my connexion 24/7 and see what is my data consumption day by day (it also allow me to shut GPRS off without switching the phone off).
by now using ppc2003 for about a week, i have no gprs shut down, except going out of coverage area, we poor french are not full gprs anywhere, but it works pretty good in cities.
on thing i ve notices that i guess is significant :
however it is said that Gprs connexion isn t dropped any more when an incoming CSD call start, that is true but the transmissions are stopped.
I mean i can not send or recieve data while talking on the phone line. But this is not due to the software i guess it is due to the number of channels aviable on the device usually it s 4 + 1 or 4 + 2
whereas phones like SE P800 have 6 + 4 channels allowing the to really exchange data while using CSD channel.
But nevertheless it is a good upgrade cause i do not have to kill my irc session while talking on the phone (just have to hang up fast before the irc timesout ) ).
New Rom for ATOM EXEC's available
Introduction
This System Software Upgrade consolidates all the new and previous enhancements and fixes into a single ROM upgrade image. O2 encourages Xda Atom Exec users to upgrade their devices to the following system software.
English ROM
ROM: 20060721B1WWE
Radio: R060711N_MN2ARC_RS00011
ExtROM: EX0033
This System Software Upgrade provides software fixes and improvements for MMS, camera, FM radio, SMS applications.
You can check the core software versions running on your device by going Start > Settings > System > System Info.
Benefits of upgrade include:
• Adds MMS Error Resilient support to MP4 codec for MMS application.
• Adds AIS WAP setting changes to AutoConfigurator application.
• Adds delete email function to Setup Wizard application.
• Adds 9600bps v.110 CSD dialup support.
• Adds new power save mode for FM Radio application. Pressing the power key will put device into power save mode (CPU in sleep mode) to achieve maximum power saving. In power save mode, user can listen to FM radio but device will not respond to any keypress except the power key. Pressing the center action button on the dPad will switch LCD off but device will still remain in IDLE mode (CPU in normal running state). In IDLE mode, user can use the dPad to control FM radio control functions.
• Adds Digital Right Management level 5 (DRM5) support for DRM-protected eBook content.
• Updates O2 Plus to version 2.1.
• Fixes an SMS bug that occurred when sending a long and concatenated text message. This could cause corruption of some part of the sent message.
• Fixes incorrect GPRS status display in Wireless Manager.
• Fixes playback issues with certain MMS content.
• Fixes hang issue when device is about to go into power save mode while camera is still loading.
• Fixes FDN behaviour which now requires PIN2 to be input when modifying the fixed dial number list.
• Fixes a bug that may cause the phone to malfunction when device is in roaming network and network selection is changed between automatic and manual.
source:http://www.seeo2.com/user/XdaAtomExec/template/XdaAtomExec_ROMUpgrade_Aug2006_WWE.vm
enjoy!
problems with the new O2 atom exec rom...
well quite noticeable till now...
The phone coverage becomes poor with the new radio. It was better with the last one that came alongwith...
The speakerphone(loudspeaker) doesn't work quite well. The other party hears noise.
The mic level is quite low. I need to speak while taking the phone close to my mouth.
I am not sure whether the last 2 problems is with the new rom but the phone's reception for sure has worsened... :-(
Can't seem to download the file.
Login failure.
Any kind souls please help to upload somewhere else for download?
Thanks in advance.
Atom Upgrade
The site was slow but I finally got it downloaded. I have not had the radio issues mentioned above. I can't really see any big changes that make this a required upgrade either though. :?
Anyone kind enough to share English ROM for EXEC?
My boss brought a Chinese Version ATOM EXEC and is asking me to help him upgrade to English. Cannot download from O2 Offical Site.
Thanks a lot
I thought everyone had the "search" tab on the screen 8) 8)
Anyone plan on trying to get the captivate gps fix and try to monkey it into the fascinate?
My current thinking on the captivate GPS fix is this, the fix was not listed in the released list of bug fixes in the update. The update that has been announced for the fascinate ( http://tiny.cc/lfrxi ) does not list the GPS fix either. But im thinking that if its included in the captivate update...?
Samsung and AT&T have both pretty clearly stated that the Captivate update does in fact include improvements to the GPS.
"An update to improve the Samsung Captivate's GPS performance is now available. Captivate customers will receive a notification on their device that an update is available and will simply need to download the file to update their phone. The updates will be pushed to customers' devices over the next few weeks.
The update for the Captivate will also improve additional device functions, such as media scanning time, add the full version of Quickoffice and address Microsoft Exchange 2003 policy support."
Click to expand...
Click to collapse
As far as assuming our update will include a gps fix... i doubt it giving how different the handsets are for each carrier.
I'm going to guess you'll see the same GPS fix. If you look at the update features, it looks almost identical to the one for the Captivate. I'm guessing the basic guts of the update are identical, but it's tweaked to account for the customized apps and other bloatware by each individual carrier. I mean, why would a GPS fix be different for the Captivate vs. Fascinate?
The radio is different, but I dont know how important that is to the GPS receiver. If it is integrated to the radio then it could be different enough to warrant a different update.
[FIX]◊[JVK]◊ PlumbBob GPS Fix [UPDATE 4/10/2011] <Insert unfunny Bob joke here>
UPDATE: plumbBob GPS Fix for Captivate v2.0 BETA 11 [JVK] is now available for testing
http://forum.xda-developers.com/showthread.php?p=12761703#post12761703
UPDATE: plumbBob GPS Fix for Captivate v1.1 RC1 is now available for testing
http://forum.xda-developers.com/showthread.php?p=12781991#post12781991
In short, I've managed to get the GPS running as well as I can, at least given the tools and sources available to me. Version 1.0 of the fix is now believed stable and effective on all platforms and ready for release.
Problem Summary:
Hardware:
- The Samsung Galaxy S series (and the Captivate in particular) make several design compromises to fit the superslim candybar form factor, some of which tend to limit GPS performance. Among them are the use of a very small patch antenna located in a less-than-optimal position (behind/underneath) as the primary antenna. The effect of this is worsened by an under-engineered attempt to use the aluminum battery door (of suboptimal size and material for this role) as an auxiliary antenna, a problem worsened by using only a weak hinge spring as the connection. In a nutshell, the Broadcom BCM4751 GPS chip itself might potentially be capable of very acceptable performance, but Samsung's design and implementation cripples it badly. There's quite little we can do about any of this, and many previously published hardware hacks risk permanent damage to the phone.
- Design and/or manufacturing faults may cause potentially problematic levels of electromagnetic interference (EMI) within the housing and/or lead to intermittent power starvation of the GPS unit (this hypothesis gains credence since GPS performance is frequently improved by plugging in to a car adapter) . Additionally, strategies for managing GPS processes and CPU load seem under-optimized with GPS processes not being properly prioritized. There's quite little we can do about any of this either, especially with the driver being closed source.
Software and Configuration:
- Samsung's drivers are proprietary closed source, greatly limiting the ability to date of open source developers to improve GPS performance. Since Samsung receives the chips from Broadcom sans driver and with only an SDK, this might be reasonable and tolerable ̶— if the drivers actually worked. However, nothing that can be done about this short of hoping for a leak or some other misplaced miracle.
- The stock Samsung driver and configuration does not make use of WAAS augmentations at all even though the chip is actually capable of utilizing WAAS. Modern WAAS-capable receivers are typically capable of at least <3m accuracy but SGS users seldom see accuracy of even 5-10m. Again, closed source driver = nothing can be done about this.
- The stock Samsung/AT&T configuration for the GPS settings is horribly, laughably, and inarguably flawed. The out-of-box configuration is essentially incapable of ever allowing acceptable AGPS-aided performance. This fix attempts to remedy the flawed configuration settings.
- In a slim mobile phone application AGPS (Assisted GPS) augmentations are not just optional performance enhancers. Indeed, AGPS augmentation is fairly necessary for a GPS receiver with such a small under-optimized antenna as once AGPS data is loaded weaker signals can be utilized. This fix attempts to make sure the AGPS augmentations are properly downloaded and implemented.
Description:
plumbBob GPS Fix uses a markedly different strategy from most previously released GPS fixes, most of which attempted to turn off some of the various augmentations and improvements to the raw GPS position data like AGPS and position smoothing. These strategies apparently operated under assumptions that the implementation of these features was simply too flawed to be useful and that eliminating these features would feed only "pure" data to apps instead.
It seems however that these features may have been more necessary than had been assumed. Since with previous fixes many users could get satisfactory stationary fixes but unsatisfactory tracking on the move, I decided some of the "purification" feature-deactivating strategies used by previous fixes might be instead feeding unusably "jittery" location data to the navigation app, confusing the app and causing some of the weird tracking errors many of us were getting.
Many previous fixes also focused inappropriately only on one or a few areas where configuration settings might be applied. Instead, plumbBob attempts to present a "whole solution" answer to the problem rather than hoping that a single magic bullet might do the trick reliably.
The plumbBob GPS fix has two primary goals:
- Make configuration changes to get the necessary AGPS augmentations working properly to allow the device to function as its designers presumably hoped for, and
- Reduce the mobile tracking errors that seem to persist under most previous GPS fixes
Features:
- Updated GLGPS daemon binary from Nexus S Gingerbread (which is also same as UCKB1 AT&T stock Froyo)
- Updated shared object libraries from stock UCKB1 release
- Official AT&T certificate file (usually omitted in most custom ROMs adapted from non-AT&T platforms) to allow Secure SUPL for security & privacy
- Regionalized NTP (internet time sync) server configuration for improved TTFF (Time to First Fix) performance
- Tweaks to configuration files needed to allow proper download and application of AGPS augmentations and improved mobile tracking
Supported Platforms:
- Captivate only, at least for now. In initial testing some Vibrant testers managed to successfully implement this fix with good results, but others experienced some fairly major problems. There are some important differences in the GPS handling on the different Galaxy S variants that may limit the effectiveness of this fix on other platforms. For instance, the Vibrant uses the AGPSD daemon for GPS handling but for some inexplicable, inscrutable reason the Captivate uses GLGPS instead even though they both use the same BCM4751 chip. And then the Galaxy S I9000 series uses a completely different chipset (Broadcom BCM20751) that includes Bluetooth and FM radio. Configuration interfaces vary considerably between the various models and as such installation on any other platform can only be undertaken completely at your own risk. Developers interested in porting and testing the plumbBob GPS Fix for other platforms are encouraged to contact me by PM.
Changelog:
See 2nd post.
Thanks to Da_g, CLshortfuse, and Adam Holden/Team Phoenix for their previous work that guided my research. And many thanks to the many testers who weathered my mistakes and contributed to the final product.
IMPORTANT: LbsTestMode settings must be manually updated as well!
SUPL/CP Settings: Server FQDN = Custom Config, Server: supl.google.com, Server Port: 7276, SUPL Secure Socket = ON, AGPS Mode = SUPL
Application Settings: Tracking, S/W Test, MS Based, Hot Start, GPS Plus = On, Dyn accuracy = on, Accuracy = 40, GPS logging = off
Installation Instructions:
Download the appropriate .zip for your region
BEFORE FLASHING - Use LbsTestMode to apply new SUPL/CP and Application Settings (see above) and delete GPS data
Copy to /sdcard/ root and flash using CWM recovery
Ensure Settings -> Location and Security -> Use GPS Satellites is ON
Ensure Settings -> Location and Security -> Use wireless networks is ON
Note: If your country or region is not listed or if you need to change regions while traveling etc., the easiest way to customize the NTP setting as needed is to use the free Faster Fix app from the market.
Note: At present Southern California is still located in the USA.
CAUTION: Though it works great for some, Serendipity 6.0+ and above DOES NOT seem to work well with plumbBob 1.0 for all users. I don't know if it's related to the JS7 base or Serendipity-specific customizations, but several Serendipity users have reported that this fix pretty much wrecks GPS. I'm continuing to look into it and hopefully future versions of this fix may be compatible. And FWIW in my testing I actually had very acceptable GPS performance using stock Serendipity 6.0 settings, so this fix is probably less necessary anyway....
The most recent stable version 1.0 is below. Advanced users who might wish to try out the latest 2.0 Beta version instead may get it at http://forum.xda-developers.com/showthread.php?p=12761703#post12761703
Changelog
Development/Discussion
irc.freenode.net
#plumbBob
Changelog
0.8.2b - Initial public beta release
Replacement GLGPS daemon binary from Nexus S. Thanks to Da_G
Modified jupiter.xml
Enabled position smoothing to help reduce tracking errors
Re-enabled SUPL augmentation
Dynamic Operation Mode set to Automatic
Remove large chunks of unhelpful commented-out debugging code to help speed load time during GPS initialization
Include secgps.conf
Set operation mode MS Based
Include NTP and gpsonextra configuration in gps.conf
0.8.3b
Added regional localization for NTP (Network Time Protocol time synchronization) servers in gps.conf to improve speed and accuracy of time sync, especially for international users. This was reported by many users especially in Europe to improve speed of initial acquisition (TTFF). For best performance download the version for your region, or if your region isn't listed or you frequently move between regions use the GLOBAL version. [This is also the same thing that the "GPS Fix" option in SGS Tools does but provides options besides North America and Europe.]
0.8.4b
added supl.google.com configuration lines to gps.conf. Another fix I found tried this with some apparent success and it really can't hurt. Performance seems roughly the same.
Add the SSL certificate file copied from stock JF6 to /system/bin/gpsd/supl_att_root.cer. This is the certificate used for Secure Socket SUPL connection. This seems to be missing in most to all of the ROMs not based on AT&T code and adapted from Non-AT&T carriers (i.e., pretty much 100% of them). This should allow SUPL secure socket to be used for better security and privacy, but can still be disabled by user with LBSTestMode if performance degrades. Secure SUPL must be enabled in LbsTestMode to be activated!
0.9
0.9:
- updated libsecgps.so from KB1 leak
- updated jupiter.xml from KB1 leak
- updated secgps.conf from KB1 leak
- glgps daemon in Nexus S is the same as KB1, retained
0.91
0.91
- changed operation mode in secgps.conf to MSBASED
- modified jupiter.xml:
* deleted extraneous, commented-out anyway debugging documentation markup
* corrected path to supl certificate to /system/bin/gps/ vs. /system/bin/gpsd/
0.93
0.93
- Fixed /system/bin/gpsd folder name bug
- changed permissions for shared libraries in install script
- tweaks to help reduce jitter and reduce road snapping errors in mobile tracking incl. dynamic accuracy, stop forcing pedestrian, MS Based operation mode
- added additional driver library copied from I897UCKB1 to (maybe) help backward- and cross-platform compatibility
0.94 (Withdrawn)
Withdrawn.
0.942
0.942
-Bug repairs from 0.94(since withdrawn)
- jupiter.xml
- decided Da_g was right and re-enabled forcing pedestrian mode for most frequent location updates
- configured to use supl.google.com instead of 3GPPnetwork.org
- secgps.conf
- changed to supl and port settings to google
1.0
1.0
- enabled PPS (Pulse Per Second) Mode in Jupiter.xml. This is (or would be) a highly accurate means for providing timing control within the unit, but although the chip seems capable it's not clear if the drivers actually make use of it
- increased the WarmStandbyTimeout times to 3 and 6 seconds to help reduce drops
- used a different method of signing the .zip that should (hopefully) allow it to be installed on systems using stock kernels by renaming to update.zip and choosing "reinstall packages" from recovery
2.0 BETA 1
- port of GPS files and new configurations from JV1 Gingerbread for I9000 leak
- improved everything pretty much
Control Plane:
I have continued to experiment with adding the Control Plane supplement (ie using the cell towers' own organic time and location services for controlling call handoff between towers etc.) but in testing I still can't get consistently improved results. For this reason I have decided to not make any changes to the configuration for now. If anything adding Control Plane often seems to degrade acquisition times and # of birds initially acquired slightly, which could indicate that it's not working at all and simply introducing a timeout delay. Or it might just indicate that it doesn't work very well. It's another one of those things that's hard to sniff out inferentially in the absence of GPS driver source, SDK etc.
I did manage to discover that there's even a whole separate control app for implementing Control Plane augmentation. Yes, in yet another example of Samsung's consistently, laughably, schizophrenically fragmented implementation of the GPS controls, there's yet another undocumented place to change settings. No wonder it doesn't work for so many.
I have left the control plane method allowed as an option in the configuration files supplied with PlumbBob 0.8.4b, so users who are still not getting satisfactory GPS performance might experiment with adding Control Plane augmentation by doing the following:
OPTIONAL/EXPERIMENTAL PROCEDURE FOR ACTIVATING CONTROL PLANE SUPPLEMENT:
Open LbsTestMode by using SGS Tools, select "secret codes" and then choose LbsTestmode OR use the phone dialer to enter *#3214789650#
Select "SUPL/CP Settings"
Under AGPS Mode choose "Control Plane" from the dropdown
Open the phone dialer and enter *#1575#
Choose "CHANGE CP STATUS"
Choose "CONTROL PLANE ENABLE"
Reboot
Control Plane settings from dialing *#1575#:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again - I can't promise that performance will improve any if at all by using Control Plane and I do not recommend this for all users. However, it could potentially be useful in locations for which supl.google.com doesn't have accurate or up-to-date info, so still it might be worth trying for some users. But if you're already getting reasonably good GPS performance I recommend it be left alone. And indeed, there might be some good reasons *#1575# has Control Plane disabled by default - it may not even work.
General GPS Tips
General Overview of Unaided/Standalone GPS:
http://gpsd.berlios.de/gps-hacking.html
Pay particular attention to the "Locking and Loading" section as it helps give an idea of what GPS is doing on startup in the various scenarios.
General Overview of GPS in Samsung Galaxy S series phones:
I had been considering writing a discussion of sorts of the general issues involved, but frankly I think this really excellent post would be tough to improve upon:
http://forum.xda-developers.com/showthread.php?t=842694
Be sure to give the author a well-deserved thanks.
General GPS Tips:
In Settings -> Location and Security make sure "Use GPS satellites" (duh) as well as "Use Wireless networks" are enabled. This is especially helpful when getting an initial fix in an area where you haven't used the GPS recently
It's best to leave WiFi on when navigating if possible. Google has mapped the location of wifi networks and can use their location to help figure out where it is even if it's not connected to WiFi
"Use Sensor Aiding" should not be turned on. This was mostly intended for pedestrian use. The sensors really aren't sensitive enough to provide useful info at vehicle speeds, and the use is problematic unless the phone is held at a fixed position relative to the direction of travel
Avoid reorienting the screen if possible when navigating. Using the GPS and Google Navigator actually involves a lot of simultaneous computation between determining the position and downloading and rendering the map data. Reorienting the screen seems to pull too much power and causes the GPS to lose fix and re-acquire a lock.
Plug in the car power adapter if you have one. More than a few people report that this helps substantially, lending more credence to the power starvation theories
Position the unit if possible where it has as much unobstructed view of the sky as possible. There's a reason in-car nav systems are mounted either on the windshield or the dash. If it's sitting on a lap or seat, between the ceiling doors and engine block the ability to get good reception to enough satellites is very limited. Even an expedient mount can make a real difference
You can try cleaning the antenna contacts on the inside of the battery cover with a pencil eraser. Just scrub a little at the white parts; don't remove the white material completely. I *do not* recommend bending up the contact as some suggest as it's extremely fragile and can break.
Acquisition times will be best under a "warm start" i.e. when the GPS already has current almanac (within a week-ish since last extended GPS use) and ephemeris (expires after 4 hours) data downloaded and when its last computed position is fairly close to its current location. In practice this means that initial acquisition times will be best when the GPS has been activated in the last few hours. A weather widget or similar that updates itself by GPS location every 4 hours or so accomplishes this neatly with a fairly small impact on battery life. Fancy Widgets seems to work just great for me.
GPS Troubleshooting Techniques:
Test the complete GPS + AGPS Augmentation:
As best I can determine, LbsTestMode will apply AGPS data if it has already been downloaded, but doesn't ever actually download AGPS supplement on its own no matter what configuration is specified.
To Test the overall functioning of the complete system:
Apply whatever fix or configuration settings to be tested
Use LbsTestMode to delete GPS data
Reboot
Use an app like Google Maps or GPS Status & Test to force download of AGPS data
Once you've followed these steps, LbsTestMode acquisition times will be much faster.
Test the GPS Only:
A great way to test the functionality of the GPS on its own is to turn on airplane mode and the use LBSTestMode or an app like GPS Test to see if you can get a fix.
If you get a fix quickly, this means that a)the GPS itself is capable of functioning, and b)the almanac data is already stored on the phone and is current
If you use LBSTestMode to delete GPS data and then try to get a fix this way, it's normal for it to take several minutes to get an initial fix, and as long as 15 minutes or so before attaining an accurate (<30m) fix. This is because the almanac data is being slowly accumulated over the satellite signal, which takes a long time
There is some indication that doing this once a week or so (almanac data usually expires after 7 days) can be helpful as it forces a complete alamanac reconstruction. It seems likely that Samsung's driver may not be updating the GPS-only almanac properly when using AGPS so doing this will help keep it "fresh."
Some users have reported that using other GPS apps (or even loading the AT&T Navigator app and letting it sit at the disclaimer screen for 15 min) improves GPS performance. This is probably why — it's forcing an almanac update.
subscribed
Let me know if you need help doing the auto configuration of the GPS settings.
It made my GPS worse, but my phone has had a hardware repair and has good GPS (was just curious).
opcow said:
It made my GPS worse, but my phone has had a hardware repair and has good GPS (was just curious).
Click to expand...
Click to collapse
Worse how? Accuracy/tracking/acquisition times?
Sent from my SAMSUNG-SGH-I897 using XDA App
I will install and test in more detail tomorrow on the way to work but based on the indoor test that I ran before and after this "fix", there is no difference.
lock times are diminished but just sitting here, test mode shows signal all over the place and maps has me jumping around erratically.
I am running a 9.1.2 rom kitchen rom. Jl2 modem with todays speed mod kernel. 1007 build captivate.
Maps is good for me. Really good.
I am going to do a my tracks run and well report back in alittle bit.
Edit: not spectacular on the my navigator. Had better.
Sent transparently through the tubes.
I've noticed little improvement (possibly even worse performance) in stationary locks; although I tested only for about 20 minutes.
Serendipity 5.8; GB steam Kernel 12-28
nyydynasty said:
I will install and test in more detail tomorrow on the way to work but based on the indoor test that I ran before and after this "fix", there is no difference.
Click to expand...
Click to collapse
Many of the adjustments I've made relate more to the tracking in motion than stationary fixes. If your configurations before were already allowing for proper AGPS download you might not notice much of a diff. at first.
Rrryan2 said:
Worse how? Accuracy/tracking/acquisition times?
Click to expand...
Click to collapse
I didn't go as far as testing it while driving. It couldn't have been better since my tracking has been virtually perfect since the repair. Acquisition was as fast as far as I could tell, but I got fewer in-views/locks and signals were up and down more. Of course it's possible with several back and forth trials it would even out, but I just played with it a bit and then flashed an undo zip I made and played with it more.
But like I said, my phone has been through Samasung repair and has really good GPS now. I was just curious if I could get better/faster locks indoors or something. If it works for people with bad GPS that's what matters.
This was the first time I've ever been able to drive home without it dropping its tracking. I only had one instance where it went off track, and it readjusted within 5 seconds. Not sure what you did but it seems to make a difference for me! So far...
Sent from my Captivate
xtremekilla09 said:
Let me know if you need help doing the auto configuration of the GPS settings.
Click to expand...
Click to collapse
Thank you, I will! I want to get some more feedback and see if the settings need more tweaking first though.
I've been toying with compiling it all as an .apk too once I'm done. Would at least make things simpler for novices.
Does it matter what ROM you are currently running (ie. 2.1 vs 2.2, etc)?
Sent from my SAMSUNG-SGH-I897 using XDA App
vn1977 said:
Does it matter what ROM you are currently running (ie. 2.1 vs 2.2, etc)?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It shouldn't. Some *modems* do seem to handle GPS better according to some reports, but I'm not altogether convinced that's not because ROM authors have already included their own GPS fixes adn it's being mistakenly attributed to the modem.
Note: installing a new ROM (or re-installing one) may overwrite the settings this fix makes. So if you flash a new ROM and aren't happy with the GPS, just re-flash the GPS fix.
The reason I was asking is that I'm on stock 2.1 (JF6) and was curious if this was made with Froyo in mind. Thanks!
Sent from my SAMSUNG-SGH-I897 using XDA App
Worked pretty well for me. But testing it out once is not a proper experiment. Locked in ~15 seconds and held lock. I was stationary on my balcony.
Rrryan2 said:
It shouldn't. Some *modems* do seem to handle GPS better according to some reports, but I'm not altogether convinced that's not because ROM authors have already included their own GPS fixes adn it's being mistakenly attributed to the modem.
Click to expand...
Click to collapse
The modem can change the GPS performance. I did a lot of modem testing before my phone was repaired. For me jl3 and kp1 were best.
Is there word yet on an official GB update coming, I read some builds like Leaky GB ED12? Anyone put this rom and modem on and seen what the issues were besides no 4G? HIT me up, I work with my epic so can't jump like I used to. Running CC is a big issue for me if I make a move from EC05.
cadams14 said:
Is there word yet on an official GB update coming, I read some builds like Leaky GB ED12? Anyone put this rom and modem on and seen what the issues were besides no 4G? HIT me up, I work with my epic so can't jump like I used to. Running CC is a big issue for me if I make a move from EC05.
Click to expand...
Click to collapse
Known issues with ED12: - 4G non-functional
- GPS non-functional out of the box - WORKAROUND: get GPS Status from the Market; reset AGPS status (works with wireless networks off)
- Wake lag present
- Does not boot when plugged in and powered off, unplug to boot
- Temperature sensor readings are incorrect. You may see interrupted charging due to bad battery temp readings.
- Slide to unlock button sometimes 'sticks'
- Has Carrier IQ
There is a new build.. EE03. But no eta on when gingerbread will be released for our phone. Here is the thread with leaky gingerbread if you want to give it a try: http://forum.xda-developers.com/showthread.php?t=1054050
and if you click on the link in my signature I have made a how to video showing how to do this if you need a visual.
(works with wireless networks off) Don't mean sound or ask stupid questions, but does that mean Wi-Fi on or wireless networks like a wireless router?
cadams14 said:
(works with wireless networks off) Don't mean sound or ask stupid questions, but does that mean Wi-Fi on or wireless networks like a wireless router?
Click to expand...
Click to collapse
It means for gps, if you go to setting>location and security Use wireless networks is unchecked being off. That's what they mean by works with wireless networks off.
Does anyone have a link for EC05 modem download?
cadams14 said:
Does anyone have a link for EC05 modem download?
Click to expand...
Click to collapse
Sure. Right here: http://www.mediafire.com/?u1h35gqewr1y4q7