Related
I know there are several apps available for profile switching but I'm looking for some specific functionality.
What I want is an automated profile switch when the mda is on external power.
I think I had a program for this a while ago but due to all the rom upgrades etcetera I seem to have lost it.
Does anybody know which of the known profile apps can do this?
Thanks
haven't come across one that changes the profile based on the charging status however I did have one last year that would react to the GSM cell ID that it was in e.g. if it recogonised the cell at your work it would go into vibrate mode or if it recognised the cell at your home it would switch to quiet or what ever you choose . It was quite neat but I'm damned if I can find it. i'll keep looking.
phoneAlarm will do this
Even Profilws for Windows Mobile does this........ Look at www.winmobileapps.com
Thanks guys, I'll check them out.
Started happening a few weeks ago. Applications that rely on the My Location service within Android fail because Android isn't receiving a location. Examples of this are the Google homepage and the multitudes of weather apps when set to Current Location. I'm inclined to believe it's a tower problem for a few reasons.
1. I have multiple G1's having the same issue while in close proximity to each other even after fresh Factory Resets on all of them AND multiple builds.
2. The problem disappears when switching to 2G (confirmed with a Market app called "Cellfinder"
3. I'll be at random places not associated with home and work and it will work.
4. The DDMS log tool within the Android 1.5 SDK shows that Android is at least trying to get a location lock but failing with various LocationManager errors saying no location was found.
5. The phone's are getting service and with BetterCut & Cellfinder I can see the associated tower's LAC and CID which leads me to believe that the 3G portion of the towers are simply not reporting location back to the phone.
My apologies if this has been posted before. I did a quick search of various child forums and did not see an active topic on the issue. I am hesitant to call TMobile Customer Support on the issue as I don't feel like RMA'ing a perfectly working phone(s). Can any technicians in here confirm or offer any insignt?
I have found out that other members here are having the same issue, such as dwang who led to find Cellfinder and the 2G solution.
I have the same problem. I'm going to try going to an earlier radio, to see if it solves the problem.
enob418 said:
I have the same problem. I'm going to try going to an earlier radio, to see if it solves the problem.
Click to expand...
Click to collapse
Let me know how it goes.
Hi all,
I am trying to find out how widespread the GPS locking problems are with this model. I am talking about non-assisted GPS, which can be tested using the "GPS Test" application on the market.
So, how is the GPS on your phone performing using GPS Test? Please give some detailed information like lock time, number of sattelites, urban/countryside location, and if possible firmware version of your phone.
---
My Spica cannot get a lock at all, will see up to 11 satellites but most of them with signal strength bars at zero. Firmware versions tested (all same result)
1.5 (XEJB2)
2.1 (XXJD1, XXJD4, XXJF2, XXJC3)
Same pb with my wife's spica. Samdroid version with FE7.
Can't lock withour assistance. What a pitty.
Go to your Settings -> Date & Time -> Uncheck Automatic and see if it helps
Or you can try this (need root)
http://forum.samdroid.net/f38/gps-speedup-1262/
http://forum.samdroid.net/f10/fasterfix-1747/ <-- same but easier
i can get a fix under 2 minutes if I stay still...moving, it can take an eternity
AfzalivE said:
i can get a fix under 2 minutes if I stay still...moving, it can take an eternity
Click to expand...
Click to collapse
http://forum.samdroid.net/f38/gps-speedup-1262/ <-- if you're willing to root you can edit it to your location.
i just don't bother with that any more...I might do it again after a month without wiping any data
rooting is like breathing to me ... as it would be to most of the people here
Anyone found a solution yet?
My spica wont connect via gps either. It just keeps blinking and nothing happens...not even after 30min.
I've tried GPStest and it reports that 12 satellites are in view but non in use, and there is no bars everything is at 0...not picking any signal at all :S
I tried my friend's one too and he gets a signal imediatley and a lock after about 10-30seconds.
Any solution to this? Is it a software problem or hardware problem?
Zitko said:
Anyone found a solution yet?
My spica wont connect via gps either. It just keeps blinking and nothing happens...not even after 30min.
I've tried GPStest and it reports that 12 satellites are in view but non in use, and there is no bars everything is at 0...not picking any signal at all :S
I tried my friend's one too and he gets a signal imediatley and a lock after about 10-30seconds.
Any solution to this? Is it a software problem or hardware problem?
Click to expand...
Click to collapse
I installed the alpha CyanogenMod 2.2 and GPS is working like a charm!
Problem was with the wrong libraries being used in many of the custom roms found at SamdroidMod. Devs found out about this issue and fixed it in this 2.2 release.
I'm running original firmwire which i got on the phone. (XXJE4)
I'm not willing to install alpha cyanogen of froyo yet...Is there really no other solution? I've had a chance to compare my spica to another one with original firmwire (JE4 too) ant that other spica worked while my gps had no lock. Also i had the chance to try one with samdroid on and it worked too.
Mine works from time to time. at the moment it works, earlier today it wouldn't get a lock no matter how long i waited.
First thing-delete /data/xtra.bin- this is data for agps which seems to cause gps locking problem. You can do it with RootExplorer/SUFBS or any file manager with root rights. Or use GPS Status and Reset agps data from setting. You can also try to swap libsec-ril.so, JF2 version works best for me. If you want I can provide update packages for libsec-ril.so
i have installed cyanogenmod 7.1 on mine, and can get a lock under 1min30s outside or under 3min in the bus near the window.
I have a rooted spica with android version: 2.2.2, baseband version: i570EXXJC1, kernel version:2.6.29 and Mod version:SamdroidMod-2.2.2-a9.
When I go to google maps app and click set location I always get an error saying: location temporary unavailable ! I checked the option on Settings->Location and security->Use wireless networks and use GPS satellites. And my phone is connected to the internet.
I just bought the phone last week, and its really embarrassing not getting this to work.
schermvlieger said:
I installed the alpha CyanogenMod 2.2 and GPS is working like a charm!
Problem was with the wrong libraries being used in many of the custom roms found at SamdroidMod. Devs found out about this issue and fixed it in this 2.2 release.
Click to expand...
Click to collapse
thanks for the useful info, you saved my life by this post.
i thought my gps is wrong in my spica then it was just a bug in the cooked rom. cyanogen mod is cool and gps is working now perfectly.
thanks again!
With spicagenmod + hp/yonip kernel gps work very well.
This possibly needs to be in the dev section but I will start here.
First off this is not a complaint. What I initially want to do is get an understanding (Technical) of the issues around the PPP dropouts and locks ups.
From where I sit this is the only outstanding issue around the current android builds. Simply the phone rocks on SD card and is ultra stable and fun.
I have noticed various wiki'sstate that internet access is complete however obviously not.
There are a number of issues such as
1: Network dropout. Data connectivity will stop responding. Restart of the radio or mobile data needed
2: Network freeze. Android restart as the radio will not turnoff.
3: console level networking not avail. Eg ping etc simply does not work. DNS does not resolve and ping cannot find a route. Std Android this works fine.
4: Related issues. GPS-A data not downloadable. Only via application layer tool.
Is PPP the default connection type on factory android builds?
What is the difference between the HD2 in dev and a std android with the implementation of the data connection.
How can I help. I have over 20 years in IT and have a thorough understanding of TCP IP layers and routing. I have reasonable understanding of Linux and the kernel IP stack but zero understanding of the android kernel or application layer.
I also have dollars to contribute.
Update:
Currently I am trying all four with isome improvements
1: Updated the Ril WRapper with no luck.
http://forum.xda-developers.com/showthread.php?t=794309
2: Change the phones default connection to GSM PL.
Change the setting found in the menu phone info when you "call" *#*#4636#*#*. There is a option to choose your preferred network. Set to GSM auto (PRL)
3: Update DNS settings.
http://forum.xda-developers.com/showthread.php?t=812930
4: Ensure the correct APN's are being used.
This is no internet versus unstable Internet.
Note. Currently trying all four and things are improving. Had my first dropout after 36 hours versus 2 per day. It happened whilst using the GPS and making a call which always tend to be a stresser anyway. Will try to keep this thread updated.
This thread also has a number of updates http://forum.xda-developers.com/showthread.php?t=813148
I am running a stock WinMo Rom (Latest European release 3.14 I believe). 2.15 radio on a Telstra Network in Australia. My phone is a T8585. Also running [19.10.10]|<<Mdeejay FroYo Sense Series>>|2.25.771.1| cos I like the transparent titlebars
Now I have been running all 4 of the above for around a week now and have to say there is a def improvement. Where it was common to get multiple disconnects per day I have only had 3 in the last week. Mainly when I use the GPS.
I am still searching and have yet to find a 100% fix the stability is now at a point of reasonable reliable. Also noted that the Devs are still hard at work on this.
Update 31-10-2010
A good test is to open google maps while driving. Its about the only time I get a drop out now.
The GPS kicking in always stresses the radio and that combined with the handover of cell sites is a great deal breaker.
This also seems to be consist with my suspicions around the poor handling of corrupt connections.
Eg the system on fresh boot only has a table for handling 50 connections line. This ensures it can handle multiple simultaneous connections as well as background coms.
Now when a connection is damaged or locked normally it should timeout and/or then be deleted from the table. My suspicions is that this is not happening and all the avail connection handling are slowly filling up until there are now free. Frozen this is why it seems to be very unlikely for a freeze to occur straight after a restart but more likely after a day. Also dependent on stress environments. Homes with lots of RF noise, Long way from cell towers, driving, lots of gps use, Wifi cut over.
http://forum.xda-developers.com/showthread.php?t=812930&page=7
http://forum.xda-developers.com/showthread.php?t=794309
Thanks for the response.
I was not looking for work around but more technical information to try and identify where the issue lies. curious to see if ppp is the default and if the ppp implementation should work or is it still a hack/work around.
The steps I have tried are
1: Updated the Ril WRapper with no luck. No improvement
2: Change the phones default connection to GSM PL. No improvement
3: Update DNS settings. Still testing however does not resolve console level network issues and unlikely related to ppp freeze. No logic?
4: Ensure the correct APN's are being used. No improvement
Note. Currently trying all three
This is also separate to a lot of people issues around APN's. From the application layer internet works fine except for the freeze.
I believe rmnet is android's default connection and ppp is winmo's. I think dft reengineered ppp for Android. Remember seeing it some where when ppp first started to appear. Of course this is how I remember it and my life is hectic so it might be the opposite.
Sent from my Mytouch HD2
So I understand that one of the issues with RMNET was dropped packets. Was this due to it not being correctly engineered/implemented or just a nature of the beast?
Also with the issues everyone is having why are we not continuing to investigate RMNET as at least this was initially more stable and more of a native option.
dusty_nz said:
So I understand that one of the issues with RMNET was dropped packets. Was this due to it not being correctly engineered/implemented or just a nature of the beast?
Click to expand...
Click to collapse
That is because it isn't implemented correctly. The radio receiver in our phones was made for PPP, not for RMNET. Latter is standard in native android devices. And there it works very fast and stable. So the devs had to implement PPP in android, which isn't proper working. But they're working on it to improve the stability, I'm pretty sure 'bout that. At least it does work and I had never problems with loosing my connection and bad speeds.
Edit: Those are the known steps to get it at least halfways stable working.
Cheers
Okay.
Did some more playing.
Both RMNET and PPP allow pinging from the console. Just had to enable SU first.
Thanks everyone for your info. Will try my best to be patient.
dusty_nz said:
Okay.
Did some more playing.
Both RMNET and PPP allow pinging from the console. Just had to enable SU first.
Thanks everyone for your info. Will try my best to be patient.
Click to expand...
Click to collapse
But did you also have a delay till it worked? It took me about 20 seconds before any reply came up. And does your ping test work if you try it in the hidden menu when you "call" *#*#4636#*#*?
Aye.
There was a delay and the hidden menu ping does not work either.
Still needs work.
dusty_nz said:
Aye.
There was a delay and the hidden menu ping does not work either.
Still needs work.
Click to expand...
Click to collapse
Right.
Have you seen this thread? It might be a possible solution.
Some people have reported that it works. But I had no time to test it. Had to move servers
That is fix number 3. Update DNS. Testing now. Only been 24 hours however no drops.
Seems strange thou. Hard to imagine it is a DNS issue.
On a side note. Does anyone know what changes to the Rom are needed when installing an RMNET kernel?
Eg If I took the latest MDeejay rom and changed the kernel?
Update
Update on first post.
Def improvements to be found. DNS seems to be the biggest improvement for me but also running all 4 at once.
dusty_nz said:
On a side note. Does anyone know what changes to the Rom are needed when installing an RMNET kernel?
Eg If I took the latest MDeejay rom and changed the kernel?
Click to expand...
Click to collapse
No one who knows cares enough to answer.
As far as I can tell, no 'modern' build uses an rmnet kernel anymore, because apparently the chefs either don't care about data reception, or don't think that there is a problem because they don't leave a build on long enough for it to start developing problems.
enneract said:
No one who knows cares enough to answer.
As far as I can tell, no 'modern' build uses an rmnet kernel anymore, because apparently the chefs either don't care about data reception, or don't think that there is a problem because they don't leave a build on long enough for it to start developing problems.
Click to expand...
Click to collapse
any build that says it uses michyprima r11 is still rmnet based. I don't think the nexus one-based kernels worked with ppp at all.
on another note, I was getting loads of Network Freezes (where flicking airplane mode wouldn't reset the data connection) since last week despite not fundamentally changing anything in my Android setup (see sig). However been doing some research around xda yesterday and may have found something else that's improved my ppp connection stability (so far) and resolved my constant network freeze issue... will update when I've tested this for a few more days.
Some improvment?
APNs are correct, Did the RIL_WRAPPER with no significant improvment. This morning I changed to GSM PRL and noticed an improvment.
Before the GSM PRL, I had many PPP drops, especially when streaming large amounts of data. After the GSM PRL update, I did try streaming youtube, Last.FM, slingpalyer together and NetTest, concurrently, everything is working with no PPP drop.
This is not enough to reach a conclusion, but nevertheless, I never could have done it before
Have a look here.
Stock rom 1.48 WWE, radio 2.15.50 and Froyostone 3.2
Thanks for the support!
BTW: How can I obtain the DNS information for my mobile carrier?
Just report.
I didn't believe change dns will work.
But after I change dns, the data suddenly work ( no need to restart!).
So I think it have something relate to dns.
Same thing. Updating the DNS in the build.pro file seems to have the greatest benefit.
I have a suspicion that the issues are caused with the network driver not flushing dead connections. Eg outgoing requests that to not get a reply. Ideally they should be flushed other wise the connection cache will fill until it can no longer take more connections. Symptom dead/frozen internet
All the symptoms seem to relate to this sort of issue
Things like ppp drop out more likely when on the move (More dropped packets). GPS and wifi but back. etc.
@Dusty_Nz,
Thanks for your help, this is a great thread and its certainly appreciated (the devs are busy enough as it is, xda member contributions are a great help).
As it was asked a few posts up, how do I obtain the DNS settings for my carrier? I am using TMobile US and I'd like to test your observations.
Thanks!
Sent from my HTC HD2 using XDA App
tgtoys said:
@Dusty_Nz,
Thanks for your help, this is a great thread and its certainly appreciated (the devs are busy enough as it is, xda member contributions are a great help).
As it was asked a few posts up, how do I obtain the DNS settings for my carrier? I am using TMobile US and I'd like to test your observations.
Thanks!
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Follow the link on post 3
will then lead you here.
http://www.opengear.com/faq383-Confi...-APNs.html#USA
Hi,
I have searched all GPS related threads on this site and articles elsewhere for this type of bug, but so far no joy.
All previously reported issues are related to positioning and slow satellite acquisition, which are not applicable to my particular case.
The device in question is a SM-N9002 Note 3 Duos, CSC unlocked with SVA-rom ver 9.0 based on Kitkat 4.4.2
Build KOT49H.N9002ZNUFNK1
Bootloader/PDA/Baseband N9002ZNUFNK1,
CSC N9002CHUFNKK
Kernel 3.4.0-3331050 [email protected] #1 32-bit.
I have (re-)rooted it in hopes of facilitating the solution to the problem, which is the fact that the phone's GPS receiver is supplying an incorrect value for GMT (and local) time. The time displayed is 1:16:57 before the correct time.
The error shows up consistently on all GPS apps I have checked and it is the only one I have encountered related to the GPS.
Considering possible causes:
- it might be a hardware defect, whish I consider a bit unlikely;
- ROM CSC versus current location issues; or
- a possible bug in the GPS receiver driver or "radio" as I came to understand.
Even after successfully rooting the phone, I still hesitate to perform more flashing operations, for fear of rendering other functions inactive on the device. I am also a little reluctant to upgrade to a Lollipop based ROM, because I understand that it would require reinstallation of apps and data afterwards and also because of bad experiences with battery performance on my Tab S 8.4, once the same upgrade was pushed onto it
Therefore I am looking primarily for a solution which would involve editing the gps.conf file.
Does anyone know if it is possible to insert a parameter in it, to define a time correction, like e.g. T+77 minutes?
If not, can anyone give info as to where I can find updated radio firmware and whether that can be flashed via Odin without loss of apps and data?
Thanks in advance,
Robert
South Caribbean.
Modems in the modem thread General section .
GPS is kernel .
You can always try editing the gps.conf file .
Pls elaborate...
JJEgan said:
Modems in the modem thread General section .
GPS is kernel .
You can always try editing the gps.conf file .
Click to expand...
Click to collapse
Are you saying that this problem has something to do with the modem?
System time and time zone as retrieved from the 3G network are correct. GPS receiver time is not.
None of my other Samsung devices are affected by this bug.
I'm trying to find out which parameter in the gps.conf file to amend so as to correct for a 76 min time discrepancy.
None of the options in the advanced section of the FasterGPS app seem to be applicable for this.
I'm not sure what the ERR_ESTIMATE parameter does, but I will sure give that a try once I get some infoo on how to edit it.
AirC2007 said:
Are you saying that this problem has something to do with the modem?
System time and time zone as retrieved from the 3G network are correct. GPS receiver time is not.
None of my other Samsung devices are affected by this bug.
I'm trying to find out which parameter in the gps.conf file to amend so as to correct for a 76 min time discrepancy.
None of the options in the advanced section of the FasterGPS app seem to be applicable for this.
I'm not sure what the ERR_ESTIMATE parameter does, but I will sure give that a try once I get some infoo on how to edit it.
Click to expand...
Click to collapse
He jsut said where you could find the modems you were talking about.
He also explained that it has nothing to do with the GPS as thats controlled from the kernel.
And just to be sure, you have set correct timezone and time right? As it might help.
HanZie82 said:
He jsut said where you could find the modems you were talking about.
He also explained that it has nothing to do with the GPS as thats controlled from the kernel.
And just to be sure, you have set correct timezone and time right? As it might help.
Click to expand...
Click to collapse
Thanks HanZie.
Yes, time and timezone are set correctly on the phone. I have done some research on GPS data and learned that each satellite includes a time signal which was set to GMT (UTC) back in 1980. The satellites' GPS time is not continually adjusted for leap seconds and such (to account for irregularities in Earth's rotation and the solar orbit). Therefore it will differ slightly from the atomic clocks. I will try to post a link to the article whereI found that information later on, as I have to return to work right now. At any rate, the time deviation from the satellites will never amount to 77 minutes. By changingyour phone's system time andstarting up and launching the GPS Status you can confirm that the app does not get time info from your service provider's network.