yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] reliant_turbo:
im thinking about trying this rom. (on 47a stock debloated) and im still a little confused about this process. do i create a folder (directory) in /sdcard/ named (insert tweak name from the first post) or do i do something like paste a text file in there and rename it (insert tweak name from the first post)

since you have used both and are currently on 47A (still, right?) which is snappier/smoother/better battery life?

i have killer battery life on 47A and dont want to lose that but games (like smashy road wanted) seemed to be smoother on lollipop roms. even with the governor cranked up/modified, that game is still super choppy seemingly for no reason..... i mean, the graphics are terrible... theres no reason why it shouldnt be 60fps all the time.

also on 47A, ive been having an issue first thing in the morning where the phone hangs hard when coming out of doze and i swipe the lockscreen to unlock.... all the lockscreen icons/clock/etc remain on the screen while the phone home screen appears..... pressing the power button and trying again seems to fix it but its never done that on 35b roms or on 46A. only change that i can think of before this started was installing and tweaking (alot) flat signal bars stuff.

thanks

Brian
[Verizon LG G3] roirraW "edor" ehT:
No, not a folder. Yes, you could paste a file in there and rename it although the file manger I use (X-plore) you can just create an empty new text file. If you paste one in there I'd open it and make it blank, or do whatever else is necessary for the one or more tweaks which requires some particular text in the text file.

Yes, you're correct. Overall, I'd say this (VS985 v2.0) ROM is my favorite, even over the stock 47A firmware. 47A seems just a tad snappier and smoother than this ROM - enough to notice but fairly subtle difference I don't feel that alone is enough to sway me from holding this ROM in high regard.

If you search this thread and the 47A thread for posts by me that contain the word "battery", you might find screenshots I did. I know on 47A with Greenify's Aggressive Doze option that with my relatively mild use of my phone (50 minutes screen on time) that at least 2-3 times now I've gotten upwards of 120 hours between charges. I believe all those times have been on long holiday weekends when besides my normal behavior of not really using my phone much, that I also was staying in one place (home) a lot so I'm guessing the phone didn't have to look for a signal at all.

I don't play games much, really hardly ever because nothing these days seems to keep my attention. Unless it was you I'm thinking of, at least one other person reported lag on the lockscreen on 47A - I haven't had that issue at all, so I don't know what could be causing that, and I use Flat Style Status Bars Xposed module to customize all of my status bar icons too.

Sounds like you should definitely try this ROM. I always implemented the further debloat tweak, but I also debloated some things that this ROM doesn't such as the boot and shutdown animation, etc, by flashing my debloat zip. His debloating has the advantage that you can easily bring the stuff back that's debloated by the tweak.

Good luck! You're welcome!
[Verizon LG G3] mroneeyedboh:
Anyone have a flashlight app that works.with this app/phone. I'd like to have an app that could have the torch I'm the power menu

Thanks
[Verizon LG G3] roirraW "edor" ehT:
I haven't fooled with flashlight apps in a long while, but I used to use Tesla Software's Notification Toggle, but that puts it in the notifications of course.

I'm on Marshmallow right now but assuming that this same option was available on Lollipop, G3TweakBox Xposed module apparently has the option, although I haven't tested it.

Edit: screenshot attached.
[Verizon LG G3] b00ster23:
How's it going there [MENTION=581991]roi[/MENTION]rraW"edor"ehT [MENTION=2941286]xdabbeb[/MENTION] ? ;) At one point in the op posting your were going try to work on finding a way for the 47A modem (VS985) to work. Know there were some problems with the bump exploit from 12b and the 47a sbl1 bootloader, but was curious if you had any progress. Understand that the 35B works fine for now on custom VZW stock roms, but was thinking more on the line of some of future and possible international roms. I'm thinking that the G3 is one of the last of it's kind for LG (and us,) and the flexibility from the current exploit. I like this little phone and hoping to use the modem for future variations, and afraid the support and attention just isn't with this guy any more. Hopefully, get that last piece so some of us can hang on... :) Appreciate EVERYTHING!

Best Regards,

b00ster23
[Verizon LG G3] roirraW "edor" ehT:
Hi! I really don't have anything to do with trying to get the 47A modem/sbl1 working with the 12B aboot, other than some very minor testing of what [MENTION=2941286]xdabbeb[/MENTION] had me try (just flashing what he gave me and seeing what happened, and unbricking myself when necessary). I think he did everything he could reasonably do to try to get it working. I haven't heard of any other attempts by anyone since that testing months ago. My impression is that there's nothing much anyone can do about it.
[Verizon LG G3] b00ster23:
Appreciate the response, and not trying to get too far off topic, but the jest of what needs to happen would be another exploit, right? That being the case, the topic probably dead in the water.
[Verizon LG G3] roirraW "edor" ehT:
No problem! I'm sure having an exploit on a more recent bootloader wouldn't hurt, but I'm not knowledgeable enough to say what alternative routes might lead to success. I think maybe [MENTION=2941286]xdabbeb[/MENTION] either found or suspected that some "key" had changed, but I don't remember the details off the top of my head and it's too difficult trying to perform an effective search in Hangouts since it doesn't display old messages until you scroll back, and there's no special search functionality.
[Verizon LG G3] tekknyne:
big thanks

Yo just wanted to post and say big thanks for this rom. I installed this +35b firmware and awesome enough, it fixed my slimport output in addition to being an awesome 6.0 rom. I used to use a previous rom and my HDMI/slimport output would blink constantly. I thought it was a hardware problem, but NOPE!
[Verizon LG G3] roirraW "edor" ehT:
Hi! Yep, this is an awesome ROM. This ROM is 5.1.1 though, unless you confused this thread with [MENTION=2941286]xdabbeb[/MENTION] 's stock 47A firmware thread.
[Verizon LG G3] OnedeeTentee:
Bluetooth reconnection issues, slow messaging, voice-to-text & keyboard

I'm having BT reconnection issues. My car auto-reconnects but 2 headsets do not. I must go into Settings->BT and manually reconnect each device. A real PITA.

I also experienced it having a mind of its own when adding a BT headset as a trusted device. It was in my pocket and the next thing I knew, it had opened an app (RedFin) from the 3rd screen, somehow found an agents phone number and started to dial it. Also while being a trusted device, it replied to a VZW account text message with the word 'Jumbo'. I never use that word.

I welcome any suggestions that would fix the BT issue. I've tried the typical reboot, remove/readd, remove/reboot/readd, remove/turn off BT/reboot/turn on BT/readd, etc.

----

Messaging: Messagin is slooow to send and for text or emojis to appear after hitting send.

----

voice-to-text & keyboard: I use TouchPal keyboard. After tapping the microphone and using V2T, if I tap in the text field to edit before Enter, the keyboard does not reappear; Google's voice services stays in front. I did not have this issue on the VZW Note3/N900V
[Verizon LG G3] roirraW "edor" ehT:
Have you verified if the same problems occur on stock unrooted 35B, and also on stock undebloated but rooted 35B?
[Verizon LG G3] OnedeeTentee:
I'm on 47A

I'm on 47A, and no/no, as I don't have access to those, and did not test that on this device prior to rooting.

Think about this: Why does an older BT device (2008 Toyota OEM NAV BT) auto-connect or reconnect, when newer headsets don't?

-Plantronics Voyager Legend (Must be turned off and back on for it to re-connect)

-Jabra GO 6470 (Must be manually reconnected from LCD screen)

Again, the N900V did not have this issue. I could walk out of range with either the phone or the BT headset and it would reconnect automagically when I came back within range. If I was wearing the Plantronics and started my car, the car BT took over. When I shut off the car, the Plantronics took back over.
[Verizon LG G3] roirraW "edor" ehT:
There's probably a better thread to discuss this in since this problem isn't specific to this ROM, and you're not discussing having the problem while on this ROM since you're on 47A. You know what I mean? :) I'd search the Q&A thread for "Bluetooth" and see if there's a thread there, or create a new thread there if necessary.

You can flash the 47A KDZ to get stock unrooted 47A and see if the problem happens there. If it does (and I suspect it would), then it doesn't have anything to do with any custom ROM, as it's an LG, Verizon or Android issue. You can use the built-in LG Backup to back everything up to your MicroSD card, move everything from internal storage to the MicroSD card, and flash the 47A KDZ with the CSE option that will wipe all. It's always recommended to test under as clean an install as possible. Then proceed directly to testing the bluetooth issues. You can downgrade to re-root by flashing the 10B TOT using the .DLL extracted from the 35B KDZ, then re-root with the Stump app and put TWRP on with TWRP Manager from the Play Store, then re-flash the 35B Bootstack and 47A ROM if you wish.
[Verizon LG G3] OnedeeTentee:
If the issue is indicative of the LG G3 hardware as you infer, then the phone is not worth my time to pursue. I've seen quite a few writings from Internet searches that point to a possible problem with MM and the LGG3. I was looking to go to a slightly smaller form factor from the N900V.

-------------------

I do thank you and everyone that made rooting this device possible but I don't have the time to spend on this (managing 3 parents healthcare and as many households) and it will probably take me the course of a month or so to find the time to move off it. I'm open to recos on an Android VZW phone with the same form factor that's rootable.
[Verizon LG G3] mroneeyedboh:
Is there a recommended kernel for this rom?
[Verizon LG G3] roirraW "edor" ehT:
The one that comes with it is modified from stock courtesy of [MENTION=2941286]xdabbeb[/MENTION] and is what I use when on I'm on this ROM.
[Verizon LG G3] ssomaa:
slow wifi tether happening

The first of all, thank you very much for everything.

I had a little problem using wifi tether.

After I upgrade to this from 5.0.1 , I felt my wifi tethering got very slow.

Even bar shows 4 bars.

I did exactly follow steps to install.

Anybody had similar experience ??

How to fix ??

Thank you
[Verizon LG G3] markfm:
I've noticed hotspot fix working kind of slow too. I'm using an alternate tether app much of the time now.
[Verizon LG G3] mroneeyedboh:
Warrior, what I've noticed is that if I'm doing too much, sometimes the app will close. Like the phone will freeze and then the app will end up closing and I'll be reverted to the main screen
[Verizon LG G3] roirraW "edor" ehT:
I don't remember having that experience when I was on this. You can always try the completely stock (but bump'd) 35B kernel although I doubt it'll make a difference. You might be able to find it in [MENTION=4132606]bweN diorD[/MENTION] 's stickied thread in General, but only use it if it specifies that the one there is bump'd. Or you can extract it from the JasmineROM 9.0 zip, and when you go to flash in TWRP, switch it to flashing in Img mode instead of Zip mode.

If that doesn't fix anything, make a backup in LG Backup, wipe Cache, Dalvik/ART and Data, reflash the ROM and check to see if you can reproduce the problem while completely stock.

If you can't, then the problem was something you had installed. If you still have the problem, I'd move everything you want to keep from internal storage too external including the LG Backup, flash the 10B TOT and start over fresh rooting and putting TWRP on and flashing the ROM.

During any of all these steps, I'd consider keeping the MicroSD card ejected because it may sound weird but sometimes a card has caused problems.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome, let us know how it works out. If you didn't know since I didn't mention, the kernel is the "boot.img" - or "boot.bin", but has to be named with .img at the end to flash in TWRP.
[Verizon LG G3] mroneeyedboh:
Thumbs up
[Verizon LG G3] danbest82:
I highly doubt it is the ROM but I've been having issues with titanium backup closing while running a scheduled backup and sometimes on a manual run. Checking the logcat, I found it happens while doing things with the mediascanner. I've looked in the init.d file and build.prop to see if the scanner is disabled somewhere but can't find anything. I've looked into titanium backups trouble shooting area also. No luck. I figured I'd just throw it out there and see if anyone else had this problem. Thanks.
[Verizon LG G3] roirraW "edor" ehT:
I can't advise in that situation as I don't use Titanium Backup on stock ROMs on this device. I just wanted to throw it out there since at least it used to be some people didn't know it was an available option to use the built in LG Backup under Settings / Backup & reset / LG Backup.

It works crazy fast. It can't backup everything Titanium Backup does like Bluetooth or have as many options but for user apps, user data and limited system data, it can't be beat in my opinion.

It does have a few quirks. When you do a backup it always changes my default keyboard to the stock LG one from SwiftKey, and I believe it also holds some apps that are running in the background and maybe even kills them until you run them manually again even when you reboot (for at least some apps that you have run in the background all the time).

They're the same apps that no matter whether you use LG Backup or Titanium Backup to restore, they won't run automatically until you run them manually once.

The second quirk is that it requires the battery to be at 30% or higher to use it, but the phone charges so fast it hasn't been too big a deal.

The third quirk is that when you're doing a restore job, you can't shut off the screen and you have to manually tell it to reboot when it's done, so you might want to lower your brightness before doing large restores.

Luckily it's so fast compared to TB that it doesn't matter too much.

If you've enabled the optional additional debloat switch on this ROM, you might have to disable it to get LG Backup back temporarily.
[Verizon LG G3] danbest82:
Thank you for letting me know. I knew it was there just never used it. It sounds like a good backup option to TiBu. I usually don't notice the length of time TiBu takes since it's scheduled at night.
[Verizon LG G3] roirraW "edor" ehT:
Sure, you're welcome. I might as well ask the obvious - I assume that you have separate mountspace option disabled in SuperSU? Personally, I find that having it enabled is fine to TB for doing the tiny tasks I've done occasionally like restoring Bluetooth, freezing a particular app and even small amounts of uncompressed app back-ups, but those app back-ups are in order to easily obtain an apk for an app that I like to keep handy for fresh installations, so I haven't done any restores with the mountspace option enabled, at least not in a while.

I wouldn't expect it to exhibit the behavior you're having no matter what though. Before I knew about LG Backup, I remember at least long overnight restore sessions sometimes got hung up on a particular file, and that was with separate mountspace disabled. Restoring the particular app by itself through TB worked fine, and TB never quit, it just stopped making progress and required a phone reboot in order to really start trying to use TB again.

If I move to a non-LG device when my contract is up in six months, LG Backup will definitely be something I'll miss. I wonder if any other OEMs have anything similar these days?
[Verizon LG G3] danbest82:
The separate mountspace option is enabled in SuperSU. I tried a full backup from my schedule with catlog running and of course everything went smoothly. Should I try disabling the separate mountspace option? You're saying TiBu might get stuck backing up a file though(which I've seen in the past). Sorry this is off topic here.
[Verizon LG G3] roirraW "edor" ehT:
The first time you run a fresh install of TB and you have left that default option of SuperSU enabled, TB warns you to disable it or it can interfere, so it's worth a shot. Like I said, I don't think I've had your symptoms when I used TB in my limited fashion with that enabled, but you never know until you try.

It normally keeps popping up that warning every time you launch TB unless you hit the checkbox to not show the warning again.

I've had the problem with it stopping making progress restoring apps with that option disabled, so I don't think it'll affect that problem. I think I've had that problem for years.
[Verizon LG G3] emplox:
Hey, I dropped my nexus 6p in the lake...and am back on a G3 for the time being. i'm on an old Tesla build from 9/21/2015 which is Android 5.1.1. Is there anything in particular i need to do before upgrading to 6.0 based ROMS? Also the link for the 35B bootstack wasn't working for me. Is that link dead?
[Verizon LG G3] roirraW "edor" ehT:
I answered you three hours ago in the other thread you created...no need to ask in more than one place - besides this thread has nothing to do with 6.0, Tesla or non-stock-based ROMs.

The Bootstack download question, of course, is appropriate for this thread. ? The 35B Bootstack just downloaded fine for me. Try a different browser or a download manager? Try on a PC and transfer over?
[Verizon LG G3] maximusmullivan:
Just a heads up for folks running this ROM. I attempted to flash the new 2.76 supersu zip in recovery. I am now receiving the secure boot error with flashing blue and red lights. So just a PSA to any others.

Edit: TOT'd back to 10B. Rooted with stump and then to 47A. All is well
[Verizon LG G3] roirraW "edor" ehT:
Thanks, good to know. I'm not on this ROM - I'm on his 47A but for what it's worth, updating SuperSU through the Play Store, opening SuperSU (which prompts to update binaries), and then choosing to update binaries and reboot worked just fine for me - might be worth a chance on this ROM but as always, TWRP backup recommended and kept in a safe place (MicroSD card) just in case.
[Verizon LG G3] maximusmullivan:
I should've just updated supersu through the play store
[Verizon LG G3] postal302:
I did the same a few weeks ago. Simply dirty flashing 47A then rerunning the debloat scripts fixed it for me. I did have to do a lot of restoring after that, but it saved some time and trouble.
[Verizon LG G3] cj360:
Because the latest supersu modifies the bootimage for root. So just remember to re-bump it:

MR_Boot.zip - all credits to [MENTION=3792100]dadi11 [/MENTION]
[Verizon LG G3] ST Dog:
So is it safe to update tbe binary with SuperSU or not?

Is It safe to install the newest SuperSU from the PlayStore?
[Verizon LG G3] roirraW "edor" ehT:
Probably but as always, have a TWRP backup handy (and on your external storage in case you have to wipe internal/flash a TOT or a KDZ in a way that would wipe internal). I updated SuperSU from the Play Store on the stock rooted 47A firmware a week or longer ago without a problem and then updated binaries after using the app.
[Verizon LG G3] freshjewbagel:
Lower stock brightness

Anybody try out lowering stock minimum screen brightness? Maybe with something like horsetastic's mod?

From what I can tell the lowest stock is 50 (percent I think, getting this value from 'Thermal Sensor Info' in hidden menu after flashing the att apk dump since VZW chose not to include hidden menu)
[Verizon LG G3] roirraW "edor" ehT:
I haven't done so in a while and I never tried (or knew about) that mod, but I used to use ScreenDim Full with success, trial version here ScreenDim Trial. I don't recall what particular values I selected or was able to select - only that I could take it extremely low so that you would only be able to see the screen at all in a very dark room, and barely then, although I also don't recall if that was on 35B or before.

As always, especially when dealing with direct mods such as the link you gave, do a complete backup and make sure everything's saved on your MicroSD card just in case.
[Verizon LG G3] Bill720:
Tethering/Hotspot question

How is the support for USB/WiFi tethering on this Rom lately?
[Verizon LG G3] roirraW "edor" ehT:
I don't have to do anything special for WIFI tethering since I don't have unlimited data any more, but as far as I've read in this thread (use the search box at the top right, immediately above the top post of the page for "hotspot" or "tether") for those with unlimited data, [MENTION=2941286]xdabbeb[/MENTION] 's hotspot mod either in this section or Original Development works fine at least for WIFI tethering although again from what I've read that only works if you're using a Verizon SIM - I have no idea about USB tethering.
[Verizon LG G3] Bill720:
Not quite unlimited...

I wouldn't actually be using it with unlimited data; just the 5GB that come with the StraightTalk $45 plan. Would that work without any extra "help"? I know that most stock Roms don't have tethering working quite right without some kind of tweak, so this was why I wanted to know if there's any kind of special hoops that have to be jumped through to restore the functionality here.
[Verizon LG G3] roirraW "edor" ehT:
The only feedback that I've noticed concerning using tethering with a non-Verizon SIM was that it doesn't work, but I don't recall if that was only for those who flashed the hotspot mod, or those who didn't flash the mod, or both. Try it without the mod, if it doesn't work make a TWRP backup, save to your external MicroSD card just in case, then try with the mod. Unless someone who's on Straight Talk chimes in.
[Verizon LG G3] Sumaech:
How do I make everything bigger? Everything is to small... Especially nav bar.

Thanks
[Verizon LG G3] roirraW "edor" ehT:
There are apps in the Play Store for changing the DPI back to stock or any reasonable value. I think 560 DPI is stock. Not positive if that affects the nav bar.
[Verizon LG G3] Sumaech:
After messing around with the rom, I love it. Even the size. But the only problem is the nav bar size... it is just too small. I messed with dpi earlier and it messed everything up, and I had to factory reset to fix it.

---------- Post added at 04:49 PM ---------- Previous post was at 04:30 PM ----------

So this will make the nav bar ONLY bigger right?
[Verizon LG G3] roirraW "edor" ehT:
Yep, you can only safely change the DPI to certain values or range of values. I don't know them off the top of my head. If I recall correctly, changing the size of the navbar requires decompiling and recompiling a file. I don't mess with that often enough to be able to advise and haven't messed with that at all on the VS985 or other LG devices. I'm very sure if you do a search in this thread, or maybe in the Themes, General and Q&A section, you'll find some search hits related navbar that might help guide you. I see you found what you probably need.

Always do a TWRP backup before messing around too much with system stuff.
[Verizon LG G3] Sumaech:
Sadly the link is down for the nav bar resize zip. :(
[Verizon LG G3] harry_seaward:
If you make the DPI below 540 (actually 534 I believe) then system apps won't open. But you can manually change the DPI for those specific apps and they'll be fine. So you can set the system DPI to whatever you want as long you change the DPI for EVERY system app (or at least the ones you want to open.)
[Verizon LG G3] maximusmullivan:
Correct me if I'm wrong but I didn't think you could modify the softkeys on the G3, like you would with say a Nexus device.