Develop Bugs

Apparently Big Red knows when you're rooted.

Talking to Verizon support today trying to figure out why Advanced Calling wasn't working, and they straight up said that it appeared that I was rooted. I feigned ignorance, but I thought it was very odd that they knew this.
Sent from my VS986 using Tapatalk

The My Verizon Mobile is the one that tells them. If you deny it root when it asks, it knows you have root. If you didn't have root I think there would be no reply to it's asking for root.

Ah, is that why my advanced calling isn't working? Annoying.

I need to call them for my Advanced Calling as well (as it's complete horse s**t that I need to enable that so my phone doesn't drop from 4G to 1X) but I've never been prompted by My Verizon about root access...

There's a system property you can find with "getprop" called "vzw.os.rooted". I tried changing it in build.prop, but it didn't work. There's also a partition called persistent with a file /persistent/rct.cfg detailing some not allowed system behavior. There are things that detect root since it's pretty noticable and readable to everything at /system/xbin/su. An app that communicates to the internet could easily transmit that information. This is one of the many reasons I have a firewall (AFWall+). I installed it pretty soon after I got root, but one of the many vzw bloatware apps probably got the info out. Guess what, I don't give a s***.

FWIW, I had a lot of difficulty trying to activate Advanced Calling on software 610B. I worked with Tech Support for a week, no luck.
I finally updated to 611A as a last resort, and it suddenly worked. So if you're having trouble getting AC enabled, and you're on 610B, you may need to update your software version.

RedOCtobyr said:
FWIW, I had a lot of difficulty trying to activate Advanced Calling on software 610B. I worked with Tech Support for a week, no luck.
I finally updated to 611A as a last resort, and it suddenly worked. So if you're having trouble getting AC enabled, and you're on 610B, you may need to update your software version.
Click to expand...
Click to collapse
Isn't 11A the upgraded version of 11B? I know it sounds backwards, but we had to KDZ that to root phone.

Before I rooted my advanced calling worked. After root when I make calls it drops to 1x. Don't really care as I don't browse the internet on my phone while on a call (99% of the time).
Still, it's pretty dumb of Verizon. Then again they do more than their fair share of dumb corporate related ****.

Mine works and I'm rooted with no firewall or protection to block them knowing.

Dennisg34 said:
Isn't 11A the upgraded version of 11B? I know it sounds backwards, but we had to KDZ that to root phone.
Click to expand...
Click to collapse
AFAIK, there is no 11B.
Just 610B (original, what shipped on my G4), and 611A (OTA update, which I needed to use in order to properly activate AC).
I am not rooted.

Advanced Calling also works fine for me on rooted 11A. However, I recently disabled it because ACR will not record calls with it turned on.

johno86 said:
Before I rooted my advanced calling worked. After root when I make calls it drops to 1x. Don't really care as I don't browse the internet on my phone while on a call (99% of the time).
Still, it's pretty dumb of Verizon. Then again they do more than their fair share of dumb corporate related ****.
Click to expand...
Click to collapse
This is the same problem I'm having. I had to KDZ to 11A when I rooted, and I haven't been able to get it to work since.
Sent from my VS986 using Tapatalk

For those of us who haven't fully been following the root discussions, what does that mean, that you KDZ'd to 11A? You had 610B, you used KDZ to put on a 611A image (not taking the OTA to 611A, so you kept the 610B bootloader), then rooted that?
Did AC work before root, presumably on 610B?
After what I went through to finally get AC working, I would really hate for root to break that

RedOCtobyr said:
For those of us who haven't fully been following the root discussions, what does that mean, that you KDZ'd to 11A? You had 610B, you used KDZ to put on a 611A image (not taking the OTA to 611A, so you kept the 610B bootloader), then rooted that?
Did AC work before root, presumably on 610B?
After what I went through to finally get AC working, I would really hate for root to break that
Click to expand...
Click to collapse
AC worked perfectly for me on 10B, and after I rooted (KDZing to 11A) it will no longer activate. I tried toubleshooting with VZW, and none of the things they did on their end fixed it. The only suggestion they had was factory resetting, but I haven't tried that yet.

I'm sorry to hear that.
There seems to be some mysterious magic to Verizon's Advanced Calling. In the span of a week, after a bunch of work on their end, Verizon was unable to fix mine, they resorted to telling me to exchange the phone. I had already done a factory reset, at their suggestion, which did not change anything. Then after the OTA to 611A, it suddenly worked, and it seemed this was a surprise to them, as well as to me.
Having issues with AC after rooting would seem worse, they could potentially blame any issues on root.
Why problems with AC can't be figured out, and then fixed, is kind of disconcerting. I guess maybe there's a reason the phone calls it Advanced Calling 1.0.

AC was working for me also and then it stopped. I was already on 11a before rooting. If you have the verizon app called name and id on your phone ac will not work. Once I froze that app in tibu it went back to working. I'm not for certain but I don't think that app was on my phone before root so it may have been included in the rooted img file.

murphyjasonc said:
AC was working for me also and then it stopped. I was already on 11a before rooting. If you have the verizon app called name and id on your phone ac will not work. Once I froze that app in tibu it went back to working. I'm not for certain but I don't think that app was on my phone before root so it may have been included in the rooted img file.
Click to expand...
Click to collapse
So you froze Caller Name ID? The icon is a phone with ID in the upper right?

sefirosu0522 said:
So you froze Caller Name ID? The icon is a phone with ID in the upper right?
Click to expand...
Click to collapse
Yeah that's the one. Once I froze it ac started working again. There is a thread on Verizon's website that says that app is not compatible with ac also.

murphyjasonc said:
Yeah that's the one. Once I froze it ac started working again. There is a thread on Verizon's website that says that app is not compatible with ac also.
Click to expand...
Click to collapse
What else do you have frozen? I have that frozen too, and it's still the same.

I'm not rooted (maybe that's the difference), but I noticed today that I have Caller Name ID on my phone. And last time I tried it, AC was working. Just FWIW.

LG G3 D851 T-Mobile Marshmallow update ruined my phone!!

3rd worst mistake of my life... (don't ask)
LG G3 D851 was working just fine until I "upgraded" to 6.0 Marshmallow.
After Android 6.0 update OTA via T-Mobile, phone calls were terminating quickly and then got to the point where they didn't work at all. I used Google Voice almost exclusively, but problems were occurring for T-Mobile direct calls, too.
The phone call issue seemed to grow, and the update then ruined my battery from boot looping.
At my wits end, I did a hard reset (btw, is there any way to save app preferences and restore them) and it seemed to work ok on AC power ONLY. If I unplugged it, it went right back into boot loop, even though my battery was showing 100%. I know it was my battery, because I tried a friend's battery and it worked ok.
So I slowly installed more apps, and finally got a new battery, so I could use it without being plugged into AC. Things seemed ok for a couple days, then today the same phone call problems and freezing were back again!
Occurred after updating eBay app, but have no idea if that was the culprit, because I have all apps set to update automatically on WiFi (probably not a smart idea).
Did the Google Voice trick (remove app from phone, then go to PC and remove real number from GV list on PC, then go back to phone, reinstall GV app and have GV find my real T-Mobile number automatically and add the number from the handset), but 'unable to complete phone call problem' is back on GV or the T-Mobile network.
Super frustrated and angry. Nice effing "update!" Everything is stock, not even rooted...
Any known app conflicts on D851 running Marshmallow?? Ideas?
I'm thinking another hard reset, but would love to save all my app preferences to restore them (doesn't seem to work on LG PC Suite, which is what I used for backup last time).
TIA.

healthylaff said:
3rd worst mistake of my life... (don't ask)
LG G3 D851 was working just fine until I "upgraded" to 6.0 Marshmallow.
After Android 6.0 update OTA via T-Mobile, phone calls were terminating quickly and then got to the point where they didn't work at all. I used Google Voice almost exclusively, but problems were occurring for T-Mobile direct calls, too.
The phone call issue seemed to grow, and the update then ruined my battery from boot looping.
At my wits end, I did a hard reset (btw, is there any way to save app preferences and restore them) and it seemed to work ok on AC power ONLY. If I unplugged it, it went right back into boot loop, even though my battery was showing 100%. I know it was my battery, because I tried a friend's battery and it worked ok.
So I slowly installed more apps, and finally got a new battery, so I could use it without being plugged into AC. Things seemed ok for a couple days, then today the same phone call problems and freezing were back again!
Occurred after updating eBay app, but have no idea if that was the culprit, because I have all apps set to update automatically on WiFi (probably not a smart idea).
Did the Google Voice trick (remove app from phone, then go to PC and remove real number from GV list on PC, then go back to phone, reinstall GV app and have GV find my real T-Mobile number automatically and add the number from the handset), but 'unable to complete phone call problem' is back on GV or the T-Mobile network.
Super frustrated and angry. Nice effing "update!" Everything is stock, not even rooted...
Any known app conflicts on D851 running Marshmallow?? Ideas?
I'm thinking another hard reset, but would love to save all my app preferences to restore them (doesn't seem to work on LG PC Suite, which is what I used for backup last time).
TIA.
Click to expand...
Click to collapse
Use LGUP and down grade to LP.
Sent from my LG-D850 using XDA Free mobile app

smilesintears77 said:
Use LGUP and down grade to LP.
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Can you point out any link for the downgrade tutorial please?

@healthylaff, probably don't want to hear this but...
If you were previously rooted, the #1 rule is, was, and always will be Never Accept OTAs! For any number of reasons, some of which you've experienced.
You can go back to LP or start off again with MM since it looks like you'll be starting from scratch.
Main irk I have with MM is the change in storage paths. That breaks or hampers a few things. Enough that I can't/won't use MM as my primary environment. Still continue to test/run them though. Anyway...
The 30D stock ROM has been available for some time now. Installable via different methods. Check it out.
http://forum.xda-developers.com/showthread.php?t=3367371
[STOCK] D851 30D KDZ + Flashable ZIPs + All IMGs (Marshmallow!!)
LG G3 D851, XOSP ROM, Tapatalk 4.9.5

@marcdw I previously flashed stock MM, but do any of the flashable ZIPs in that post include stock recovery? I need to send my phone warranty replacement

"My Verizon Services" process, wtf where did that come from?

Hey all, apologies if this has been addressed.
The background, I was starting to get some slow down, laggy performance from my phone, so I went under developer options and went to see what processes were currently being run and what cached processes were saved. And then I noticed a process named, "My Verizon Services". WTF.
The last I remember, I setup my phone via WiFi without my sim card in, so that bloatware from Verizon didn't get installed. Am rooted via magisk/twrp and have manually installed subsequent updates.
Where did this process come from? And how can I make sure that after I do my full wipe, it won't sneak its way back into my phone? Or is this a mandatory process force installed to work on a Verizon network?
2XL, 8.1 January (non-verizon), rooted, magisk 15.3

rknee said:
Hey all, apologies if this has been addressed.
The background, I was starting to get some slow down, laggy performance from my phone, so I went under developer options and went to see what processes were currently being run and what cached processes were saved. And then I noticed a process named, "My Verizon Services". WTF.
The last I remember, I setup my phone via WiFi without my sim card in, so that bloatware from Verizon didn't get installed. Am rooted via magisk/twrp and have manually installed subsequent updates.
Where did this process come from? And how can I make sure that after I do my full wipe, it won't sneak its way back into my phone? Or is this a mandatory process force installed to work on a Verizon network?
2XL, 8.1 January (non-verizon), rooted, magisk 15.3
Click to expand...
Click to collapse
You sure that the My Verizon app isn't installed? I set up mine without the sim card in the beginning and as soon i as popped in the sim card, it installed those 3 Verizon apps. I just uninstalled them so it wasn't a big deal.

Yeah not installed, and searched throughout the phone with two different file explorers to root out verizon (vzw) apps, folders, etc. tried deleting them all but the process still shows up.
I'm curious if you still have that process running even after you deleted the apps.
Check it out for me and let me know.
pipnmike said:
You sure that the My Verizon app isn't installed? I set up mine without the sim card in the beginning and as soon i as popped in the sim card, it installed those 3 Verizon apps. I just uninstalled them so it wasn't a big deal.
Click to expand...
Click to collapse

If you put a VZ SIM in the phone it pulls My Verizon. If you start the app...even if you don't fully sign in..that service shows up. It stays there after you uninstall the app.
Just tested and confirmed on my Google phone.

Dang.... need to figure out how to block that from getting installed. Or how to fully rid it from the phone after.
Or does it only show up if you start the app? So if I don't start it up, I'm good?
I'll report back here in just a bit
TonikJDK said:
If you put a VZ SIM in the phone it pulls My Verizon. If you start the app...even if you don't fully sign in..that service shows up. It stays there after you uninstall the app.
Just tested and confirmed on my Google phone.
Click to expand...
Click to collapse

rknee said:
Dang.... need to figure out how to block that from getting installed. Or how to fully rid it from the phone after.
Click to expand...
Click to collapse
If you uninstall it, the service shouldn't show up. Try rebooting after uninstalling and see if it goes away

rknee said:
Dang.... need to figure out how to block that from getting installed. Or how to fully rid it from the phone after.
Or does it only show up if you start the app? So if I don't start it up, I'm good?
I'll report back here in just a bit
Click to expand...
Click to collapse
Going to have to flash back to stock and uninstall it before you start it. I had never uninstalled it or started it. It was not in my running services when I first looked. So remove it before you start it.
pipnmike said:
If you uninstall it, the service shouldn't show up. Try rebooting after uninstalling and see if it goes away
Click to expand...
Click to collapse
Nope, it stays there even after reboot. It pops back up for a second running then moves to the cached in background section.
---------- Post added at 08:08 PM ---------- Previous post was at 08:00 PM ----------
Bummer, just ran the flash all minus the -w and it's still there. So it's part of the User partition. Gonna take a full wipe I think. I am not worried about it, just enjoying figuring out the puzzle.

I'm right there with you. I don't understand why that process persists.
I've got slow wifi at my place, so it make take a bit for me to report back in. Currently installing all apps I had on my phone before, root, and then pop my sim card back in.
Goal- basically stop verizon apps download while in process.
Not sure what that process is/was doing. Or what information it is sending. But I really don't see why it needs to be taking up memory, or why it needs to be sending any data.
Thanks for looking into it with me.
TonikJDK said:
Going to have to flash back to stock and uninstall it before you start it. I had never uninstalled it or started it. It was not in my running services when I first looked. So remove it before you start it.
Nope, it stays there even after reboot. It possible back up for a second running then moves to the cached in background section.
Click to expand...
Click to collapse

I think it must be connected to the Sim card.
Factory reset, root, no verizon apps installed or downloaded
And it's still showing up in the running/cached processes.
It was not there when the Sim card was not in.
I'm curious if Sprint or T-Mobile folks have a similar process.

Got it killed.
Install All In One Toolbox from the play store, requires root for what we are doing. Fire it up and you can disable services from startup. My Verizon Services was there, disabled it and rebooted and it is gone. Then I uninstalled All In One and rebooted. Still gone.
I love the smell of burnt Verizon in the morning.
Be interesting to see if any side effects, like lost voicemail notifications.

rknee said:
Hey all, apologies if this has been addressed.
The background, I was starting to get some slow down, laggy performance from my phone, so I went under developer options and went to see what processes were currently being run and what cached processes were saved. And then I noticed a process named, "My Verizon Services". WTF.
The last I remember, I setup my phone via WiFi without my sim card in, so that bloatware from Verizon didn't get installed. Am rooted via magisk/twrp and have manually installed subsequent updates.
Where did this process come from? And how can I make sure that after I do my full wipe, it won't sneak its way back into my phone? Or is this a mandatory process force installed to work on a Verizon network?
2XL, 8.1 January (non-verizon), rooted, magisk 15.3
Click to expand...
Click to collapse
Are you using the Verizon app by chance?? I have the same setup as you, and I use the app to check my data usage periodically. If your on wifi, you won't see it running under developer options. However, if you use it on mobile data, and deny the location prompt when you open the app, it'll stay running in the background searching. When your back on wifi, it'll still run, so I just go to developer options and shut it down.

Nice one.... worked like a charm. Thanks
TonikJDK said:
Got it killed.
Install All In One Toolbox from the play store, requires root for what we are doing. Fire it up and you can disable services from startup. My Verizon Services was there, disabled it and rebooted and it is gone. Then I uninstalled All In One and rebooted. Still gone.
I love the smell of burnt Verizon in the morning.
Be interesting to see if any side effects, like lost voicemail notifications.
Click to expand...
Click to collapse

TonikJDK said:
Got it killed.
Install All In One Toolbox from the play store, requires root for what we are doing. Fire it up and you can disable services from startup. My Verizon Services was there, disabled it and rebooted and it is gone. Then I uninstalled All In One and rebooted. Still gone.
I love the smell of burnt Verizon in the morning.
Be interesting to see if any side effects, like lost voicemail notifications.
Click to expand...
Click to collapse
Thanks this app was bugging me. Kept reinstalling itself

TonikJDK said:
If you put a VZ SIM in the phone it pulls My Verizon. If you start the app...even if you don't fully sign in..that service shows up. It stays there after you uninstall the app.
Just tested and confirmed on my Google phone.
Click to expand...
Click to collapse
Is the service related to the My Verizon app or is it due to network connectivity, specifically LTE Advanced Calling and/or Wifi calling? And you said you disabled and uninstalled it with a root app, which I can't use. But have you noticed anything untoward after disabling it? I click on it in the Cached Services tab and it says an old app cached but available if needed. Doesn't seem like it's doing anything weird. Phone is working fine and no crazy data or battery drain. (I have a Pixel 2 and not the XL version)

Haven't noticed anything detrimental. Though I did do a full wipe before doing all this because I was having some performance lag issues, like home screen swipes not being smooth, increased time while switching between apps.
I would be curious to know what it's actually doing since I never had any Verizon related apps loaded onto the phone.
If you watch the running processes screen during load up you'll see it run for a few seconds and then move over into the cached processes.
I don't know enough about debugging, but it would be interesting to see what it's doing and if it's sending or receiving any information.
But...I no longer have it running so I'm currently unable to do so.
bobby janow said:
Is the service related to the My Verizon app or is it due to network connectivity, specifically LTE Advanced Calling and/or Wifi calling? And you said you disabled and uninstalled it with a root app, which I can't use. But have you noticed anything untoward after disabling it? I click on it in the Cached Services tab and it says an old app cached but available if needed. Doesn't seem like it's doing anything weird. Phone is working fine and no crazy data or battery drain. (I have a Pixel 2 and not the XL version)
Click to expand...
Click to collapse

I have a Pixel 2 XL simless on project fi and this app showed up on a security scan with Clean Master so I'd be curious to know how it got on my phone

Funny story....

https://www.apkmirror.com/apk/googl...rizon-services-1-0-89-2-android-apk-download/
It's actually a Google app and not Verizon bloat. That would explain how it got onto the non-Verizon variant of the phone. Still not 100% sure what it exactly does though, but according to this Verizon rep it is a dependency service for other apps which I'm assuming are from Verizon.
https://community.verizonwireless.com/thread/942253

giants8058 said:
https://www.apkmirror.com/apk/googl...rizon-services-1-0-89-2-android-apk-download/
It's actually a Google app and not Verizon bloat. That would explain how it got onto the non-Verizon variant of the phone. Still not 100% sure what it exactly does though, but according to this Verizon rep it is a dependency service for other apps which I'm assuming are from Verizon.
https://community.verizonwireless.com/thread/942253
Click to expand...
Click to collapse
It's needed for VZ wifi calling. I froze it, wifi calling instantly stopped. Unfroze instantly worked again.

TonikJDK said:
It's needed for VZ wifi calling. I froze it, wifi calling instantly stopped. Unfroze instantly worked again.
Click to expand...
Click to collapse
Wonder what other Verizon services rely on it to function. Figured I'd reach out to Google via the support chat to see if they might know, but they were pretty much useless.

RCS went away?

A few days ago RCS randomly stopped working. I also got an update to Messages later in the evening but it was hours after it stopped working. I have rebooted, uninstalled updates and reinstalled, etc. No dice.
When I first launch Messages after updating to the latest version it has the popup to enable messages clicking enable goes straight to "ready to go" (or similar) and I can tap the link to Chat settings and see the options but after exiting the app and coming back Chat is gone completely and I only have SMS.
This was present before and after Q beta 3. Verizon, Pixel 3 XL.
Anyone else experiencing similar? Any ideas on how to fix?

May need to check with Verizon, since it's activated from a carrier level.
They may have disabled it with they're most recent backend update, not from Google.

Not sure what happened, or is happening, but even T-Mobile states the Pixel no longer supports it.

bobbyphoenix said:
Not sure what happened, or is happening, but even T-Mobile states the Pixel no longer supports it.
Click to expand...
Click to collapse
Did T-mobile ever support RCS? I have never seen the option to enable it on my phone, even though I've been hoping they would support it.

draiken78 said:
Did T-mobile ever support RCS? I have never seen the option to enable it on my phone, even though I've been hoping they would support it.
Click to expand...
Click to collapse
They never have, because the Pixel was not officially sold by them and had not gone through whatever hoops they have for devices to get that feature.
Prior to I/O, I was trying to figure this out but there's such a lack of knowledge that actually calling tech support got me info.
The Verge just released an article about this issue with RCS on Pixels on T-Mobile, due to the release and availability of 3A on T-Mobile.

y2k1ltd said:
May need to check with Verizon, since it's activated from a carrier level.
They may have disabled it with they're most recent backend update, not from Google.
Click to expand...
Click to collapse
I contacted VZW on Twitter and provided screenshots showing what happens. If I uninstall updates and install the latest version, the first time the app opens it says it's ready to go and I can tap to see Chat settings toggle them around, etc but it doesn't actually work and the Chat settings disappear from the advanced menu after closing the app.
They told me everything appears correct and I should contact Google. I explained this started without any changes to the Messages app but they just told me to talk to Google again so I gave up on that.
This weekend I rolled back to two releases ago (4.2.069 fairie) and got the same prompts about it being ready. Went to the convo with my fiancee and it was still SMS. BUT, I had Chat settings in Advanced, so it was at least different than before. I rebooted the phone and RCS worked. But if I updated to either of the newer versions, it breaks and I have to uninstall and go back to 4.2.069, reboot again and it works. So I guess I'll wait and see if they release another update and try that, but for now I'll stay on this version.
The more annoying part is that Q beta 3 doesn't allow you to change any notification settings for Messages, so I can't turn the damn vibration off every time I get a text.

Yea it's broken for me too. I got a random pop up that RCS wants to be enabled which it already was so I hit accept. I still can't get it to turn on. reboot, turn off, turn back on reboot and still can't get it to work. Pixel 3 xl on verizon here.

coldconfession13 said:
Yea it's broken for me too. I got a random pop up that RCS wants to be enabled which it already was so I hit accept. I still can't get it to turn on. reboot, turn off, turn back on reboot and still can't get it to work. Pixel 3 xl on verizon here.
Click to expand...
Click to collapse
That's exactly what happened to me. It randomly said enable chat features after they were on for months, and quit working after that. If you want it back you can uninstall updates and go back to 4.2.069 and it will work again. Thinking it must be something in the way Messages is talking to Verizon.

This is still broken for me

coldconfession13 said:
This is still broken for me
Click to expand...
Click to collapse
https://www.androidpolice.com/2019/...-seems-to-be-breaking-rcs-messaging-for-many/
Roll back to 4.2.069 and it will work.

I'm still shocked this hasn't been fixed yet.

[ROM][VS996] Verizon LG V30 Pie 30c Debloated Rom

Here's my LG V30 VS996 Verizon Pie 30C debloated rom.
Features:
*Most bloat removed.
*Weather Animation thanks to pittvandewitt. Enable them in Settings, Lock screen and Security, Customize Lock screen.
*DTS 3D stereo thanks to ChazzMatt
*Includes Disabled Force Encrypt and RCTD Disabler.
I made rom by extracting system.img and boot img from 30c kdz and added weather and DTS myself. Thanks to osm0sis for flashable zip format.
Prerequisites:
**Must be on VS996 Pie firmware. Go here first to flash 30C firmware.
https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-vs996-verizon-30c-t3974139
Instructions:
1) TWRP backup.
2) Can dirty flash over stock 30c.
3) Flash ROM
4) Flash Magisk for root
Download:
VS996-30C-Pie-Debloated-v1.0.zip
MD5: bc5b479c92c59d9ee0c6b22e45dcee19

Cranking out Roms since LG G2 days. Great job :good:

Do you have a debloat list you could post?

HueyT said:
Cranking out Roms since LG G2 days. Great job :good:
Click to expand...
Click to collapse
Oh yea. Actually started with the original Google Nexus One way back in the day. So tempted to pull the trigger on the new Pixel 4 XL. But $43 a month for the next two years is not something I look forward too. lol
Stuckurface said:
Do you have a debloat list you could post?
Click to expand...
Click to collapse
I don't. But only thing left is My Verizon, Voicemail, Youtube, Maps, LG Health, Google Photos, Google Music, Google Pay, Gmail, and basic apps. Got rid of all the bloat junk though like Facebook that nobody in their right might uses anymore if you value your privacy.

Your room is real smooth. Thanks for this!
I too remember you from G2

MicroMod777 said:
Oh yea. Actually started with the original Google Nexus One way back in the day. So tempted to pull the trigger on the new Pixel 4 XL. But $43 a month for the next two years is not something I look forward too. lol
I don't. But only thing left is My Verizon, Voicemail, Youtube, Maps, LG Health, Google Photos, Google Music, Google Pay, Gmail, and basic apps. Got rid of all the bloat junk though like Facebook that nobody in their right might uses anymore if you value your privacy.
Click to expand...
Click to collapse
Hi, whats the difference in between your and this rom
https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-v30-joan-vs996-verizon-30c-t3974139
your download size is bigger than his stock rom

Would there be any way to enable native tethering on this rom?

MicroMod777 said:
Oh, yea. Actually started with the original Google Nexus One way back in the day. So tempted to pull the trigger on the new Pixel 4 XL. But $43 a month for the next two years is not something I look forward too. Lol
I don't. But only thing left is My Verizon, Voicemail, YouTube, Maps, LG Health, Google Photos, Google Music, Google Pay, Gmail, and basic apps. Got rid of all the bloat junk though like Facebook that nobody in their right might uses anymore if you value your privacy.
Click to expand...
Click to collapse
Hi, I got strange issue, everything works fine, but when I'm trying to send the text it won't go , look at the picture I tried over Wi-Fi, and data. I can receive it but I couldn't and I'm running on your latest build. Any help?

zfk110 said:
Hi, I got strange issue, everything works fine, but when I'm trying to send the text it won't go , look at the picture I tried over Wi-Fi, and data. I can receive it but I couldn't and I'm running on your latest build. Any help?
Click to expand...
Click to collapse
Make a phone call, then see if texting works? I'm not joking. That's a workaround for wonky Verizon service.
On AOSP ROMS every time users reboot they have to make a phone call for texting to work. Don't know why you would need to do this on stock firmware, but give it a shot.
Also try toggling on/off airplane mode.

zfk110 said:
Hi, I got strange issue, everything works fine, but when I'm trying to send the text it won't go , look at the picture I tried over Wi-Fi, and data. I can receive it but I couldn't and I'm running on your latest build. Any help?
Click to expand...
Click to collapse
ChazzMatt said:
On AOSP ROMS every time users reboot they have to make a phone call for texting to work. Don't know why you would need to do this on stock firmware, but give it a shot.
Click to expand...
Click to collapse
In my experience, the issues on Verizon regarding texts deals only with not *receiving* texts before making/receiving a call. I've never had issues with sending texts.
Side note: Facebook messenger seems to also play a roll in this...but it doesn't look like you're using it so idk.

Stuckurface said:
In my experience, the issues on Verizon regarding texts deals only with not *receiving* texts before making/receiving a call. I've never had issues with sending texts.
Side note: Facebook Messenger seems to also play a role in this...but it doesn't look like you're using it so IDK.
Click to expand...
Click to collapse
No FB at all, turning on/off flight mode didn't do anything, neither calling someone. Still stuck with no sending text. I might try another ROM to see if I can fix it.

ChazzMatt said:
Make a phone call, then see if texting works? I'm not joking. That's a workaround for wonky Verizon service.
On AOS PROMS every time users reboot they have to make a phone call for texting to work. Don't know why you would need to do this on stock firmware, but give it a shot.
Also try toggling on/off airplane mode.
Click to expand...
Click to collapse
It didn't work, so I called the Verizon support and tech told me he has to refresh the 4g data signals servers once he does it that, it started to work, and I was able to send the text, but if I get disconnected due to connecting to Wi-Fi, restarting the phone then texting will stop again and I have to call them to refresh the server.
I'm on pie do you think going back to Oreo should have fix this issues?

I use US Mobile (Verizon MVNO). Will this ROM allow me to use tethering without having to sign in through My Verizon? Or is there some way to disable that verification step?

I used this debloated rom for a couple of days. I thought it ran very well. But, because I need the Hotspot functionality that the US99830b twrp version has, I had to go back to that rom. Thx, for it.

You might want to see if the old hack to disable the subscription check works on the VZW rom.
* Open "build.prop" in the system folder.
* Look for or add at the bottom
net.tethering.noprovisioning=true
* Reboot and see if you can enable hotspot/tether without a subscription check.
gimpy1 said:
I used this debloated rom for a couple of days. I thought it ran very well. But, because I need the Hotspot functionality that the US99830b twrp version has, I had to go back to that rom. Thx, for it.
Click to expand...
Click to collapse

cmrntnnr said:
You might want to see if the old hack to disable the subscription check works on the VZW rom.
* Open "build.prop" in the system folder.
* Look for or add at the bottom
net.tethering.noprovisioning=true
* Reboot and see if you can enable hotspot/tether without a subscription check.
Click to expand...
Click to collapse
Thanks for the tip, that worked great for me! Now I can continue to be lazy and stay on VS996 (even though I'm not on VZ directly anymore - I'm on TotalWireless).
Note of clarification - I used FX file manager and FX text edit for this, and the build.prop was located in System/system (not at the root of "system")... in case anyone couldn't find it.

I've been having a hard time getting the zip to flash?
It says the zip file is corrupt?
Is there another mirror or link?
Thanks!

kfa670 said:
I've been having a hard time getting the zip to flash?
It says the zip file is corrupt?
Is there another mirror or link?
Thanks!
Click to expand...
Click to collapse
Does the md5 match?
Listed right below the download link:
MD5: bc5b479c92c59d9ee0c6b22e45dcee19
If it matches, then it's not corrupt. There are free md5 tools to download to generate the md5 number and match against the one listed by the dev.

Long explanation guys but I'm using some old tech! Kind of a combo of Droid Turbo, Laptop, and trying to get a new V30 up and running since my little boy slobbered into the charge port of my last one (and dropped it numerous times) and finally my touch screen quit.
I tried checking the MD5 a few times on the old Droid Turbo (which I used to download the zip) but the poor bastard is so wore out that it was having issues with various apps and the size of the zip I think. Story short, I downloaded the Debloat zip from a different mirror and flashed it again and bam! Working awesome. Thanks to all for your awesome work and even more awesome help.
I have a dilemma I would like to ask everyone their opinion on but I will start a new thread. I am looking for native tether solutions for the VS996 rom on the V30 because as @ChazzMatt has pointed out, Volte is going to be needed by the end of the year and US998 won't work correct? And I absolutely need tethering, am still on grandfathered unlimited data.
ChazzMatt said:
Does the md5 match?
Listed right below the download link:
MD5: bc5b479c92c59d9ee0c6b22e45dcee19
If it matches, then it's not corrupt. There are free md5 tools to download to generate the md5 number and match against the one listed by the dev.
Click to expand...
Click to collapse