Hey guys, bit of a weekend brain teaser for you guys...
My rotation function just stopped working completely a day or two ago. I dont know if its worth mentioning but I actually never use auto-rotation (I just personally dont like/need it much). However, certain programs; Youtube, games, have usually served their proper rotation function when in use.
I've been running SC 2.9.2 with jt's ec10 kernel for quite some time now without any flaws. No changes were made to the phone before the issue.
Kinda sucks not being able to watch Youtube in full screen...
Any ideas?
Interesting. Mine stopped working a couple of days ago as well, also using SC 2.9.2. I'm using jt's 4/7 kernel. I've tried reinstalling both the rom and kernel with no success. In addition to the rotation my compass also does not work, so both the accelerometer and magnetometer have failed. It happened while using Google Nav in walking mode, where the phone froze and became unresponsive. After about 10 minutes of no response I pulled the battery and afterward noticed the problem. I'm planning to revert to stock to see if it helps tonight.
whereas im relieved to know that someone else is on the same boat, i really hope that it doesnt come.down to doing a full back to stock wipe :/
it would be nice to know what caused the malfunction...
Sent from my SCH-I500 using XDA App
Mine's working again after going back to EB01 briefly before going to EC01. I was planning to try out EC01 anyway and the brief revert to EB01 is part of the procedure.
Related
Sorry all if this has been touched on but I'm at work right now and the search on the app isn't the same as the full sites. Anyway, I first ran into this issue on listybs nomsensikal 4.6 and now I'm kaosfroyo v32 and when I open gps and type on the address, it begins to load but freezes on the screen where it loads the route but isn't actually navigating..It just keeps searching for gps...after about thirty minutes if finally starts telling me how to get where I am going...i think my issue may stem from TransparentKaos as I used this on both roms and hadn't had issues before flashing it, if anyone has got two cents to throw my way it would be appreciated.
edit- it's definitely not transkaos, which is a relief cause i love the theme but i'm still not sure why this is happening to me, i've done a full wipe and reinstalled the rom but still not picking up the gps signal consistently, randomly it will work right away but mostly waiting for at least 20 minutes before it finds it...not sure whats up
Sent from an Eris running in beast mode aka KaosFroYo v32 using the XDA App
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.
I have two Samsung Fascinates. Both were wiped clean and Odin flashed with DJ01. I followed all the steps to install SC 2.92 Voodoo. One of the phones works fine. The other phone occasionally stops responding in the middle of the screen.
I went ahead and flashed it back to stock and it doesn't seem to have this problem. I have gone from SC to Stock 2-3 times now, and after a few minutes of use it keeps doing this. Is anyone else experiencing anything similar?
Which odin package did you use to return to stock?
There are a few of us on here who have screen response issues. It's even worse when the phone is charging. No known solution. I think it's a problem that carried over from the i9000 which our current kernel is from. I was going to pull the thread for you but the search function is down.
Some work arounds:
Reboot. It will work for awhile repeat as needed
Don't root...
Try my guide, if it doesn't work still.
http://forum.xda-developers.com/showthread.php?t=1001064
Let me know by posting in guide.
Your guide is what I did twice. It appears that this is a known issue with only certain phones. I also noticed that the display is brighter on the fully functional super clean fascinate.
I went ahead and flashed it to stock took it to the Verizon store showed the person that it wasn't as bright at max settings, they said it looks like a manufacturer defect they will send me another phone and just to mail back the one I have.
I also have 2 FC n other one had that so b4 flashin di01 I flashed eb01 stock rom then flashed di01. Now its working flawlessly
Sent from my SC2.9.2Voodoo/EC10 kernel/Nitro Ultra Honeycomb v3.1 using XDA Premium
I am one of the unlucky ones too. I don't think its kernel related. It does it on the OEM mesmerize kernel too (ec10). I think the only real solution is to wait for our OEM update and if it still does it take it in for an exchange.
Very frustrating! !
Sent from my SCH-I500 using XDA App
I had this problem, but once I wiped data, cache, dalvik, and flashed the newest SC 2.9.2, it went away.
a newbe i am wondering what is the differences between eb01 and di01????
newbe here what is the difference between eb01 and di01???
I haven't had a problem since flashing the jt's new kernel. Not yet anyways
Sent from my SCH-I500 using XDA App
mrtonee said:
newbe here what is the difference between eb01 and di01???
Click to expand...
Click to collapse
EB01 is a 2.2 froyo release (not official)
D101 is an early 2.1 eclair release (oem)
thank you...........
Switched the phone out problem gone
that'll do it..
How did you go about exchanging your phone? Did they make you replicate the problem?
Sent from my SCH-I500 using XDA App
I told them that it does it sometimes and it's completely random. I showed them the phone they made sure it wasn't rooted.... and then they said...ok, we'll mail you a new phone just send yours back
Shinebox said:
I told them that it does it sometimes and it's completely random. I showed them the phone they made sure it wasn't rooted.... and then they said...ok, we'll mail you a new phone just send yours back
Click to expand...
Click to collapse
Just spoke with a VERY nice man at VZW tech support. I explained my problem (leaving out a few particulars of course). He had me boot it in safe mode and wants me to run it that way till Monday. Hmmm, yeah. . .that is not going to happen. He said he will call back at 3:00pm Monday and see if my problem went away. I plan on telling him that it made no difference. Am I being unethical?
I would suggest Gizmo Droid's fix for CWM. I flashed through ODIN and checked Repartition like he said. I followed all of his instructions and my phone no longer gives me a headache. Since doing so, I do experience lag, but I no longer need to lock and unlock my phone to make it work.
Update: Downloaded official froyo and had same screen responsiveness issues. Called Verizon and they are sending me a replacement!!
I've been having pretty good success with Imanut's 100mV voodoo kernal with cpu clocked to 800mhz. However, the screen is still unresponsive when the charger is plugged in
Sent from my SCH-I500 using XDA App
Anyone ever had problems with their accelerometer and other sensors? Right now prox sensor is the only one working, according to phone tester app. Running bionix 1.3.2 with overstock, never had issues until recently, last few days maybe? Noticed that auto rotation no longer functions... only dropped it once, about 6 months ago, so I dont think it could be that.
Sent from my SGH-T959 using XDA App
took my first forray into the world of ODIN and went back to JFD and now sensors are working again...
so time to move into another ROM.
I have had this happen when flashing back to bionix from a GB rom. ODIN to stock fixed it in my case as well.
Hello well not sure but I think my GPS is "broken broken" like maybe something hardware related but just wanna to check with you guys first instead of doing anything drastic.
I think I first noticed when i was on a build of trigger(cm based) that the GPS kept searching for location and unscessfully tried the CM7 GPS script. I then just decided to Odin back to stock and getting the same results GPS wise. I also tried Nandroiding back to a ROM that knew GPS worked when i use to use it(toxic w7 clone) but still no luck. Also worth noting that while on Stock Odin I tried some different Market based GPS fixes(GPS Restore GPS Aids).
Any help would be appreicated thx
some people have working gps, some dont. mine kind of works but it takes forever to lock.
Big2hd said:
Hello well not sure but I think my GPS is "broken broken" like maybe something hardware related but just wanna to check with you guys first instead of doing anything drastic.
I think I first noticed when i was on a build of trigger(cm based) that the GPS kept searching for location and unscessfully tried the CM7 GPS script. I then just decided to Odin back to stock and getting the same results GPS wise. I also tried Nandroiding back to a ROM that knew GPS worked when i use to use it(toxic w7 clone) but still no luck. Also worth noting that while on Stock Odin I tried some different Market based GPS fixes(GPS Restore GPS Aids).
Any help would be appreicated thx
Click to expand...
Click to collapse
Did your GPS work in the past?
I used a 2.2 build of Trigger a little bit back, and it did the same thing to my phone. I have a "fixed" hardware GPS antenna (since I did the FFC mod, fixing the GPS at the same time was a piece of cake), so when I suddenly couldn't get any GPS signal, I knew something was most definitely up. I tried the sgps "fixes" to no avail.
Eventually I flashed CM7 (since gps wasn't working either way, at that point), then Odin'd to stock, then flashed Bionix 1.3.1, and suddenly at some point it fixed itself. Now my GPS is back to working on CM7, as well as 2.2 roms.
So, if your GPS used to work fine, there was something software-wise which screwed it up.
Do yourself a favor and call TMobile. Tell them that your GPS doesn't work and you'd like a replacement. Do it three times and get a completely different phone for free.
The Vibrant is a POS at best.
sroach23 said:
some people have working gps, some dont. mine kind of works but it takes forever to lock.
Click to expand...
Click to collapse
Hmm.. i did see a post where someone said it took 5 minutes to get a lock maybe I'll try the GPS test again for longer period.
reuthermonkey said:
Did your GPS work in the past?
I used a 2.2 build of Trigger a little bit back, and it did the same thing to my phone. I have a "fixed" hardware GPS antenna (since I did the FFC mod, fixing the GPS at the same time was a piece of cake), so when I suddenly couldn't get any GPS signal, I knew something was most definitely up. I tried the sgps "fixes" to no avail.
Eventually I flashed CM7 (since gps wasn't working either way, at that point), then Odin'd to stock, then flashed Bionix 1.3.1, and suddenly at some point it fixed itself. Now my GPS is back to working on CM7, as well as 2.2 roms.
So, if your GPS used to work fine, there was something software-wise which screwed it up.
Click to expand...
Click to collapse
Sorry bout that I should of mention that GPS was working in the past, never tried Bionix I'll see if that does the trick.
spiz516 said:
Do yourself a favor and call TMobile. Tell them that your GPS doesn't work and you'd like a replacement. Do it three times and get a completely different phone for free.
The Vibrant is a POS at best.
Click to expand...
Click to collapse
Yeah this what I meant by drastic but probably my only real solution, wonder how that works though im pretty sure I'm paying for some replacement/warranty but that's only if they find out it is broken or defective right?
So glad i bought a Vibrant for my birthday as my 1st smartphone
Well I think I made some progress here, I Odin back to Eclair and to Bionix. GPS still wasn't working but GPS Test shows that there are some Satellites "in view" but not "in use" weird...