Hi All,
I've been playing with different roms over the past month or so, I'm currently using joker's CM9 Build. I've noticed that my camera comes up with a black screen on the back camera, the front facing one seems fine. I flashed back to a CM7 rom (Neutrino i think) and same thing. I flashed a new radio last week, the Australian one, to get better battery life, not sure if the camera was working before that or not. Would the radio do anything? I'm going to flash back to a bell radio now, but thought I would pick everyone's brain. I've dropped my phone alot in the last week (had a crazy week at work) and I'm wondering if one of those may have done it.
Any advice would be greatly appreciated
Related
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
Hey guys could anyone help me out, I received a refurbished phone from Verizon 5 days ago and it keeps rebooting. I managed to root my phone using "BAMF GingerREMIX v2.0 Beta #6", Radio: 1.39.00.0430. The most I can use my phone is for about 10 min. unless I leave plugged into a charger. Can anyone help me out???
Are you sure your battery is any good?
Yeah my battery is good, i got a brand new one and its still acting up..
Change the radio to the mr2 radio. Seems the most stable of the gb radios. That might help
Sent from my thunderbolt
This happened to me as well as soon as the screen went off. Rebooted. If I kept playing with it it was fine.
Had to go back to Froyo roms because of it. Happened with MR2 and 2.5 radios.
Sometimes when I mess with the kernel settings a lot this will happen. Try flashing a new kernel or even the same one and see what happens.
Mine has started doing the same thing after receiving refurbished from VZW. My old one never rebooted with same setups. Something quirky going on with it. I can flash back to stock and stops. Its not the rom or kernel i'm using because i have tried all combinations that used to work flawless on old device.
guyz who are using the leak , would they be kind enough to post their experiences about the leak as well as if it solves the missed calls bug that has been plaguing us FSC users ever since FROYO hit.
regards
Since it is a network issue, and the build is older than what we currently have, I doubt it fixes anything. A lot of people think it is a Fascinate issue or a FroYo issue, but it is a VZW issue. Since LTE was flipped on, it has been happening to multiple devices on different OS versions. For example, my wife has a Fascinate still on DL09 and she experiences it. A friend of mine has a DINC and also misses calls
Kevin Gossett said:
Since it is a network issue, and the build is older than what we currently have, I doubt it fixes anything. A lot of people think it is a Fascinate issue or a FroYo issue, but it is a VZW issue. Since LTE was flipped on, it has been happening to multiple devices on different OS versions. For example, my wife has a Fascinate still on DL09 and she experiences it. A friend of mine has a DINC and also misses calls
Click to expand...
Click to collapse
No mate i am 100% sure its fascinate + froyo issue ??
why coz i am using the handset here in India with an Indian CDMA operator and having the same isse , tried calling my phone sitting in front and i could hear the ringig from where i was calling , but the fascinate was sitting idle with no ringing no dispaly and as soon as u unlock the screen it starts ringing.
so believe me its fascinate + froyo and certainly not verizon
I was on both the leak and both versions of Nameless. Ran into several issues on all...
Nameless v4 wiped my sd card. Lost all video playback on Nameless v4.1 Did have Netflix working on the leak but had to side load it. However I found the leak to be very glitchy. I decided to go back to Comm Rom after like 3 days of GB. I'll wait until the glitches are worked out, but really wanna see JT succeed with his CM7 project...
rac1974 said:
I was on both the leak and both versions of Nameless. Ran into several issues on all...
Nameless v4 wiped my sd card. Lost all video playback on Nameless v4.1 Did have Netflix working on the leak but had to side load it. However I found the leak to be very glitchy. I decided to go back to Comm Rom after like 3 days of GB. I'll wait until the glitches are worked out, but really wanna see JT succeed with his CM7 project...
Click to expand...
Click to collapse
well i am keeping my fingers crossed as well
as i am seriously hoping that a proper Stock or properly worked upon leak should get us all rid of the missed call crap.
A little background, I've run Alien 4 for a few months with no issues whatsoever. About three weeks ago, CM7 (the stable atrix build Ba2TF), and shortly after I Flashed Neutrino 2.1GT (1.3), with the patch and assorted addons.
Within the last 1-2 weeks, my internal speaker began going in and out. I flashed 2.2 EE last week, and still had the speaker issues. In that last week, I've also been virtually unable to connect to a PC in any capacity. It's worked at random a couple of times, but that's it.
I reverted back to CM7 attempting to fix the issues, and no luck (this was before the charging issues).
Yesterday, I flashed Faux's Unified CM7 024_r2, thinking maybe it was just wigging out on me. No luck there, so I reverted back to a stable (with the exception of the speaker issue) restore.
Now, my phone will not charge, except when the demon inside it wants too. I've done a factory restore, manually formatted everything but the SD card via CWM, and restored back to the supposed stable CM7 restore. I've tried Neutrino 2.1 & 2.2, CM7, and am currently downloading the MFBSR stock restore.
If it helps, I'm using Rom Racer's current recovery.
Any thoughts here? I'm still pretty new to all this. Could the overclock to 1.3 (Neutrino 2.1GT) have done some damage? My phone was in an otterbox defender. Is there anyway to tell that you guys can think of?
Dumbass me procrastinated on getting my usual Square Trade insurance, and they've now stopped insuring phones past 60 days of purchase. I've had this one since June.
Sorry for the long windedness. If I missed anything, please let me know.
From a powered off state, when I plug the phone in to the PC, it turns on. I'd think this would mean it's seeing something via the data cable, right?
Anyone?
has the gps signal been fixed with the latest ota update?
what is the latest touchwiz on this device?
is it smooth and how is the battery life?
I am on AOKP and get instant and accurate locks instantly indoors or out with or without a good signal.
I know this doesn't answer your question but I haven't had a problem with GPS since froyo.
sent from my ice cream sandwiched Samsung fascinate
shop around... 120 seems steep for a used i500
I just recently picked one up, i was a vibrant user untill work switched over to verizion.... i had just got the darn thing working perfectly too :-(
Mine has no luck with the GPS, it is nearly identical to how my vibrant worked, although the reception is just a little stronger... it is way weaker than a normal phone. It takes nearly 15 min for my phone to get a lock, however once it does, it has the lock... although it does loose quite a few satilights every so often and then grab lock right away again... Seeing how this is exactly how it worked by default on my vibrant, and it didnt get any better till i went to MIUI, who worked out thier own driver which got perfect locks with out dropping the sat lock.
Now for my question....
Im not the account holder on this phone,(its my work phone) and when i had a phone that used a sim card, i had no fear of loosing my regestration info, but im not sure what will happen when i flash this phone to a custom rom. Do you have to reregester it with verizion? or will it just reclaim my number? what kind of issues could i have... i need to make sure i wont have any issues since i dont have the password for activation...
and second, what is the most bug free rom avaliable? I'd like to try out MIUI again or even a stock rom as long as it has better support for GPS.
I've never had to re-activate after flashing anything FWIW. We have MIUI ICS that is quite functional, although I don't believe quite as much works on MIUI compared to the other ICS roms yet. I've had good luck with AOKP, gummy, and THS (rootzwiki) ICS builds. Much better than GB.
For me, the update to Gingerbread (2.3.5) has really improved the GPS performance. It's still not perfect, but it seems to lock up much faster than it used to.