yashsingh1/xdaforums huggingface dataset:
[Sprint LG G3] PervyPrincess:
Ya i put v2 and noticed I wasnt able to write in system as well. However, i just needed to put ring tones and noticed the sound section has a plus button now to add music files from any location, if that was what you were trying to do.
[Sprint LG G3] smithers987321:
Sound and volume problems

Everything was working fine but suddenly today the volume would turn itself all the way down, I would turn it back up and it would just turn itself back down when connecting to an auxiliary cord to listen to music in the car. Also, the Google voice thing would pop up suddenly interrupting the music for no apparent reason. Anyone know what is going on? It is driving me nuts.

Thanks
[Sprint LG G3] 53l3c7a:
Sounds like a physical malfunction. Something about that cable or your headphone jack is triggering the actions that headset control buttons can perform.
[Sprint LG G3] Koont:
Same here.
[Sprint LG G3] 991luy:
I also have the same problem with the Google voice poping up !! And sometimes my phone doesn't reconiza my headphones... I don't know what is going on!
[Sprint LG G3] engine95:
Which version are you guys running? TE is probably the only one that might do that. Try flashing the upgrade to V3.

That's all I can think of.
[Sprint LG G3] smithers987321:
I'm on V2
[Sprint LG G3] myxmastrmike:
So, pardon my admitted lack of research... but is the only difference between V2 and V3 is that one is odexed?

V2 is working stellar for me and I don't want to bother "rocking the boat" to upgrade if it will be of no real benefit to me..

Thanks!
[Sprint LG G3] engine95:
Maybe try wiping cache and dalvic in TWRP.

or

Wipe the app data in Settings>Apps.

I know google voice has created issues for all roms in the past. Google is tying apps together anymore, so you may need to do all Google apps.

In the changelog you can see what's different. I think guestmode/privatemode work in v3 while not in v2.

V3 is an update for people on TE. So you would need to flash TE then V3.

It MAY fix some things on V2, but idk.
[Sprint LG G3] churchey360:
Cant wait to try this ROM :) i finally got around to rooting my G3 (on ZVA) and only tried AOSP ROMs and this is gonna be my first custom stock ROM to try. Thanks!! [MENTION=1280108]engine95[/MENTION]
[Sprint LG G3] smithers987321:
I can't take this Google voice popping up thing anymore. Tried everything you recommended and nothing changed. Thanks, but I can't deal with this. Later
[Sprint LG G3] DHSoccer4:
no issues here at all with that pop up
[Sprint LG G3] churchey360:
Only force close i noticed was when i tried to turn on data connection optimizer in settings i would get an android.process.phone (or something like that) FC.. But its prob because of the removed sprint apps.
[Sprint LG G3] smithers987321:
Good for you? Thanks for telling everybody. That helps a lot.
[Sprint LG G3] solver404:
did you try ↑ ↑ ↓ ↓ ← → ← → B A yet?

maybe you just aren't good at this xda thing?
[Sprint LG G3] bhzmafia:
How go I get the weather and smart notice back when I upgrade from v1?
[Sprint LG G3] engine95:
You don't. Each rom is it's own. To see what's in each one, see the change log.

Other than what I've removed on each one, they're the same.

Or you'll need to see what I've removed and compare it to the one your on and add the appropriate files back in.
[Sprint LG G3] RandomPooka:
I'm looking to pass my G3 on to my daughter and I was going to flash BarePop v2. I found BarePapA while I was digging around for stock ROMs and was wondering if there's any functional difference between ZV8 and ZVA. I recall reading that Google implemented the password protection even after a wipe or some such in the ZVA update. Was there anything else of note? Just wondering if anyone has any input on whether I should go with a ZV8 or ZVA base.
[Sprint LG G3] engine95:
ZVA fixed a couple things. The one I remember is there's no more WiFi calling message in the statusbar.

Another, and I'm not positive, but if your do a factory reset, it doesn't wipe your internal SD. At least Flashtool didn't when I used it a while ago.

Really, it's just the latest. That's about it.

Edit: Whacha gonna go with this time? ;)
[Sprint LG G3] RandomPooka:
That's cool, though. I think I'll just backup my CM12.1 and pull the trigger on this one. I should only be running it for a few days, but that will be long enough for me to get used to it in case my daughter has questions about where some feature or other is.

Appreciate your hard work and the fact that you answered me (not to mention that you answered quickly!!)
[Sprint LG G3] RedNak71:
Sweeeet unlimited lives now!!!
[Sprint LG G3] DjMizzTikk:
Dude chill... Prob is the aux cord or something else.. also what can help is flashing everything freshh.. TE then v3 i had the same issue and went away. Also try goin Bluetooth a bit better and less hassle.
[Sprint LG G3] DHSoccer4:
:crying:
[Sprint LG G3] macho9556:
Multirom

I've been trying to get this to work with multirom but with no luck.

Any light on the subject will be very appreciated, thank u in advanced. Right now I'm running xenonhd as my primary but would like to have a stock ROM also because of Bluetooth issues and camera.
[Sprint LG G3] engine95:
I couldn't either when I tried MultiRom.

I think Multirom doesn't work for us. I even tried building the kernel with Eliminater's help and no luck.

I need to get with him again and see if he has anymore insight on adding the kernel patch.

There was something about memory banks. His patch is for 4 and we have 3.

If you want, flash skins1980 oversharpening fix. It's working for others with bumped bootloaders. I didn't try that. You'll find it in the Multirom thread OP.
[Sprint LG G3] macho9556:
OK, thanks. I will give it a try. Flash oversharpening fix to the barepapa ROM in the multirom section for secondary ROMs or flash the fix to my primary ROM? Thanx for your response
[Sprint LG G3] engine95:
Flash it on BarePapA. It won't work on CM/AOSP.
[Sprint LG G3] macho9556:
Thank you. Will give it a shot
[Sprint LG G3] RedNak71:
No APN's. How can i manually set my apn? I have not been able to send or receive any mms messages. Anyone else having this problem? I cant seem to find the right menu in shortcut master. Any help would be great. Im not getting any at all. When i check my apn is says no apns.
[Sprint LG G3] Valsorim:
Refer to post #2 of this thread. Try the first two, but I remember I had to to do ##rtn# when I had this issue, you need msl
[Sprint LG G3] RedNak71:
Hey thanks for the reply. I do have my msl number but couldnt remember if ##rtn# resets my phone and loses root. Its not worth bringing it all back from a near factory reset.

Edit: I went ahead and did the rtn. Had to restore apps but looks like mms is working again. And my Wi-Fi hotspot came back too. Bonus!
[Sprint LG G3] myxmastrmike:
Has anybody been able to get Android Pay working with this rom yet? I've tried every workaround I can find, and nothing works...

I get all the way to the end of setup and get this error

http://i.imgur.com/oKjdHFV.png
[Sprint LG G3] Macguyver:
So is there not a way to link ring tone and notification volumes in LP anymore. I know the aosp roms have that option but did LG screw that up? It's most annoying when I just lower my ring tone down so its real quiet at my desk then an text or email comes in and it's super loud because the notification volume is still set to full.
[Sprint LG G3] Valsorim:
Hit volume up or down, on pop-up hit settings button and should be there

or

Pulldown notification, hit settings button on ringtone slider to get there
[Sprint LG G3] Macguyver:
There's nothing there to link them. If I adjust the ring volume, the notification doesn't change with it. I find it really annoying.
[Sprint LG G3] klarthur:
That error is because Android Pay will not allow you to add a card on a Rooted device. There is a workaround however! Go to SuperSU > Settings > and uncheck "Enable Superuser". Now go ahead and add all the cards you need to add on Android Pay. Now go back and check "Enable Superuser" and Android Pay should work just fine. For whatever reason Google will not allow a rooted device to add cards, but they can use the app. If you use this workaround it fools the phone into thinking it is no longer rooted and will allow you to add the cards!
[Sprint LG G3] RandomPooka:
Be glad that you can do that. They won't enable Pay if your bootloader is unlocked (not Bumped, but genuinely unlocked)
[Sprint LG G3] myxmastrmike:
I had tried that (and a method using an xposed module called Rootcloak) before i made my post and it 100% did not work
[Sprint LG G3] Valsorim:
I miss understood what you were wanting, but just tried Linked Volume Control at playstore and that links them together with this app. Hope that helps. It was made from Samsung device but just tested and it works
[Sprint LG G3] Macguyver:
Thanks, I downloaded "simple volume" and that works well too.
[Sprint LG G3] jcfunk:
Worked for me, just installed. Didn't hid root, but I do have mount namespace separation unchecked in superSU. Also xposed installed.
[Sprint LG G3] myxmastrmike:
Weird... I just tried unchecking that on mine and it still didn't work.

I even went so far as to roll back google play services to stock, uninstall Android Pay, uncheck Namespace and enable superuser, then restart... from there I installed the updated google place services, then installed Android pay, went thru the setup and got the same result.

There has to be another variable blocking me (and others) if you were able to do it successfully...

In the mean time I just uninstalled android pay and new wallet, rolled back Play services to stock, installed v7.8.99 and Google Wallet v9.0-R206-v27 (last version before android pay) so I can have everything working till a universal fix comes about
[Sprint LG G3] chrisctb:
Yeah I can't get pay to work either. Tried everything people have said. Someone will figure it out!
[Sprint LG G3] thegold3nchild:
thats the method i used to get it to work on Stock_ZVA_L_Odexed when android pay was first released last week and can confirm it works on barepapa as well...
[Sprint LG G3] chrisctb:
Thanks man that method worked!!
[Sprint LG G3] dkratter14:
The old Google Wallet worked differently than Android Pay does.

When you paid with Google Wallet, you paid with a virtual MasterCard number that Google assigned to you, so Google/MasterCard handled the transaction with the vendor, and then dealt with your bank. So your bank knew nothing about the vendor transaction or what Google Wallet was doing, only about the MasterCard transaction.

When you pay with Android Pay, you're paying directly with the credit/debit card you added, so your bank handles the transaction with the vendor. It knows all about Android Pay, and needs to support it.

That's why the same card can work in Google Wallet but not in Android Pay, if your bank doesn't support Android Pay.
[Sprint LG G3] myxmastrmike:
See thats just it. the same two cards DID work in Google Wallet and Android Pay.

The issue came when I needed to replace one of those two cards...

It was like this:

card#1234 is for account A and card#5678 was for account B. Both were added to and used in Google Wallet.

When I finally got Android Pay working, both cards were able to be added (by confirming the security codes on the back of the cards) no problem at all.

Then I received card#7654 for account A (this replaces the other card since it was expiring soon) so I delete the original, completely added and working card for account A, then attempt to replace it with the new card and it tells me my bank doesn't support Android Pay.

How can this be when my two cards/accounts from that very same bank 100% worked in both Google Wallet AND Android Pay?

I read elsewhere something to the effect of "any cards that were added to Wallet prior to the update to Pay are "grandfathered in" and will continue to work...so, in an attempt to make things work I rolled everything back and installed the OG Wallet app, added my new card#7654 in the app, it adds absolutely fine. For good measure I even went out and made a purchase using that card in Wallet. I am waiting for that transaction to be marked 'complete' in the transaction history before I then install the updated Play Services and install Android Pay and go thru the setup again.

I am hoping that since the card was added via Wallet and used in Wallet that it will then meet the criteria to be "grandfathered in" like my other two cards were...though, I suspect that the deal is that it is any card that was added to Wallet before Android Pay was RELEASED falls into that Grandfathered designation.....

We'll see!
[Sprint LG G3] dkratter14:
The cards that were added in GW and that now appear in AP are still using the virtual MasterCard from the GW days. So your bank still knows nothing about the vendor transactions, and that's why it still works (and what they mean by grandfathered in). They're not going directly through your bank like they would if you delete them and add them in AP as new cards.
[Sprint LG G3] myxmastrmike:
I suspect that too... And if that's the case I could care less.

I just need to be able to use the card that is for my "Account A" that I described above since it is my primary account otherwise Android Pay is useless to me.

If they've got to still do the virtual Mastercard on the back end, whoopty-doo...

But if this doesn't work, then until my bank plays nice, I'll just continue rockin the rolled back old school Google Wallet app in the mean time...
[Sprint LG G3] Trident:
Wrong thread. Sorry.

Sent from my LGLS990
[Sprint LG G3] cabbieBot:
rejoice my friends, for we are saved. The Great El Gee is merciful, and has delivered us from our long national nightmare of remote code execution via an appropriately badass-named protocol, 'stagefright'

Now to remember how to get this **** off my phone and keep it off. Again.

I haven't even checked the other threads so I dont know if this has been done, but I went ahead and pulled the OTA update.zip out of /cache and hosted it on medifire in case it should be useful to engine or others: LS990 Stagefright OTA update.zip
[Sprint LG G3] churchey360:
So is this a new update for our phones?
[Sprint LG G3] engine95:
It must be. But don't install it! You'll risk losing root/unlock!

To be on the safe side, we need to wait for [MENTION=2684188]autoprime[/MENTION] to have a look at it. Or come up with either the tot/img files.
[Sprint LG G3] cabbieBot:
LISTEN TO THE MAN! Do NOT install it! I've never even heard of an OTA -not- eliminating root. Just seeing that OTA notification freaks me out, I treat it like a live bomb that could blow up in my hand.

How is this done, by the way? I'd like to take a look at it.

---------- Post added at 12:48 PM ---------- Previous post was at 12:45 PM ----------

This link will tell you what you need to know. The update I got (and which you'll be getting soon enough) is basically an emergency hotfix for a nasty lil security hole in the Android OS. Don't expect new features or anything except maybe some minor bug fixes . . . this is 99.99% a security patch.

Vast Majority Of Android Devices Are Vulnerable To 'Stagefright' Exploit That Can Be Executed Via Text Message, According To Researchers
[Sprint LG G3] engine95:
I don't know what to look for, but autoprime is part of the root team. He seems to be our link to them. And I trust him wholeheartedly.

There are ways to avoid the issue which are posted all over the web. So for me, I'm not that concerned. And I'm in no hurry for the update.

I'll put a stock rom together when we get the tot/img. Unless someone else does it before I get the time. ;)
[Sprint LG G3] cabbieBot:
I gotcha. Are you getting one of the new Nexus devices being announced in a few days, or stickin with ol LS990? I'm probably moving on myself . . . I sort of got stuck with the G3 because I lost my Nexus 5 and have been waiting to get back into the sweet motherland "fastboot oem unlock". LG's double-tap to wake and rear volume buttons/cameras have really spoiled me, I'm going to miss those a lot. But f-u-c-k bumped bootloaders, I want the pure stuff in my veins. Regardless, your ROMs and kernels have made it a fun detour so thank you, sir, for providing me many hours of fun tinkering over the past year. My only regret is that I never did find a foolproof way to completely defeat the LG Cliptray, much to my dismay and shame. God I hate that thing with the heat of a thousand suns. It's always baffled me how you folks seem okay with that crapware. If for some reason the fates decide to torture me, and something similar to the cliptray ends up being an unremovable part of stock Marshmallow, I'm just going to say eff it and get a Palm Pre. ¸¸♬·¯·♩¸¸♪·¯·♫¸¸WebOS, I'm comin home to you.¸¸♬·¯·♩¸¸♪·¯·♫¸¸
[Sprint LG G3] engine95:
Thank you.

Palm Pre!? I LOVED that phone! I wish I still had it, many a time. To bad HP couldn't use WebOs properly.

I've still got a few months left, so ill see what comes out then. I'm actually pretty happy with this phone as I have old eyes. ;) As for the clip tray, I just deal with it, but it has been handy a time or two.
[Sprint LG G3] geeksmurf:
Former Palm Pre'er also. I miss that little thing so much. But my eyes sure don't miss how small it was. I'm kinda excited by the new Android BlackBerry.
[Sprint LG G3] autoprime:
thanks for the heads up.

after a quick look.. it looks like it was mainly for stagefright. I can confirm that anti-rollback has not been used in this update (like flex 2 and g4) so people who take this ZVB update will be able to downgrade or use the ZVA TOT etc without any worry.

can't confirm if the current root method is blocked or not BUT Codefire has adapted a newer method that we use on the G4.. still using download mode to root. I am positive that the G4 method will work to root the device (worst case). It's possible the current method y'all are using would still work but hard to say without actually poking around on the device.

after some more poking around.. seems the old root method isn't going to work. I could make a hybrid root method that uses the newer Sprint g3 1-click... and incorporating some elements from our G4 method... could be risky... but it depends.

Using the current G4 method as is... it'd require someone dump the ZVB system.img.. root it using Linux.. then uploading it for all to use. Then the users would flash the pre-rooted system.img thru download mode (our current g4 method).

Here's our root thread - http://xdaforums.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765

but since no anti-rollback is being used... I'd say this is a safe update. downgrading is possible via TOT. But there won't be a root method for a lil bit.

Let me test some things and see if I can get around needing a pre-rooted .img.

also thanks to [MENTION=2477252]cabbieBot[/MENTION] for pulling the update.zip. it's always nice not to have to hunt around for the update myself.
[Sprint LG G3] engine95:
[MENTION=2684188]autoprime[/MENTION]. Do you think the way we've been keeping root for ZV8, ZVB will still work? Just using the img files from the. tot? As that's just a bootloader workaround, right?

Thank you for looking into this. VERY MUCH APPRECIATED!! :)
[Sprint LG G3] autoprime:
how were u previously "keeping root" ? by just flashing the system.img thru twrp then flashing supersu zip or having twrp root you? instead of taking the OTA? if that's what you mean then yes it should work still.

if not.. can you explain? I've been living in G4 world trying to keep up with LG.. so not sure what G3 users are doing anymore. All I've done was take a look at the modded script people were using for ZVA which looked like it was flashing a downgraded download mode (laf) while in download mode.. then flashing a root script in the downgraded download mode. But that seems to not work anymore.
[Sprint LG G3] engine95:
Something like that. Honestly, I can't remember for sure until I sit down and do it. And I've done it 3 times now. Lol I do it all on my phone, then pull the system.img.

I'm pretty sure I'm using the .tot to do it though.

I need to go through all my messages and see how I've explained it to others in the past. Getting old sucks.

I understand about the G4 stuff. I've been reading on it. So no need to apologize.
[Sprint LG G3] autoprime:
if you already have twrp installed on the phone... then yes you could flash the ZVB system.img as well as a bump'd ZVB boot.img.. while staying on the older bootloader.

but for those who update to ZVB via OTA or some other method.. they will need to either downgrade and use a proper root method for the downgraded sw version... or wait for new root method (g4 method.. just needs some tweaks for sprint g3).

I'm assuming there are still some LS990 users who want root.. but do NOT want TWRP.. so they will be the ones who most likely want a new method. while anyone already on twrp just needs to wait for system + bump'd boot. There are some other ways to go about it.. but they can get a little more risky and it's not worth the trouble.

gonna watch a little tv and relax for a bit.. but I'll get the updated root method sorted.. along with something for the current users already on twrp... and yourself so you have a new rom to tweak. :good:

I have some thing's I want to test first.. but as long as nothing goes wrong in my tests I should have something late tonight or early tomorrow.

*update*

Got TWRP installed. Things seem to be going as planned. Still work to be done... but this is good new of course.

*update 2*

Methods for stock ZVB users and those already with TWRP all finished... just waiting on some Codefire server updates before I can upload the files. New thread in the Sprint G3 Development section coming soon.
[Sprint LG G3] engine95:
Thanks [MENTION=2684188]autoprime[/MENTION] I was just working on modifying the update.zip to see if I could get it to work. I'm sure I'll still try it.

But at least you've got a sure-fire way.

Thanks again. :D
[Sprint LG G3] engine95:
ZVB should be out tonight if all goes well. With some sugar added. But should I keep the name? BarePopB? BarePapB? BareBarb? Suggestions?????

V1 will be totally stock, but with....

Init.d support

busybox

increased mixer paths

sd card fix

LG Backup to /data

Sprint VoiceMail to /data

So far. ;)