Hey guys, so my OGP recently started having GPS issues, which got progressively worse as time went on. The GPS would just turn on at an ever-increasing frequency, and if I did not turn it off manually, it would eat up a lot of my battery. After some searching online, I found out that the problem is caused by CarrierIQ (AT&T). So then, I searched how to remove CarrierIQ, and found a beautiful guide posted by ghostfaceg35 in the LG G2 forums. I tried it on my E980, and it worked flawlessly. The guide is here http://forum.xda-developers.com/showpost.php?p=45672822&postcount=47. You must be ROOTED for this to work; I used this tutorial to root my OGP: http://forum.xda-developers.com/showthread.php?t=2362657 (credit goes to the original developers). After rooting and following ghostfaceg35's guide to a T, my GPS no longer turns on! Hope this fixes your issue if CarrierIQ was really the problem.
Related
Hey,
I know theres a lot of threads about htc/android phones freezing and crashing/rebooting but none of them really described my exact situation. And since it's getting worse and worse and driving me crazy, I wanted to ask for help.
As the title suggests my HTC Desire keeps freezing and crashing (sometimes rebooting, too).
It all probably started shortly before I first rooted my device, following the great sticky noob-tutorial. First problem was, that sometimes my phone wouldn't wake up from standby, especially after I a missed call (rooting didn't solve that problem).
Some time later, now rooted and with a custom ROM, I noticed, that sometimes when I wanted to use my phone, it showed the PIN-screen, which obviously means, that it rebooted quietly (don't remember if this also happened before rooting).
A few days ago it started to completely freeze, when connected to the charger. Orange LED showed it was charging but no reaction to pressing any buttons or disconnect the charger.
Since yesterday it also crashes randomly in standby mode (can't wake it up) or e.g. when watching a video (just freezes the device, no reaction to button-pressing, screen stays on etc.)
now I am running the stability test with the charger connected - no problem for 1h10min til now...
The ROM I am running is the latest cool sense (problems also existed before the latest update)
No modification of CPU (I used to use SetCPU but since I thought that would cause the problems I uninstalled it -> no improvement)
What could be the problem here? (And how can I solve it, of course?)
Anything else than a full wipe, which could help? (that would be my last option...)
Thanks for helping...
it just happened again -.-
I was just backing up some apps with titanium backup and in the middle of scrolling through the list - freeze!
dunno what to do...
is this hardware or software related?...
Hello.
It would be pretty easy if it is a soft problem. This kind of problems are usually dealt with by installing another ROM and see if the problems persist. So if you want to try and eliminate the last option, go and install another ROM, it can be a Stock ROOT-ed ROM, Sense or anything.
The fact that you mentioned your phone was crashing even before rooting got me thinking it is a motherboard fault. I've read some threads in which people had the same problems, and in the end they all got to the same conclusion: motherboard fault. The only resolve with this is to get it to guarantee.
So first of all try installing another ROM and if the problems persist, you will need to install a RUU and see if this one eliminates your problem. If not then I don't know if there is anything else you could do, besides getting it to the guarantee.
I wait for your progress.
Hi,
thanks for your reply.
The funny thing is, that I didnt have those problems with this ROM in the beginning. Everything was fine, that's why I was using it the whole time. But as I said before, it became worse by and by... thats why I thought it could be an app or so...
that would be a recent list of apps: appbrain.com/user/marioiram/
Cannot even sync my newest list, because after freezing while watching a video, it froze again shortly after reboot... still getting worse
Try reinstalling the ROM or installing another ROM.
hm.. just when I was thinking about following your advice, my desire stopped freezing xD
no crash, no freeze oder reboot since my last post.
I even tried to force it by watching videos, playing games, connect to the charger etc.
everything is fine... strange.
Will see for how long
Well this is good news. Just keep in mind what you can do if the rebooting comes back. Hope it doesn't
Well, it did xD
Now even shortly after reboot. I'll try ROM changes as soon as I get home but there's something I noticed: it often freezes when it's supposed to display a whatsapp notification and sometimes it seems there's a problem with the sdcard (just bought a new one because my old one went nuts). Sometimes the notification 'sdcard was removed unexpectedly' (translated from German) is appearing, but after waiting a few minutes everything is fine again...
Well I'll try some stuff when there's time...
Sent from my HTC Desire using XDA App
Hi:
I just wanto to let you know that I had the same issue, so I decided to send it to SAT, they changed the motherboard...
my problem now (with the new motherboard) is everytime I root my phone and use a cooked ROM, then freezes/crash again... ONLY works with the official ROM...
please let me know if you solved you problem pls... and how? of course...
I copy the link of my post (just in case helps to you)
http://forum.xda-developers.com/showthread.php?p=15103560#post15103560
best
SCeesarin
Hmm... I don't know what i did (nothing, actually) bit since my last post it runs stable... Absolutely nothing like freezing or crashing... Strange
Sent from my HTC Desire using XDA App
Hi guys!
I wanted to share a quite annoying thing I've noticed since installing the new stock gingerbread.
In short: my phone cannot be turned off. In addition it took me about a week to find it out properly, because it acts like switching off. There are two strange things: 1. it seems quite fast when switching on (it is actually, but it is more like returning from sg. like sllep/stand-by mode), 2. my battery was drained during the nights.
Now I have to enter boot menu, and select power off there.
I tried to search forums (this one and from other sites as well) but I couldn't find anybody else who experienced the same. So be aware of this new software, particularly because your phone cannot be downgraded or rooted yet (I hope someone finds a solution for this too).
Any ideas?
Thanks.
I think it's to do with Fast boot. You could turn it off and try.
Settings/ Applications and it's at the bottom.
Thanks a lot, I tried and it solved my problem immediately.
Actually it is quite embarassing, because it was only one single click. I couldn't remember of this fast boot option from FroYo, now my phone is usable again.
Thank once more!
Lol, that's the fastboot feature, which can be turned off.
Sent from my customized HTC Desire using TTP
Is this a known issue with the D851 and CM13? I keep getting a force close over and over and it won't stop unless I reboot the phone witch in turn disables Bluetooth. I can't seem to find anything about it other than one post with no answers. Here is a pic of the build causing the problem. Any way to fix this?
Same issue here. Seems to be caused by a commit to lg g3 update init in the cm changelog.
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
SovereignKnight said:
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
Click to expand...
Click to collapse
Looking at the changelog for the next potential nightly, it seems like it will be fixed. They added back part of that file.
See http://review.cyanogenmod.org/#/c/132118/
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
UPDATE: re-flashed, GPS is working fine.
I dirty flashed 20160212 and now my GPS doesn't work, but the Bluetooth messages have stopped on my D851.
mdphoenix said:
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
Click to expand...
Click to collapse
CM maintainers Forget our Device is BCMD unlike their devices.. so they think if it works for them, it must work for all.......
Only the D851/D856/F400/LS990 use BCMD while the others use that wcn crap.
as for data. Leave that to CM to mess that up to............. I had to go and fix my Device tree for PAC that CM totally screwed up.
your data issue is more a apn-cong.xml issue.. if you want a fix to that.. go read the last few pages on my Pac thread. and I listed a fix for data issues..............
Nice. Thanks!
..
Had this issues on an earlier build fixed it by reflashing
MuF123 said:
What was the fix?
Click to expand...
Click to collapse
A long hard road followed all of this. Lessons were learned, and in the end, nothing really gained. Except a working phone.
The entire issue started when I tried to flash SuperSU. Not knowing that CM didn't use SU. That began the decline. I ended up using the LG flash tool to put it back to an older stock version. It worked for a while, then I rebooted and it went to hell. Deader than dead. I shipped it off to a guy in Texas I found on Ebay to JTAG it. Came back just fine. Except I think whatever I did to it before then jacked up the charging. The phone wouldn't charge at all. Sitting on a charger for two days gave it about 5%. Come to find out, it was still under warranty. I shipped it to LG. They fixed it, returned it, and now it's on stock Lollipop, and I have to say - I quite like LG's interface. I've turned off a few things, installed Nova, etc. But at this point I have no reason to root or go custom. I did with my VZ phones because they were such nazis about everything. But I've got free tethering with Tmo. The phone works well. So, I'm sticking with what I have for now.
Hi, I would like to share my experience with this forum as I gained many tips from here, so giving and not only taking becomes obvious for me. Big thanks goes to Mr. Rusch for his excellent custom ROM and also for his idea regarding the solution to the GPS problem I was facing.
During offline navigation any GPS software on my phone was taking ages (from 30 min. to more than one hour!) to get a fix on the satellites even if it saw more than 20. I read a post from Mr. Rutsch earlier where he uploaded a modified gps.conf file but at that time my phone was not rooted. After I eventually decided to root it and flash his custom ROM the GPS problem persisted so I searched again and could not find his post but found another one with a very similar solution. I followed the steps and now my phone gets a GPS fix within a minute! So here is the link to the video, hope it will help others who encountered the same problem as I:
http://www.xda-developers.com/gps-lock-faster-xdatv/
UPDATE:
Unfortunatelly this fix worked for only one day. If a-gps data is cleared and downloaded, the fix goes quicker but still tricky... If anyone found a good solution, please share here.
UPDATE on 15.04.2016
I am more careful now posting things too early but for a few weeks now my GPS has been working consistently. What I did was I downloaded the gps.conf file made by Mr. Rusch and followed his instructions. This in itself did not solve the problem either BUT I discovered that in GPS Test (or in any software where sats can be seen) my phone did not see any satellites until I switched off GPS and switched it back again. Now I keep the GPS on all the time (I don't notice any increase in power consumption) AND switch off and on GPS right before/during I use any GPS navigation. This way I get a fix within a minute. A clumsy workaround but at least I can use my phone for navigation.
So this happens before but has always been able to resolve by restarting or reflashing the newest nightlies. However, this time no matter how many times i restart and reflash, it doesn't work.
Essentially my phone doesn't have sound, and all sound-related apps are acting strangely. I have found a similar case with same issues as mine but is a s4. link :http://android.stackexchange.com/questions/124501/no-audio-samsung-galaxy-s4
The poster mentioned he solved the issue by flashing a pack but I couldn't find the equivalent for g3. Can anyone help?
This should help :good: http://forum.xda-developers.com/lg-g3/help/lg-g3s-sound-cm13-whats-wrong-t3300246