I was getting 15-20 second gps locks when I had radio .40 and DCD 3.2.6, but as soon as I upgraded the radio and DCD then it's taking like over 7-9 minutes to get a lock. Sometimes it won't lock at all anymore unless I do a hard reset on the phone. I'm not sure what happened. Does anybody have any ideas? Look at my signiture below for my current configuration.
What's the best Radio and ROM to use right now with the least amount of problems, etc.? I was looking at the V2.2 heavy and light, but I'm not sure if I really understand much about what they are about or the differences in what I have now. I think my biggest problem is with text messaging. If I do it a lot I have to keep restarting my phone because the memory goes down to zero in no time at all. Infact, I have to keep constantly clearing the memory if I use any programs at all. Thanks for your help and time!
Try either 3.3.4 or 3.2.6. I prefer 3.3.4
after all of my testing i ended up sticking with 3.2.6. did you do the aGPS fix? have you checked the QPST settings since your flash? generally, these settings should stick, but in some cases; such as when you need a new a-key, these settings are lost. my last flash removed all my QPST settings and i couldnt lock until i did the aGPS fix again with the updated IP address and port.
Well, in the past it kept all the information after I did the upgrade, so I just assumed it still did. I didn't need a new A-Key. I guess I'll check the QPST settings and do the aGPS fix again. It's been so long ago since I did all the GPS stuff I can't remember what I did and didn't do. I still do get locks but they take forever now and sometimes I don't get them until I restart the phone.
Why are you sticking with 3.2.6? Why don't you like 4.1.2 or 2.2 heavy or light? I've always had the memory problem where if I use programs it just eats up my memory and I don't get most of it back after exiting the software, and if I use my text messaging then my memory just goes down to zero in no time flat and I can't recover it unless I'm constatly restarting my phone. There must be some kind of fix for this. Please let me know. Thanks.. Steve
kflipproductions said:
after all of my testing i ended up sticking with 3.2.6. did you do the aGPS fix? have you checked the QPST settings since your flash? generally, these settings should stick, but in some cases; such as when you need a new a-key, these settings are lost. my last flash removed all my QPST settings and i couldnt lock until i did the aGPS fix again with the updated IP address and port.
Click to expand...
Click to collapse
the QPST settings have changed, so if you did it a while ago you probably just need to update it. youll be locking again after that. ive tested all of dcds roms quite a bit, and always ended up back at 3.2.6 or 3.2.5. im really happy with the speed and everything works exactly as it should. i have a pretty heavy today screen load as well as running several apps at the same time. i didnt like the 4.x.x roms for a couple of reasons. the unread text message thing bugged me alot. i also had a problem with random hard resets, which i was not a fan of.
kflipproductions said:
the QPST settings have changed, so if you did it a while ago you probably just need to update it.
Click to expand...
Click to collapse
Are the changes in the AGPS thread?
yes they are
Oh, really? Then that's probably part of the problem. I changed them maybe a year ago or longer. I tried running QPST to check and it's giving me an error message when I start it, so I'm going to have to try to reinstall it and see if that fixes it. Also, the links for the pictures are dead and they aren't coming up anymore, it makes it harder to figure it out.
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
I ran the Serf Telus aGPS Provisioning CAB file and that seemed to help. I sometimes get locks under 1 minute now, but sometimes it won't lock at all and I have to keep soft booting the phone to get it working.
Oh, so that's why my phone keeps resetting? It's not hard resetting I think it's just soft resetting. At first I didn't like the unread text message thing, but now I do because I get a lot of text messages and when I go to read them it doesn't mark them all as read in the group and I can read them when I get a chance.
I still had the memory issues with the 3.2.6 ROM with my memory going down to nothing, especually when I did text messages, I had to keep restarting my phone. That's been a problem I had with all my ROMs. I wonder why that is? Could it be the version of the MMS software I'm using? Is it the latest version?
Maybe I should go to the MR1 ROM? I still will be able to use the GPS and the WiFiRouter software with it right? Maybe that will solve all my problems? What about the 2.2 light and heavy ROMs? Does anybody know anything about those? Thanks for your help and time...
kflipproductions said:
the QPST settings have changed, so if you did it a while ago you probably just need to update it. youll be locking again after that. ive tested all of dcds roms quite a bit, and always ended up back at 3.2.6 or 3.2.5. im really happy with the speed and everything works exactly as it should. i have a pretty heavy today screen load as well as running several apps at the same time. i didnt like the 4.x.x roms for a couple of reasons. the unread text message thing bugged me alot. i also had a problem with random hard resets, which i was not a fan of.
Click to expand...
Click to collapse
Well, I uninstalled QPST and reinstalled it and it worked this time without any error messages. It seems if I don't use it for a while it gives me a error message if I try to use it again and I have to uninstall it and reinstall it and then it works OK. I don't remember the error message, but I think it's something about can't find a server or something.
Anyways, you were right about the information I had being old and not correct. I had 66.174.95.132 and 8888 instead of PDE IP Address: 216.198.139.92 and PDE Port Number: 8889. I corrected it and it still seems to take about 56 seconds to get a lock, but hopefully now it will be more reliable in getting the locks. I seem to remember in the past getting locks in less then 10-15 seconds, and I wonder why I can't get locks like that anymore.
Thanks for the help!
Well, I was wrong, I'm getting 15-20 second locks now and I'm getting twice the satalites, up too like 9 satelites and I was getting 1/2 that before and it's a lot more accurate now. Before when I was using Google Maps, I could see it was off like about 50-75ft, but now it's spot on, on my location. Hopefully someone knows the answers to some of my previous questions and can get back to me. Thanks..
I too was having this same exact problem and I had to update the QPST IP address and port again. Mine had reverted to the same thing that Apota's had, with the exception of my default port being 8888. All is working well now that I reset the QPST IP address. I get 6-8 sats and locks in about 10 seconds.
I had been experimenting with some of the RyanMogul's new ROMs when this broke for me. I tried 2.1 light and it stopped working. I'm currently running 1.1 light with it functioning after reusing QPST.
DustinEarnhardt said:
I too was having this same exact problem and I had to update the QPST IP address and port again. Mine had reverted to the same thing that Apota's had, with the exception of my default port being 8888. All is working well now that I reset the QPST IP address. I get 6-8 sats and locks in about 10 seconds.
I had been experimenting with some of the RyanMogul's new ROMs when this broke for me. I tried 2.1 light and it stopped working. I'm currently running 1.1 light with it functioning after reusing QPST.
Click to expand...
Click to collapse
I just upgraded to the v2.2 light. I think I'm going to have to get use to it because the interface is so different, but I got a GPS lock with my TomTom GPS software in about 4 seconds. I couldn't believe it. I haven't seen a lock that fast before. It's really awesome! LOL
Related
I know this is not supposed to be able to happen, but on two occasions today and since upgrading to new radio and DCD 3.0 my wifi has turned on and detected networks with the wifi switch set to off, not sure why this is happening and I can not duplicate it on demand, trying to turn on wifi with the switch of via comm manager still does not work. Trying to find some kind of pattern but it has only happened twice.
Perhaps with the new radio there is a way to turn it on and off via software, or perhaps my switch is malfuntioning.
I had a similar experience as well.
I noticed it when I soft reset (not all the time, but 1/10 maybe?) and when trying to activesync, it would sometimes turn on.
I wish there was a way to figure it out, this means that it should be possible turn on wifi via software doesn't it?
Now that you mention it one of the times it came on was right after a soft reset.
Yep, this is becoming a well known problem.....well, for me not a big problem, just a slight annoyance....in the new ROM/Radio. It must have something to do with the radio, because I never experienced this in any other ROM. I'm wondering if WLAN may be turning on when there are short lapses in carrier coverage, and when an app (like activesync....I sync my e-mail using outlook)is trying to be connected to data (the internet). I just turn it back off when it turns on by itself. It doesn't ever seem to turn OFF by itself when I'm actually using WLAN.
EDIT:
one thing that may support my theory is that when you do a soft reset, it takes a bit to connect to the carrier network, and this just happens to be one of the times that WLAN turns itself back on..
And yeah, the battery usage definately sucks....plus when WLAN is turned on, and you're not connected to an access point, you could have data throughput issues as it keeps trying to see if it can connect through WLAN and/or radio......
I need it fixed , I didn't catch it earlier and my battery lost 85% today wihtout me even using my phone. Normally I get 2 full days I haven't really used my phone today and was fully charged this morning now I am at 15%, very poor performance for my typical use.
I am running dcd's 3.0.1 on my XV6800 and noticed that the wifi will turn on with the switch in the off position. It has happened to me a half dozen times or so. It only does it while I am on a call. Any suggestions? Has a solution been found yet? Any help is appreciated!
Same here, but has only happened a of of times.
louderjw said:
I am running dcd's 3.0.1 on my XV6800 and noticed that the wifi will turn on with the switch in the off position. It has happened to me a half dozen times or so. It only does it while I am on a call. Any suggestions? Has a solution been found yet? Any help is appreciated!
Click to expand...
Click to collapse
It only appears to happen while in a call for me as well...it happened with no additional software installed at that point so I'm certain it has something to do with the rom itself...I'm guessing the new radio but who knows for sure...
shame here
i know what it is guy its wifirouter setting changes it makes all phones with this app will have the same deal!
llmo128 said:
i know what it is guy its wifirouter setting changes it makes all phones with this app will have the same deal!
Click to expand...
Click to collapse
Except that I've never installed WiFiRouter...
I don't have WifiRouter either.
cdoggwsu said:
Except that I've never installed WiFiRouter...
Click to expand...
Click to collapse
And I hvae never had the problem. (and I do run wmwifirouter)
i saw this when the kitchen first came out as well. i also saw that it wanted to connect to a roaming alot more than it should as well.
sprint will tell you to set you phone roaming settings to "sprint only" the phones and ROMs come with "automatic" enabled.
my sprint buddy told me long ago to change this from auto to sprint only. soft reset. let it conect to a good sprint connection. then switch back to "auto" and soft reset.
i haven't did this for a year or so, but when i started seeing the roaming icon after many of the soft resets i thought about it. since i did this i haven't seen the roaming nor the wifi bug.
i think it is the theory that when you softreset the phone set on auto looks for the first tower, which could be a roaming tower. this takes a little too long to conect. in this longer than normal connection time when something like activesync wants to connect and has no internet connection it will enable wifi to connect if it has to.
i have noticed in the past with other ROM's as well that if your phone is in flight mode and you soft reset. as soon as activesync tries to connect and cant it will turn on wifi.
try this. turn on flight mode. soft reset. open active sync and hit sync. you'll see.
so for the record... this is not a dcd bug, but rather a windows mobile bug. wm 5 and 6. the best fix is to set it to sprint only or do the trick i stated above.
Are any of you running the HTC Home Plugin with the weather patch?
Because I installed it on my XV6800 and on a soft reset the WiFi was acting wacky. As if it was looking for a signal.
All I did to correct this issue was to disable automatic roam / download of the weather.
Well what I noticed so far is this, mostly happens after a soft reset, but sometimes it does it at random. Only happens when I have DCD 3.0.1, I am not seeing it with any other custom rom and I think I have tried them all. I have not had any roaming icons or the like and with telus customizations on you have two options for network, there is standard and automatic.
The only reason I hold on to it being dcd 3.0.1 is that no other version 3.35rom I've installed has done it, the ones I have installed off the top of my head are the stock sprint rom, DCD 3.0, 3.0.1, no2chem 5053, and two others that I can't remember as well as my own stripped down version of the stock sprint rom.
jjlwork said:
Well what I noticed so far is this, mostly happens after a soft reset, but sometimes it does it at random. Only happens when I have DCD 3.0.1, I am not seeing it with any other custom rom and I think I have tried them all. I have not had any roaming icons or the like and with telus customizations on you have two options for network, there is standard and automatic.
The only reason I hold on to it being dcd 3.0.1 is that no other version 3.35rom I've installed has done it, the ones I have installed off the top of my head are the stock sprint rom, DCD 3.0, 3.0.1, no2chem 5053, and two others that I can't remember as well as my own stripped down version of the stock sprint rom.
Click to expand...
Click to collapse
Did you have this issue with your Stock ROM?
I only ran the stock 3.35 rom for about a day but I seem to recall it happened then as well. I didn't think it was necessarily DCD's rom but was an issue with the new radio. I'll try the steps cody recommended and see if that does the trick.
llmo128 said:
i know what it is guy its wifirouter setting changes it makes all phones with this app will have the same deal!
Click to expand...
Click to collapse
Nor have I.
I just switched to sprint only, and after a soft reset, the wifi did not turn on as usual.
[email protected]$ said:
Did you have this issue with your Stock ROM?
Click to expand...
Click to collapse
No I did not, however I also did not have it on there very long. I flash often, and I am constantly tweaking, "My name is jjlwork have a flashing problem" lo
Interestingly enough I am able to reproduce by following cody's instructions with the flight mode -> soft reset -> activesync
Hey guys,
I recently upgraded my phone ( http://forum.xda-developers.com/showthread.php?t=402027 ) and it seems to have killed my gps. i have just loaded up 3.39 and dcd 3.1.6. I ran all the cabs like i was told and then installed all my programs, including gps gate, the htc gps tool, quick gps, and iguidance.
Before when i had the 3.35 i would get a lock in my house within 3-6 minutes. but since the upgrade i have been unable to get a lock. GPS gate always stays in yellow (running ok but not getting positional data) and if not, it is red with the message invalid data coming from the serial port. Iguidance constantly sees satellites but is unable to get a lock sometimes seeing as many as 8-9 satellites but simply unable to get a lock. same goes for the htc gps tool.
Frustrated by this, i read about the Titan gps fix, that required going through qpst programing , and read that many Verizon users have had success simply using this fix. After trying this fix, my situation has not changed and i am still unable to get a lock. I figure i might go and try driving around with this phone tomorrow seeing if i am able to get a lock outside my home.
If you guys have seen anything like this and have a word of wisdom i would love to hear about it.
Have you tried a hard reset? If that fails, re-flash the phone. 3.39 should not have killed your GPS, but it's possible that the GPSone chipset simply failed on its own. I personally had this happen to my XV6800.....
I have done a hard reset and re-installed all my apps, Iam still unable to get a proper lock on my phone as of right now using google maps or gpsgate. I am going to reflash 3.39 along with the dcd again tommorow to see if that will fix; before i do that i am going to make sure that the hard reset did or did not fix it by driving around and seeing if i get a lock then.
You shouldn't need to drive around. In my experience, locks tend to be quicker when you are standing still. I've never tested it, but it at least seems that way. So just stay in the same place (and save gas $$$). To simply reinstalling all your apps, use user configuration or Sashimi (my preference)
Heh, Looks like i spoke to soon, I went it seems that my google maps just got a lock so i assume everything is working as it should now.
I really appreciate all the support guys.
Sweet, let us know if you have anymore issues. Also, a commonly overlooked step is to enable the Location ON setting instead of 911 only.
R 3.42.50
D 3.3.4
Verizon Service
I've been running on this awhile. A few weeks ago, I noticed that my GPS just stopped working. Ie meaning that it was working before, and I made zero changes and now none of the GPS applications can detect that there is a GPS.
I'm looking for the most painless recommendation that I can do to get it working.
A. Do I need to flash a new radio rom and then do another set of the GPSFix using the windows tools again?
B. Do I need to upgrade both the rom and radio at the same time (ugh ...)
C. Is there another reason for the fact it no longer works, such as the IP address changed for assisted GPS or anything and I could just change it?
Anything you can offer would help. I went through a few pages of the 70+ page posts here on these subjects but couldnt find anything relating to prior working phones randomly stop working.
I will say that my friend is also on Verizon, has a mogul, I think he has a similiar radio and firmware and his has stopped working as well, so my guess is something has change carrier side and we're just not in the know =)
Thanks in advance for any points, and no flames for not being magical and finding the right post with the answer already in it ..
I just went through the latest updates to the AGPS article at:
http://wiki.xda-developers.com/index.php?pagename=VerizonAGPSFix
I have updated the IP address to the one listed there (mine was different), and still no luck.
Working now. Had to restart it twice, turn location on and off and on again, and then let it sit for awhile. I just didnt have the patience.
Are there any ROMS out there that have working MMS ? I have tried a number of them and no luck. I know these are labors of love but it's such a vital part of the phone itself to be left on the back burner. The only ones it works for me are 2.1 v's 1,2 & 3 every other ROM i tried it's always the same thing, no soft button lights, no trackball lights, no MMS. I've tried every fix offered under the sun & it just doesn't work, OR it might work, 18 hours later.
From what i have read it looks like half the people have no problems & have are in the same boat as me.
any suggestions?
thanks
I use sense-able and have no issues sending or recieving mms msgs
the MMS fix is quite simple. What ROM are you using? I know that in the EE thread there is a link to ivans-apns and instructions on removing your current APNs and installing the APNs from ivans rom.
I have working MMS on every rom I have tried except for one .....
Thanks for the 411 and I must say that name gave me the first laugh for the day "Cornbreadfarts"
Fn Funny dude.
well last night i loaded ZenEXP-Eris_Rev6-fixed_mak, i hadn't seen that one before and it looked very stylish. The overclocking isn't so important but i like the apps2sd. Followed all the instructions including flashing the mms fix also cited in the thread. I should have tried it our right away but i began to get comfy with the rom then when i remembered, bingo, same thing. Attaching even a very small photo gets a generic network error, it'll try 4 times to send it then stop. With other roms, sometimes 18 hours later it'll suddenly go through.
before this I'd tried evil eris, lightning, Dvanilla2fast, vanilladroidv1, fresh 2.1 & aloysius, all with the same result.
every rom has their own little quirks, evileris would seem to stall for a while then suddenly go through all the motions of your frantic thumb presses while u thought there was something wrong. I tried all the solutions offered also with the apn's in the evileris thread but still the same thing
the zenexp seems to restart itself at random times and does not come out of landscape mode after taking a pic. I have to press settings, then back & it resets itself
I like the variety in the various roms and the little extra bells & whistles that the developers add it's just this 1 issue really for me. I don't make a lot of calls and i mostly text back & forth to my daughter in NYC. Recently a loved pet of 13years died but beforehand i couldn't send her any pics of the cat in the days previous.
I guess i'll look for this sense-able and try that. I just don't get it though, we are all using an eris, it should either work or be broken for everyone right ?
heywoood said:
well last night i loaded ZenEXP-Eris_Rev6-fixed_mak, i hadn't seen that one before and it looked very stylish. The overclocking isn't so important but i like the apps2sd. Followed all the instructions including flashing the mms fix also cited in the thread. I should have tried it our right away but i began to get comfy with the rom then when i remembered, bingo, same thing. Attaching even a very small photo gets a generic network error, it'll try 4 times to send it then stop. With other roms, sometimes 18 hours later it'll suddenly go through.
before this I'd tried evil eris, lightning, Dvanilla2fast, vanilladroidv1, fresh 2.1 & aloysius, all with the same result.
every rom has their own little quirks, evileris would seem to stall for a while then suddenly go through all the motions of your frantic thumb presses while u thought there was something wrong. I tried all the solutions offered also with the apn's in the evileris thread but still the same thing
the zenexp seems to restart itself at random times and does not come out of landscape mode after taking a pic. I have to press settings, then back & it resets itself
I like the variety in the various roms and the little extra bells & whistles that the developers add it's just this 1 issue really for me. I don't make a lot of calls and i mostly text back & forth to my daughter in NYC. Recently a loved pet of 13years died but beforehand i couldn't send her any pics of the cat in the days previous.
I guess i'll look for this sense-able and try that. I just don't get it though, we are all using an eris, it should either work or be broken for everyone right ?
Click to expand...
Click to collapse
ZenEXP-Eris doesn't restart itself at random times out-of-the-box, you must have installed or modified something that's causing that error. My releases go through a somewhat rigorous beta testing before they see the light of day - at least since Rev5 - and we've only seen minor issues upon release of them.
As for the accelerometer (the "not coming out of landscape" issue you refer to), that's a known bug in Rev6 that was found after releasing it. It is fixed in Rev7.
At the begining of my ZenEXP-Eris thread, I state that you should read the entire thread twice before flashing. This is so you know what you're doing, what to expect, how to make things work properly and what bugs are present in the ROM. Obviously you didn't read my entire thread, or you would have found the MMS-Fix, which is located about 6 lines below the ROM download
On a side note, Rev7 includes the MMS Fix built right into the ROM, no need to flash the MMS-Fix through Recovery like you do now for Rev5 and Rev6. You'll be able to enjoy Rev7 (hopefully) tomorrow (if not the next day).
-mak
Sorry, I thought I had been clear, I did read the whole thread and did dl & flash the mms fix zip u attached. I'm only reporting on the problems I'm having. This isn't a personal attack on you.
As I said, I understand these are labors of love and I wouldn't report something if it didn't happen. I have had 3 occasions where it restarted itself and all 3 times all I had installed was vignette, meebo, Google translate, shopper & barcode scanner.
Thank you for your reply
-------------------------------------
Sent via the XDA Tapatalk App
heywoood said:
Sorry, I thought I had been clear, I did read the whole thread and did dl & flash the mms fix zip u attached. I'm only reporting on the problems I'm having. This isn't a personal attack on you.
As I said, I understand these are labors of love and I wouldn't report something if it didn't happen. I have had 3 occasions where it restarted itself and all 3 times all I had installed was vignette, meebo, Google translate, shopper & barcode scanner.
Thank you for your reply
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I'm sure it wasn't a personal attack, but I'm not sure why you're telling me that?
Anyway, if you installed the MMS fix, you should have working MMS. The MMS fix hasn't failed anyone that I know of and I used it myself on Rev5 and Rev6. Did you boot into the phone and set it up after flashing the ROM, but before install the MMS fix? The file the MMS fix installs gets overwritten during the first boot, which is why you need to reboot before installing it.
I don't use any of the apps you've installed, so I can't attest to their compatibility with ZenEXP-Eris. What I recommend you do is backup your data, go into Recovery and wipe data/cache/dalvik/ext, then re-install the latest release of Rev6, boot into ZenEXP-Eris and set your phone up, reboot into Recovery and install the MMS fix. Before installing any applications test it all out for a few hours, the proceed to install them one-by-one, leaving an hour or so in between installs until you (possibly) find what is causing the issue.
I'm really sorry to hear this issue persists for you but, as I mentioned earlier, you're the first to report such issues, thus the reason I suspect something else as the culprit
Feel free to PM me for one on one support if you need it.
-mak
edit: Also, regarding your softkey lights, they only turn on in dark areas. Hold your finger over the light sensor to the left of the earpiece speaker to see them light up. In ZenEXP-Eris the jogball LED doesn't function, but I have mapped notifications to the charging/power LED in the upper-right-hand corner of the Eris as an alternative, for now.
heywoood said:
Are there any ROMS out there that have working MMS ? I have tried a number of them and no luck. I know these are labors of love but it's such a vital part of the phone itself to be left on the back burner. The only ones it works for me are 2.1 v's 1,2 & 3 every other ROM i tried it's always the same thing, no soft button lights, no trackball lights, no MMS. I've tried every fix offered under the sun & it just doesn't work, OR it might work, 18 hours later.
From what i have read it looks like half the people have no problems & have are in the same boat as me.
any suggestions?
thanks
Click to expand...
Click to collapse
Hey,
There are several out there that work. Ivans are typically good to go out of the box and most if not all the Sprint based roms will be good to go by using the apn fix. Its a trial and error thing just find a rom that you like and give the thread a good read.
Most all the posted roms now have an mms "fix" or are good out of the box. I know it gets a bit disheartening flashing, setting up, wiping, flashing etc...lol...but thats the joy of a rooted handset...trial and error till you find a rom and dev you like well enough to stick with.
.mak said:
I'm sure it wasn't a personal attack, but I'm not sure why you're telling me that?
Anyway, if you installed the MMS fix, you should have working MMS. The MMS fix hasn't failed anyone that I know of and I used it myself on Rev5 and Rev6. Did you boot into the phone and set it up after flashing the ROM, but before install the MMS fix? The file the MMS fix installs gets overwritten during the first boot, which is why you need to reboot before installing it.
edit: Also, regarding your softkey lights, they only turn on in dark areas. Hold your finger over the light sensor to the left of the earpiece speaker to see them light up. In ZenEXP-Eris the jogball LED doesn't function, but I have mapped notifications to the charging/power LED in the upper-right-hand corner of the Eris as an alternative, for now.
Click to expand...
Click to collapse
I actually did exactly what you said. I downloaded all the files first then i formatted the sd card, toggled, loaded the rom & the mms fix, wiped the handset (reset & dalvik), flashed the rom. When it loaded I set up the phone, power cycled & booted to recovery, flashed the mms fix and restarted the phone.
I wanted to make sure that apps2sd was working to i went to the market & installed vignette (excellent photo app) and the usual google made apps like translate, shopper etc
it was after all this I remembered the mms, so i tried it & nada.
I'm about to reformat & wipe now so i'll see what happens
My installation has been working fine and I even managed to increase battery life by installing "Juice".
Suddenly, about 3 days ago I noticed the phone was saying no signal. I was clearly getting data, as my apps worked and I was getting eMail alerts and downloads, but no calls.
I tried restarts, but to no avail. I am using Rod_100 UK as I am on Vodafone UK... I assume it is correct, certainly worked for the past month.
I have had to revert back to Windows Mobile.
My immediate thoughts are it is Juice that is causing it. I have just logged back in to my XDAndroid to write this and Juice did not load, and guess what, the signal has come back.......
Just in case is there anything else to look for?
Never heard of "Juice". I have heard of JuiceDefender however...
If you don't have the issue on a clean install, I'd say that app (or one of many I'm assuming you have installed) is the culprit. Rename your data.img and boot, see what happens.
Yes, it is JuiceDefender, apologies for the abbreviation.
I un-installed it and I have network again, but I guess I will loose battery longevity again, not that it made a huge difference.
I'll keep my eye on it....
Still no improvement
No, still not working. I get no signal, when I am in eye shot of a mast and on WM I get a full signal. I am booting in to WM to a deluge of SMS messages that I had not received, mostly vMail notifications, to which the messages are from calls that I did not receive.
The radio is not as strong and keeps dying on me requiring a reboot
I dont know what exactly but some program is giving android problems
jonners59 said:
No, still not working. I get no signal, when I am in eye shot of a mast and on WM I get a full signal. I am booting in to WM to a deluge of SMS messages that I had not received, mostly vMail notifications, to which the messages are from calls that I did not receive.
The radio is not as strong and keeps dying on me requiring a reboot
Click to expand...
Click to collapse
All I can say is do the standard mess.
Make sure you're up to date.*
Delete (move, rename) data.img.
Format SD. Full format. HP tool.
*There's a lot of testing stuff flying around right now too, making that difficult admittedly. Hopefully the auto-build service will return soon, and all the madness will get committed soon!
Check in your startup file forcecdma=0. I had that problem too.
wormy315 said:
Check in your startup file forcecdma=0. I had that problem too.
Click to expand...
Click to collapse
The command is force_cdma=X....
arrrghhh said:
The command is force_cdma=X....
Click to expand...
Click to collapse
OK, I have tried deleting the data.mag
Didn't work
Have just changed "force_cdma=0" to "force_cdma=X" Will see if this works and feed back
My gut feeling is it is something to do with "JuiceDefender".
jonners59 said:
OK, I have tried deleting the data.mag
Didn't work
Have just changed "force_cdma=0" to "force_cdma=X" Will see if this works and feed back
My gut feeling is it is something to do with "JuiceDefender".
Click to expand...
Click to collapse
Uhm, you replace X with a value. 0 if you're GSM, 1 if you're CDMA....
arrrghhh said:
Uhm, you replace X with a value. 0 if you're GSM, 1 if you're CDMA....
Click to expand...
Click to collapse
Well I took it literally, as I have no idea, sorry. I'll put it back... Anyway, I have another problem now anyway. Having made the change it will not boot. I checked the permissions and it is not "Executable" any more. I have tried changing it but it will not let me. How do I fix this - I am accessing via my laptop which is Ubuntu (Linux).
Can you help, please?
jonners59 said:
Well I took it literally, as I have no idea, sorry. I'll put it back... Anyway, I have another problem now anyway. Having made the change it will not boot. I checked the permissions and it is not "Executable" any more. I have tried changing it but it will not let me. How do I fix this - I am accessing via my laptop which is Ubuntu (Linux).
Can you help, please?
Click to expand...
Click to collapse
What is not "Executable" any more... haret.exe?
The startup file
Sorry, ignore me.
After the change, I double clicked the Android shortcut to launch Android, but it would not start, so I assumed the file had to be executable (as it was the only item I had changed)... I had forgotten to disconnect my TP2 from my laptop!
I've done so now and it has launched. A stupid user errorhttp://media.xda-developers.com/images/smilies/biggrin.gif
I'll keep you posted on any changes.
Ha, fair enough. Enjoy.
Solved. Keep loosing Radio
OK. I tried all the above. Delete data.img, and check the startup script/cmd.... none worked. At some point I would loose the network connection.
As it started within days of loading JuiceDefender and its components and from the description of how it works - controls the running apps including radio and data transfer, I always suspected it to be the root cause. After the other checks failed I tried removing all Juice Defender apps and since then c30hrs I have not experienced any loss of communication.
Thanks everyone for your help, and I hope this will be of use to anyone else suffering from loosing radio/ signal.
jonners59 said:
OK. I tried all the above. Delete data.img, and check the startup script/cmd.... none worked. At some point I would loose the network connection.
As it started within days of loading JuiceDefender and its components and from the description of how it works - controls the running apps including radio and data transfer, I always suspected it to be the root cause. After the other checks failed I tried removing all Juice Defender apps and since then c30hrs I have not experienced any loss of communication.
Thanks everyone for your help, and I hope this will be of use to anyone else suffering from loosing radio/ signal.
Click to expand...
Click to collapse
It has been a number of days now and I have not experienced the same issue, so my conclusion is that it is the JuiceDefender that caused the problem.
The down side now is that I get 7am to 4pm battery life as opposed to 7am to 7pm.... But atleast I can receive and make calls!
A note: The signal strength on the project image is not as strong as the WM6.5, but I am sure that is a known issue.
jonners59 said:
It has been a number of days now and I have not experienced the same issue, so my conclusion is that it is the JuiceDefender that caused the problem.
The down side now is that I get 7am to 4pm battery life as opposed to 7am to 7pm.... But atleast I can receive and make calls!
A note: The signal strength on the project image is not as strong as the WM6.5, but I am sure that is a known issue.
Click to expand...
Click to collapse
Hrm, didn't realize that app would help out that much. But, it makes sense if it's turning off all your radios lol.
Anyhoo, have you seen the kernel I posted from WisTilt2? It has full panel collapse, and battery life is astounding with it.
Code has yet to be committed, as he still has some work to do for the AUO panels (select RHOD100's basically) - so unless you have one of those you can reap the benefits of his new code .
(bzo got nearly 65 hrs with the radio on, sync off - 100% sleep.)
Looks interesting, but where do I download the latest version... I don't plan reading all the threads! And IF I installed would I loose all my settings and apps?
Update
It has been a while since I did all this tinkering, during which time there has been an update.
What I find I get is sometimes (c every couple of days) the meter says I have signal but nothing connects with a message "no network". Also, but far more frequent, as with today where it has occurred 3 times, I dial a number and nothing happens. It says ringing but there is no ring tone and it never seems to connect. I then shut the call down either by using the hang up button or the soft hang up key. The screen then changes to "Hanging Up" but again sits there indefinitely. The only solution id to do a restart.....
Any ideas?
PS: any news on when the bluetooth and camera will be working...?
I have found that any app that acts as a task killer of any sort (juice defender must in someway stop apps to save battery) can also kill your connection. I found this out while using xdandroid and it became immiediately clear when I stopped using the task killer my bars and data proved to be more consistant! Hope that helps.
-------------------------------------
Sent via the XDA Tapatalk App