Hi, i have a bell lgog. and i recently flashed CM10.1 on it. now when i go back to stock my proximity sensor doesnt work. its very weird. seems to work both on AOSP and CM10.1 when i reflash. but its not working on stock. Can anyone help?
Ive tried multiple factory resets and Tried Stock 'H' and 'F' Roms. it was originally on 'H' but it doesnt seem to be working. Works perfectly on any custom rom.
Related
Hey!
New Epic Touch guy here.
Everything is going good. Rooted no problem with the eg30plus and went from there to the LoStKernel. That went fine as well but I lost vibrate after doing so. I'm running no ROM's and have essentially went from stock to this. I reverted back to eg30plus and reflashed to LoSt, but I'm having the same issues.
Am I missing something? Thanks in advance!
Edit: I should also add that I have no WiFi working either. Says "error" in settings and I can't click it on at all.
flash an older version of same kernel.
1.0.0.2 is working fine, vibrate and wifi working.
Wonder what's wrong w/ 1.0.0.4? Most other people seem to have it working perfectly. Would installing a ROM help w/ these issues or do nothing?
Yesterday my gps wasnt working at all. It would not lock on no matter what I did. I was on a custom rom and I tried wiping my data/cache, reinstalling maps (just for giggles), and a multitude apps from the market that help deal with gps problems (gps fix, gps status, toolbox, etc).
When all this didn't work I decided to odin back to the last official JB update and still no gps. On a whim I decided to odin back to an ICS firmware and that made my gps work. I have no idea but it did. I then odin to UVDLJC, installed TWRP's most recent and restored my backup of the custom rom I was using in the first place and gps now worked.
While I'm happy as heck that my gps is now working and that it was not a hardware issue I'm extremely curious what happened.
I have flashed many roms lately and I cannot think what a custom rom can do to gps to hose it or if it was just one of those things. I would of thought that when I originally did an odin to UVDLJC that would fix the issue but that didn't. Whatever the flash to ICS did fixed it but what in the heck could that of been?
I figure if I can find out or get an idea what happened then I can steer away from flashing certain roms, or just be prepared that flashing any roms at all can make this happen again.
Same here.
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Typically, it's been when people are going from 4.2 to 4.1.
Zza1989 said:
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Click to expand...
Click to collapse
Well I used odin to flash an T999_UVALEM which was a prerooted ICS rom. After booting it up I checked to see if GPS was working and it was.
I then used odin again to flash T999_UVDLJA which is a JB rom and booted it up also and saw that gps was working. Then I just restored a backup of a room I had been using and GPS still worked.
I've been out of town and noticed that after flashing a few roms that gps wasn't working so instead of doing all the above stuff I just flashed a cm10 rom. I believe I either used a cm10 nightly (or maybe 10.1, memory is hazy) or LiquidRom and that got the GPS working by just doing that. Not sure if that will work for you but you could always backup your setup using TWRP's latest and then flashing a cm10 rom and seeing if gps is working and if that fixes it then you could then just reboot and restore the rom you are currently on and that might fix your gps for you.
http://forum.xda-developers.com/showthread.php?t=1949687
Hi everybody,
For a while I had been running Wicked rom (version 7 and then 8) without any issues at all. Data was great, wifi was working, calls and texts were made perfectly. Not a single issue as far as I could see. GPS was working just the way I was expecting it to (I use my GPS for navigation on a weekly basis).
I've explored other roms as well and I've never encountered anything serious or out of the ordinary.
Now this problem has appeared recently. Ever since I flashed a 4.3 rom (Infamous V9), my GPS has stopped working. It keeps trying to lock but never does. I've left it on for a long time too, it never locked; It just keeps searching.
I've even tried apps I've seen suggested such as GPS status & toolbox. Nothing I've done with those apps have worked. When I went back to the wicked rom (version 8), gps still did not work. Prior to the Infamous v9 rom, I had flashed the Cyanogenmod 10.2 rom and the gps was fine.
Now, regardless of what I do, the GPS no longer works on any of the 4.2 or 4.3 roms I've flashed.
When I flashed VirginRom (android 4.4), I had no signal on my phone at all, but that was due to my modem. I followed the instructions to odin flash the new modem and everything worked! On that 4.4 rom, everything worked perfect. More importantly, the GPS was working again and I was able to use it for navigation when I went out. I tried to test out other 4.4 roms. I flashed the dandroid google edition and cyanogenmod 11 on this forum. Both of these roms worked perfectly. The GPS was working and it locked within a few seconds.
When I tried to go back to any of the 4.2 or 4.3 roms, the GPS still did not work, even though everything else was fine.
I'm not the techie type of person, compared to so many people on this wonderful forum. I just do my best to follow instructions and learn from what is done ><. Does anyone here know what the issue I'm experiencing is?
Just for some added info:
I guess it's obvious my model is SGH-M919
Baseband changed though. It used to be MDL. Now it's M919UVUEMK2.
Any help would be much appreciated! Thank you.
Have you tried the app faster fix app? Also, do you have Google maps and earth installed?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
jtleniger said:
Hello,
I rooted my M919 and tried a few ROMs to hopefully find one that I liked, but it seems that they all have bugs that make the phone unusable for me. (Flashed a Google Edition rom, the proximity sensor didn't work anymore, so I couldn't end a call, ever).
Now I am trying to flash the stock firmware, and it seemed to have worked, except I get the com.android.phone has stopped, CONSTANTLY. I already have tried clearing data/cache several times, no luck.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Try using a different recovery. I've had that problem before, baseband and IMEI were shown as unknown and com.android.phone would force-close constantly. I don't know why the recovery would cause that, but switching recoveries worked for me.
I had this same issue yesterday, very strange that I would see this listed here about the same time. I haven't done anything different, that I haven't done before. Then I flashed the stock T-Mobile rom and it still kept doing it. Apn settings disappeared when this happened.
I know this seems to be a fairly common issue, but I've read & tried everything I could with no luck. Wondering what other options I have.
Been on a few different ROMs on my S-OFF M8 (vzw). Went from LiquidSmooth 4.4.4 to LiquidSmooth 5.0.2 and lost GPS. Most solutions say flash back to stock, get a GPS lock, then restore nandroid. Problem is, even when I flash back to stock (either KK or L), I still don't have GPS. Nothing seems to work.
I've tried flashing back to stock rooted roms and I've tried RUU back to stock rooted roms. Never get GPS lock. Any other ideas or am I SOL here?