i am having the persistent launch of locations.apk.
i was once using cm7 and experienced auto-launch of car mode. i decided to flash another rom, this time RCMix 3.3. I thought the issue will be resolved by flashing new rom but i was wrong, i am experiencing it until now.
Can anyone help me out and explain the probable cause of this issue? i bought my desire hd in second hand condition and i am afraid that it is due to any hardware defect.
your help will be greatly appreciated. thank you!
PS: i am thinking of deleting the locations.apk as well as the locations laucher.apk, is it safe?
thank you
i had the same problem for a while with android revolution, thought the same as you flash something else see if it´d fix the problem but it happened again. it sorted itself out in the end, not sure why but from what i can gather is that it has something to with the usb port, check if it has some fluff or other debris inside.
again like i said i´m still unsure what exactly sorted my problem but it did stop happening after blowing into the charge/usb port and plugging it in to charge so i assume that that worked. its been two/three months no problems since
i got the issue fixed, too! i installed blackice CM7 rom, now the locations/car mode isn't launching automatically now. currently running blackice rom for 19hrs now and now sign of said issue anymore!
thank you, ponk2k. yes, i did read a lot of threads concerning that issue but i haven't tried cleaning or doing something with my usb port. and i am in denial that my usb port is defective
anyway, i hope the issue wont bug me anymore.
thank you again
Related
I'm pretty much having the same issue as:
CM Issue 2851: screen remains blank after call..
..except my phone is the HTC Slide (HTC Espresso), so the fix doesn't work.
Does anyone have a similar fix for this? Basically it seems as though my proximity sensor is malfunctioning.
I've tried wiping and installing CM6.1.1, CM7.0.1, & CM7.0.3. All have the same issue.
Sorry I couldn't post the link to the CM Issue because of the forum's spam protection.
Thanks for any help in advance!
I had this issue awhile back and it lead to other issues as it was a hardwware problem not a rom issue which is wwhat it SEAMS is happening to your phone as well.
cidica said:
I had this issue awhile back and it lead to other issues as it was a hardwware problem not a rom issue which is wwhat it SEAMS is happening to your phone as well.
Click to expand...
Click to collapse
But people having the same problem (from CM Issue 2851) were able to fix it with that proximity callibrator app. But the app doesn't work cuz it wasn't made for the Espresso.
Does anyone know of a proximity calibrator for the HTC Espresso (HTC Slide)?
cidica said:
I had this issue awhile back and it lead to other issues as it was a hardwware problem not a rom issue which is wwhat it SEAMS is happening to your phone as well.
Click to expand...
Click to collapse
cidica, did you end up replacing your phone because of this problem?
My sons was doing that, ended up being a faulty ribbon cable, replaced the cable and all has been fine since.
Sorry this is late been kinda busy. Yes i did end up replacing the phone cause of it. I called T-Mobile and talked to one of the reps there and we went through a quick troubleshoot (since i had been troubleshooting it myself the entire day). I even went as far as unrooting the cell and going back stock with the same issues. The rep i talked to just said ok well im sending you a new phone few days later i had my new slide.
Sent from my HTC Salsa C510e using XDA Premium App
Hi,
sometimes the touchscreen of my defy stops working (but the phone is not frozen)
and the only way to fix it is to lock/unlock the screen...
does anyone have the same problem (and can help me)?
thanks
P.S
i've had the problem both with stock rom (2.2) and with cyanogenmod rc 1.5
When this happens, do the 4 buttons below your display still give you haptic feedback (little vibration) or do they react not at all?
Also, does this only happen when there's the normal launcher/standby screen active or when there's an other app active too ?
Did you undervolt ?
Edit: Also, this seems to be a hardware problem which seems to be well known in a certain German android forum but I cannot find much about it in here. In short, the digitizer unit seems to be broken for some people and locking/unlocking helps because it disconnects and connects power for the digitizer. The people there fixed the problem by replacing the digitizer (which isn't easy at all!).
It would be nice to have someone from XDA who had this problem before too, to confirm this problem!
First of all, thank you for the answer
When I have the problem, 4 buttons stop working too.
It usually happens after a period of stand-by, i don't undervolt or have some other application running than the launcher (ADWlauncher).
I bought the phone one week ago, if it is an HW problem, i can't repair it by myself...
I'd recommend to wait and see whether xda has other suggestions for you and if not, just check the Motorola hotline and ask whether they know something and if they do change it for free.
Also, what you describe fits perfectly to what I've read elsewhere (don't know whether I'm allowed to post a link here or if it were useful at all because it is in German). So it sounds like your digitizer could really be defect.
ok, even if i hope to solve the problem by myself...
News: They've changed the touch screen, but the problem is still present...
Can it be a sw problem??
Keep sending it back, they will replace it in the end.
Sent from my MB525 using Tapatalk
the whole phone?
Yes, the whole phone. They have two year warranties, but don't put up or make do, you should have a phone that works right
Sent from my MB525 using Tapatalk
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
I wonder when it happens ,are you charging?
nameite said:
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
Click to expand...
Click to collapse
What nightly version are you using?
The problem happens even if i'm not charging...
Hey, I really didn't want to have to start a new thread but unfortunately as i have not posted before i could not post on the development thread for this ROM.
Basically I managed to successfully install SGBS 2.8.2, or i though i had. It boots fine but when it gets loading sense it gets stuck at the sense loading box, I am not entirely sure what may be causing this problem but i thought it may have something to do with me using a class 2 micro SD card.
Being that I am relatively new to the whole ROM and flashing scene i am not exactly sure on how to effectively troubleshoot the problem without posting on here.
I hope someone can help me and thanks in advance to anyone that is able to.
Thanks , Luke.
Sorry to re-post, I just realised that I missed some information that may be important, firstly I am using the stock Hboot version of SGBS, so I am not sure if perhaps that could be causing an issue as I am unsure as to how different boot tables would affect the loading speeds, if the would at all.
Also I have been experiencing problems with the flashlight on my phone, it began when I was using the flashlight apk and it randomly started becoming out of sync with the level of brightness that I selected within the app so I uninstalled it, now the flashlight LED randomly turns itself on for no reason, I did some research and I thought it could have been an issue with the proximity sensor but after downloading an app that reads the values for the sensor I discovered it wasn't.
I really am clueless as to what to do in an attempt to fix any of these problems but it certainly is becoming really annoying.
Thanks, Luke.
Flash a ruu and see if your problems are still present
Sent from my HTC Desire using XDA App
Yeah, I have thought of attempting to flash a RUU to fix my flashlight problems however I still cant figure out how to fix SGBS hanging at the loading box for sense. It's weird because I can still receive calls and use the notification bar and quick settings but sense just doesn't seem to load :/
Right well I just flashed the official HTC 2.3.3 RUU and it has not fixed any problems, ,my flashlight still randomly turns itself on and off. Although for some reason flashing the RUU did not s-on my device which it has done every time I have flashed my RUU.
Sounds like a hardware problem if the ruin has not fixed it
Sent from my HTC Desire using xda premium
Yeah, it has turned out to be a hardware fault so I contacted virgin and they sent out a new phone the next day. So all of those problems are fixed.
However I am still not entirely sure as to how to get SGBS working properly, the installation instructions for it are pretty vague so if anyone could give me some more detailed instructions for this ROM it would be greatly appreciated.
Hello xda members! I have been experiencing a strange problem with my "T-Mobile G2"'s microphone and would like to share it with you in case you had any insight on it:
My phone's microphone is not working - I cannot use voice input, music recognition services, etc. all it picks up is silence. What makes it a "strange" problem? Well, the microphone will work during calls, but ONLY IF I first snap out the keyboard and then snap it back in! Sometimes the microphone will fade out and then go silent again, at which point I'll open/close the keyboard again so that the other party can hear me again.
I thought it was software at first, but then I flashed it to stock and still had the same issue. Now I'm worried it might be a problem with the ribbon cable that connects the two halves. Have any of you ever heard of a similar problem? Any suggestions as to how I might fix it?
If it is intermittent and you reflashed then my guess would be hardware like you suggested.
Most likely you mic is loose. Does it behave the same as opening and closing if you just hit it or shake it?
Sent from my ghdudsjihfr using dhhcdfhuf.
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
jervill said:
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
Click to expand...
Click to collapse
Do you superwipe?
killj0y said:
Do you superwipe?
Click to expand...
Click to collapse
Yup I did use superwipe.
Incidentally, the issue returned after 2 days of working perfectly. Doing a wipe and then installing that same ROM fresh (not a backup) did not fix it so that new most likely ROM had nothing to do with it. I'm giving up then and calling this a hardware issue, period. I guess it's a good thing that the HTC One phones are are coming out soon!
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
kozij said:
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
Click to expand...
Click to collapse
I had this same problem for two different reasons with two different phones.
The first time, which seems unlikely for you, was a problem with DSP Manager that comes with CM9 causing my phone to crash and restart.
The second is manufacturer error. The phone has a titanium case, and due to some errors in assembly, when I would plug in headphones, the system would freeze and restart. Because I still had warranty, I had it replaced and the problem disappeared.
If you have a multimeter there are ways to check for a short, but I'm not sure if you are familiar with this.
Hope this helps!
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
blutooth
Sent from my HTC Vision using xda premium
kozij said:
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
Click to expand...
Click to collapse
If you still want to try and find a solution, get some electrical tape (or another strong insulating tape) and cut off a thin strip lengthwise (about 0.8-1cm width x 3-4 cm length) and tape it to the top of the headphone plug on your headphones so that it blocks any contact with the titanium.
demkantor said:
blutooth
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I use a pair of Bluetooth headphones and a Bluetooth-enabled car radio. But alas, if you care a lot about your sound quality, then Bluetooth certainly is *not* the way to go.
But if you care that much about audio quality, you would have a dedicated device which uses all it's processing power for playback, right?