yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] chorba69:
Hi people.

One question about this rom.

I used cm12 before and I have had problems with GPS. It never worked as it should and thats why i switched back to other rom / now to stock.

Can you tell me, do you have problems with gps too? Does google maps work as it should, location etc?

I have a d802 32gb and im in Europe.

Thanks!
[G2 Original Android Development] PsychoGame:
Hello Chobra69,

GPS on this device works perfectly in my case.

The sourcecode rebuild for the G2 device improved the overall CM experience a lot.
[G2 Original Android Development] gozzaa:
Gps works. Just tested with todays nightly
[G2 Original Android Development] Jeik:
Hey guys.

I had a problem on 21.8. nightly.

The hidden network I use keeps disappearing,so I would have to input the name and password again,every 2 hours.
[G2 Original Android Development] antond57:
GPS is working fine on my D802 / 32Gb.

Using daily with TomTom and with sports app's
[G2 Original Android Development] chorba69:
Thanks yall for answers!

I might switch to cm as soon as i root my device :)

One thing more.

Since I am already on official lollipop, after I root my device and flash recovery via Autorec v2 app, do I need to flash a bootstack or anything similiar?

Or I can proceed flashing the rom without flashing anything?

I have read that I need a bootstack to use cm.

If thats all true, can you tell me what to do and how to do it?

Thanks!
[G2 Original Android Development] th3ant:
Can I be that guy and ask about stability of any recent builds? I'm going travelling and would quite like to install but it would have to work reasonably well for a while as I won't have the ability to refresh..
[G2 Original Android Development] jl10101:
Stability wise it is A OK, havent had one issue like a reboot, freeze, showstopping bug etc.

The only thing that keeps me off of CM is the lack of a fully featured Quickremote, the slight volume variances throughout the ROM and camera quality. Otherwise, it works as it should. D802 if it matters..
[G2 Original Android Development] th3ant:
D802 is perfect. Good to hear no freezing/rebooting.. I've issues with that on some cm rooms I've been using lately. Lack of quick remote hasn't been an issue for me, camera is slightly but I'll live and sound can be adjusted with kernel tweaks right?

In any case thanks for the swift response!
[G2 Original Android Development] jaboneros:
One of my FB friends also using CM12.1 managed to get this to work (I haven't tried it yet, though) - LG quickremote for AOSP
[G2 Original Android Development] daniel.stuart14:
It works, but doesn't have even 20% of the features that stock has. It's because the ported app is very old, it was one of the firsts qremote vers. that were released for G3

I still waiting for someone port G4 qremote to aosp. (maybe now, that G4 is getting cm)
[G2 Original Android Development] ice124:
Still seeing reboots with my d801, same as all CAF-based ROMs. Running the 8/22 nightly. Same story as others, happens indoors in areas of bad reception.
[G2 Original Android Development] dr4stic:
Switch the Location setting on your device to "Device only", or apply the lib_loc_apiv02" hack mentioned a few pages back. As always, reading is key.

---------- Post added at 12:15 AM ---------- Previous post was at 12:13 AM ----------

I have a D800, but the process should be the same. If you're coming from stock LP and you used autorec, that should be all you need to do. Download CM, download a gapps of your choice (tk_gapps, opengapps, etc), put them on the storage of the device. Boot to the recovery, install CM and gapps, and then do a factory reset. Voila. Any more detail, please research on XDA.
[G2 Original Android Development] ice124:
I did read and investigate prior to posting. I tried that "patch" but it kills GPS, as is referenced in the supporting thread. I use the GPS and am areas that don't have good coverage, making network or wifi locks less effective.

I simply posted as a reply to the general query about stability. It's not there yet.
[G2 Original Android Development] dr4stic:
You mentioned the patch. Did you try without the patch (i.e... without replacing lib_loc_apt_v02.so) and simply setting the Location mode to Device Only?
[G2 Original Android Development] Flo0008:
[MENTION=2413393]Shelnutt2[/MENTION] [MENTION=4662457]Rashed97[/MENTION]

The last days I found a weird bug on the nightlies from the 14th until the 22nd of August:

I started the camera app, switched to the video mode and focused manually for three to five times. Then I wanted to switch back to the camera mode again - Suddenly the camera app froze and wasn't usable anymore (anyway, I could enter the camera app settings). By the way, sometimes I got an error which said that no connection to the camera is available.

I tried this many times again, first on the nightly of the 14th, then on the nightly of the 22nd august. Every attempt concluded in the same problem. On the Google camera app the same.

Thanks in advance!

Perhaps anybody else can try this too?

Attachment: Logcat (I hope it helps you), picture of the frozen camera app
[G2 Original Android Development] .wojtek:
just my 5 cents - it's either-either:

- without the patch - 'device only mode', no location if you can't get gps lock (and it takes waaay longer), otherwise - quite constant restarts

- with the patch (lib only, there needs to be modification of the sources?) - you get the stability, but you don't have the navigation... at all... so it's quite pointless;

I switched to the first mode and I'm hoping it will get resolved some time in the future :( I guess it's included in the CAF already so it should reach CM12.1 eventually?
[G2 Original Android Development] jaboneros:
read this late, I already flashed to 8/23 build. tried anyway but couldn't replicate your issue.

switching between cam and video is smooth on my phone.

D802

CM12.1 0823 build

TWRP 2.8.6.1 autorec

SuperSU Psuedopro 2.49 cyandelta for updating
[G2 Original Android Development] Rashed97:
Switchings pretty smooth on my D801. I'll keep seeing if I can replicate the error.
[G2 Original Android Development] Flo0008:
I tried it with the nightly from 23rd August and still the same. Like told above ... I open the camera app, switcht to the video mode, tap on the screen for four to five times and then switch back to the camera mode ... all the time the app freezes ... I am on D802 with the kernel delievered with CM12.1, and flashed your bump Rashed.

Anyway, thanks in advance :) Btw, did you find anything in the logcat?

Finally, here I made a video of it: https://youtu.be/6no9kgFvFsU
[G2 Original Android Development] chewdaniel:
i can confirm i'm having this issue too..... using google camera

switched to video and tap on the screen a few times. switch back to camera and it freezes. stopping the camera makes it available again.
[G2 Original Android Development] dr4stic:
Here's the problem I have with what you're saying. I don't understand it. Are you saying that, with a virgin system (no patch, absolutely certain it's what our lord the nightlies server intended)... when you switch to "Device Only", it's stable and stops crashing (and you've verified that)? Or are you saying it still crashes? Clarity is needed here with this solution.

Here's why it matters: i'm trying to drum up numbers to try and convince the devs to pay attention to this problem.

I've had this problem for months and reported it, but I thought (and they thought) I was the only one. They drummed it up to an issue with my phone. I didn't believe that, but I have a feeling it may be a problem with my SIM, and maybe everyone else's. In fact the problem isn't with GPS at all, but seems to be with Agps which comes from the cell tower and not from space. Some illegal call happens on missing AGPS data (when trying to grab said AGPS data and failing) which produces an unexpected result and crashes the UI. In fact, the offending call happens here. This is probably why most people that report the problem seem to have it in areas of bad reception.

There's no fix yet. No one quite knows why it's happening and I'm trying to get attention drawn to it. The devices are old and the devs are moving on to bigger and better things. It's not the easiest thing to do. I know I'm not labeled a dev, and my role is actually to test and "maintain" the d800 line, but it is very helpful, if only to help other end users determine if they have the same problem as you, to be clear about what you've tried and what does and doesn't work.

I know this problem is frustrating to many people for the EXACT same reasons they're frustrating to you. It frustrates me too. For the last 2-3 months in testing the pre-nightly builds (this has been on the table since about May/June) I had to explain to people why my phone would hang up on them anywhere from 2-30 minutes into a call. All the while analyzing logs and picking up clues trying to figure out when and why this was going on.

Thanks for your help.
[G2 Original Android Development] jaboneros:
happens on my phone, too. if you are in video mode and don't tap, switching back to camera works.

the multiple taps while on video appears to be the trigger for the bug. and then going back to camera produces http://imgur.com/VyBkKmK

need to reboot to make camera work again.

D802

CM12.1 0823 build

TWRP 2.8.6.1 autorec2

SuperSU Psuedopro 2.49 cyandelta for updating
[G2 Original Android Development] jaboneros:
ran PCMARK benchmark tests for performance and battery and here are my results for 0822 and 0823 builds -

http://imgur.com/kBbev14

scores above the collective data of LG G2 based on their database.

D802

CM12.1 0823 build

TWRP 2.8.6.1 autorec2

SuperSU Psuedopro 2.49 cyandelta for updating
[G2 Original Android Development] WoodmanMN:
Lock ups when streaming bluetooth music

I'm running a D800, have had this issue on 20150817 up through 20150822. When I am streaming Pandora to my car stereo, the phone will reboot itself after about 15 minutes. Also seemed to happen when using my bluetooth headset for voice calls.

Haven't tried 20150823 yet, but anyone else having this issue? Only thing "wrong" with the nightlies that I can see.
[G2 Original Android Development] dr4stic:
Go into your settings, set location to device only. Please report back if it works better or not. Make sure to reboot after making the change (the random reboot is not a real reboot).
[G2 Original Android Development] WoodmanMN:
Done, will give it a try over the next few days.
[G2 Original Android Development] .wojtek:
OK, I think I was quite clear but just to make things absolutely clear - with the 20150816 nightly when I switch from "high accuracy" to "device only" there are no crashes at all and device is rock solid.

Second case - if I change the library (libloc from CM11) I can set "High accuracy" and then there are no crashes (but GPS or 'device only' doesn't work at all).

Please see this thread:

http://xdaforums.com/lg-g2/help/random-soft-reboots-caf-based-5-1-1-roms-t3157912

There are a couple of commits related to the problem and it seems they nailed it down.

As stated above - I think it's fixed in CAF already (and CM12.1 is based on it - right)? I'm not ruling out possibility that it's related to some weird usage of AGPS (as in the sources that you've linked to) but again - not an android dev here so can't help more.
[G2 Original Android Development] dr4stic:
Thank you.

No, you're wrong. They aren't CAF, that "fix" isn't in or coming from CAF. That's not even a fix, the thread name clearly calls it a workaround. It's not coming from CAF, it's being modified on a repository for a specific ROM which uses a CAF kernel. The "workaround" has nothing to do with the kernel and thus nothing to do with CAF other than the problem appearing on CAF based ROMs. Why does the problem appear on CAF based ROMs you ask? Because the lg-devs LP kernel is a CAF based kernel and it's what most of the ROMs out there (including CM12.1) is based on.

It's also important to understand that what they did was to revert all the code to use the lib_loc api from cm11. That's very, very old code. That's not a fix. I'm trying to get an actual, reasonable fix. If we can get an actual fix, then that would be fantastic. The devs really really REALLY do not want to incorporate any early JB code from KK into the current LP version. If in the end they simply can't get something workable, then they'll go that route. But it's important to understand that it isn't the route they want to take, and I agree with that decision.

Of course, anyone building their own CM12.1 releases can incorporate the changes in the above link in their own builds and release them for the community.
[G2 Original Android Development] Rob014:
D802 user here, GPS causing reboots for me. Only way I can use maps is with battery saving, device only or high accuracy causes reboots. I have not applied any patches or any mods, untouched cm12.1 install.
[G2 Original Android Development] jaboneros:
I haven't encountered any reboots when using the Waze GPS app, using high accuracy, with mobile data set to 4G or 3G. The phone gets warm, but that's it. Why is it an inconsistent bug, i.e. some users have it, others - like me - don't?
[G2 Original Android Development] dr4stic:
I'm not really sure. I know it has to do with AGPS. I've been running my own builds and referencing back the crashes to the symbols and they always come back to that spot I mentioned in the code.

AGPS data comes from the towers and not from the satellites in the sky. It's availability has to do with signal strength. The people with the issues seem to have varying levels of connectivity issues. Some are in decidedly bad reception areas, and they're the ones that seem to exhibit the worst of the reboot problems. In these cases it wouldn't be surprising that the AGPS data might have encoding errors due to the signal degredation.

The devs used the lib_loc library and code from bacon (the OnePlus One). They thought it was a better base than the one from the G2 and since it used the same family of chips, should work fine. I think that something about the radio on bacon reports AGPS signal errors differently from the G2. My theory is that these differences are causing the call for AGPS data to fail and that's producing an unexpected result: the crashing of the UI.

I'm trying to steer the development towards attempting a build with LG's own LP version of the lib_loc. The original attempt didn't work out so well (hence, the switch to bacon's version). I guess we'll see what happens.

Another point to consider: the problem is triggered by cellular activity. You don't have to be using a mapping app to trigger the reboot. Sure it might exacerbate the issue a little and make it visible, but it isn't the root cause. Your phone is CONSTANTLY grabbing it's location for one reason or another. And since AGPS comes from the cell towers, periods of high data use expose it just as well. It would happen to me on phone calls when I entered my home, occasionally when I was streaming audio to my car through Bluetooth. In fact, until I learned to track the memory locations in the logs back to the symbols to get an actual line of code responsible for the crash... I thought it was a Bluetooth or audio mixer problem.
[G2 Original Android Development] jaboneros:
[MENTION=2096805]dr4stic[/MENTION], that sounds like a timebomb waiting to happen to me.. Do you know of any other rom without this issue related to AGPS? I would be using gps a lot and wouldn't want to have a reboot at the middle of a trip

D802

CM12.1 0823 build

TWRP 2.8.6.1 autorec2

SuperSU Psuedopro 2.49 cyandelta for updating
[G2 Original Android Development] dr4stic:
I don't know about timebomb. Like I said before, I've been helping build/test patches for the d800 device on cm12.1 for many months now, and this is the only real problem I've experienced. It's also one of the only places another device's code is used for our phone. And since I was the only one experiencing the problem in testing, they chalked it up to my phone. Otherwise, my phone has been absolutely rock solid. Just about as solid as my N5 has been.

There's just 3 things on my "needed fixes" list:

fix the random crashing on location calls

bring back the USB charging patches to open up the floodgates on faster charging

figure out why the hell you need to re-flash GAPPS whenever you upgrade from one build to another

Only one of those is particularly critical and that's the random crashes. And if you're worried about your phone crashing on a trip, just switch to "device only" (and make sure to reboot after the change). If you're driving you'll still have GPS, the worst that can happen is you'll end up with wonky locations indoors.

Sorry, I don't use other roms, I've never been one for switching much and I like that CM exists mostly everywhere :)
[G2 Original Android Development] barturblits:
Maybe I am just lucky with the lack of GPS reboots but if the issue is related to AGPS maybe this information helps.

I use cm12.1 Temasek from zg85 on my D802 and have not had a reboot yet. zg85 did try to use the old gps drivers at a moment in an experimental build, I am not sure what drivers are used in the latest build I am currently running but at least I know that I used builds before that with the newest GPS drivers without reboots. I don't have gapps installed but blankstore combined with µg UnifiedNlp with GSMLocationNlpBackend and Apple UnifiedNlp Backend. Maybe the issue is related to gapps? It's a long shot but who knows.
[G2 Original Android Development] ghost141:
battery kinda bad. wait for a better version.

I know it's kinda annoying for me to keep ask to fix battery problem.

But i really need it, cuz i usuallu working outside and hate to charge it when it rush situation.
[G2 Original Android Development] KiRAdot47:
I updated Cm from nightly 23 to 24 and ended up in a bootloop, no recovery.

had to flash stock again, bad luck? :)
[G2 Original Android Development] Jeik:
Bad luck.

For me everything worked.
[G2 Original Android Development] horst0815:
sorry to say that, but what in the world should a dev do with such a statement? You realize, that there are different people using the rom, hence, different usage situations. And now one guy comes around and complains about battery? No logfiles provided, no use of cellphone provided, no usage of apps provided... sorry, but next.

For me, battery is great. I get usually 1.5 days with MY usage of the phone. And for me, thats sufficient and I cannot complain about battery.
[G2 Original Android Development] Underworled:
Usé disable services ( for Google play services) servicely and amplify.
[G2 Original Android Development] marn3us:
What services do you suggest blocking with servicely?

Thanks
[G2 Original Android Development] jaboneros:
I only use rooted greenify and no other apps, including xposed. Very satisfied with battery, and results from pcmark benchmark reinforces my belief that the battery performs much better with this ROM than when I was on stock

D802

CM12.1 build 0824

TWRP 2.8.6.1 autorec2

SuperSU Psuedopro 2.49 cyandelta for updating
[G2 Original Android Development] berlen:
Hello everybody! I am on stock 5.0.2 but I am seriously thinking to switch to CM12.1 because I come from a nexus device.

What is the correct procedure to install it? I mean do I have to flash (once rooted) any bootstack or anything like that? Or do I just have to wipe and flash CM and gapps (like for nexus devices)?

Thank you for your help...

Keep up the good work!
[G2 Original Android Development] dr4stic:
Rooting stock LP on the G2 can be found elsewhere on XDA. Instructions shouldn't be hard to find.

Once you root you're likely going to run Autorec, because that's what the people do. Once you've done this step you've done everything you need to do. Your hardware firmwares will all be in the right place to do an install of CM-12.1

Recommended things once you autorec:

learn to boot into recovery without having an OS installed (there's a key combo not too dissimilar to the nexus procedure) -- See this discussion somewhere down the middle of the page on the d800 for instructions

upgrade twrp to blastagator's latest (not all together necessary, but the newer ones let you backup more partitions)

do a full backup of your stock install

Then just factory wipe, flash cm and gapps, just like you mentioned. Enjoy!
[G2 Original Android Development] gozzaa:
thats a strange thing that occurs on cm12.1

your recovery is still there and working but its hard as hell to enter it. i had the same problem and i could enter recovery after like 20 tries. really sucks.

i wish the developer could adress this issue. must be a problem of the rom since bootloader is not changed
[G2 Original Android Development] Mashed_Potatoes:
Finally fixed my phone, whats the status on cm12.1, how much of an improvement it is over 12? Hows the camera? Is AudioFX working? Bugs? Too lazy to go through 30 pages
[G2 Original Android Development] LRC1710:
I'm having random reboots in the latest nightly for d802 anybody else ?
[G2 Original Android Development] jaboneros:
I've had no reboots, no problems going to recovery. and never too lazy to back read ;)

Using this excellent rom as my daily driver since build 0815.

D802

CM12.1 build 0825

TWRP 2.8.6.1 autorec2

SuperSU Psuedopro 2.49 cyandelta for updating
[G2 Original Android Development] LRC1710:
might be that I upgraded straight from jellybean? I got the device yesterday and it came with jellybean and it said "your device is up to date" and I was like wtf? I rooted flashed latest TWRP then bootstack then JB bootloader then the ROM and gapps, anything wrong with that ?
[G2 Original Android Development] jaboneros:
see posts #28, #29

D802

CM12.1 build 0825

TWRP 2.8.6.1 autorec2

SuperSU Psuedopro 2.49 cyandelta for updating
[G2 Original Android Development] KiRAdot47:
and again, i updated from 23 to 25, same story > bootloop

i saw the last line, updating TWRP (it tries to change the recovery, the option to update cm recovery it wasn't activated)
[G2 Original Android Development] powwow12:
After updating to the latest nightly i get this: "Unfortunately, Google Partner Setup has stopped"

Im endlessly pressing 'OK' but it does not disappear. Wiping cache from TWRP and re-flashing gapps package does not have any effect either

Edit: solved following this

"Wipe the /system partition and reinstall both CyanogenMod and Gapps (as long as if you don't wipe /data, your data will be preserved)"
[G2 Original Android Development] maydayind:
Different bootloaders have different key combos for entering recovery. Don't complain about devs... It's LG who decides what keys are to be used.

If u can't even googel maby u should keep it stock.. Or by a iPhone
[G2 Original Android Development] Fobz:
Is there any way we can merge the following commits to prevent the reboots for some of us?

https://github.com/ZdrowyGosciu/device_g2/commit/7d8b49acf1c19093f2b612ec039f9f514edb8636

https://github.com/ZdrowyGosciu/vendor_d802/commit/513977138beb7a3b996fa7ffb9e182bacf4f4646

https://github.com/ZdrowyGosciu/device_g2/commit/0acc0c8e54814aba3598f21b79cd1e768459952f

Thanks!
[G2 Original Android Development] epapsiou:
Right. This is the way to flash nightly (d800 too). IIRC previous versions of CM did not require reflash of gapps when dirty flashing nightlies. Guess must be device/cm12.1 specific issue.
[G2 Original Android Development] foxmonter:
In last nightly 20150826, Chrome is not responding.. Anyone else having this?