yashsingh1/xdaforums huggingface dataset:
[LG V30 Guides, News, & Discussion] jcsww:
Anytime! I have the benefit of dealing with carriers from Canada, the US, and even the UK at times. I also enjoy technology a little more than I probably should. :P My future in-laws also live in a cellular dead zone so having an understanding of which bands will eventually provide the best potential for future service there is always good to have an idea of. I also tend to expect a lot from the companies I deal with, hence the list of contacts in my phone for many carriers. Daniel has been one of the very few employees at the store level I think fits the model of what all customer service experiences should be.
[LG V30 Guides, News, & Discussion] sundoggy:
[MENTION=3116388]jcsww[/MENTION]

I think you are looking for this? someone was talking about T-mo version of it.

"The box and the phone said" I think the box won't be wrong this time.

"Looks like nobody knows what bands the phone has.

LG website says:

B1, B2, B3, B4, B5, B7, B12, B20, B38, B39, B40, B41, B46, B66, B71 (Some are listed as roaming bands. Not sure if they would work with a local sim or not or what that means)

GSM Arena says:

B1, B2, B3, B4, B5, B7, B12, B20, B28, B29, B40, B41, B66, B71

T-Mobile website says:

LTE: 1, 2, 3, 4, 5, 7, 12, 20, 28, 29, 40, 41, 66, 71 (Same as GSM Arena)

Box and phone says:

1,2,3,4,5,7,8,12,13,17,20,25,28,29,30,38,39,40,41, 46,66,71"
[LG V30 Guides, News, & Discussion] jcsww:
Yeah, and it's like that with all of the models I have researched. Definitely frustrating in the beginning to try and get accurate information. It may not matter for some, but for those of us who travel a lot, more bands offer up more compatibility across roaming partners and international networks. I have yet to see a box that lists the LTE bands supported on it as well. That could have been helpful if LG had that information right on the box.
[LG V30 Guides, News, & Discussion] sundoggy:
Do you know what's the model number for the V30+ t-mobile version?
[LG V30 Guides, News, & Discussion] jcsww:
It is still an H932. It just has more storage and comes with headphones. Other than that, there are no hardware differences. The logo on the back also says, V30+, and it comes in black.
[LG V30 Guides, News, & Discussion] ChazzMatt:
Like the Droid Turbo XT1254. Came in 32GB and 64GB storage options, but both were still the same model number.
[LG V30 Guides, News, & Discussion] chriskwarren:
So my poor LTE reception is not due to a bad SIM card. Looks like I have to send this in and Bell will exchange for a brand new one, but they are saying it will be 30 days before its processed. Bummer, brand new device and it sucks as I am travelling over the next weeks and will not have a good phone to take pics.
[LG V30 Guides, News, & Discussion] jcsww:
Wow! 30 days for an exchange is nuts! That would be enough to make me switch carriers. I did have an issue with the third party company Telus contracts out to when my Nexus 6 was having issues. My pristine Nexus 6 was to be exchanged for one that looked like it was used in a few games of floor hockey. I got rid of my T-Up for that reason and sent them back their scuffed and scratched up replacement. Telus basically wiped out my device term and told me to vet a new phone instead of taking the chance in getting another unsatisfactory replacement.
[LG V30 Guides, News, & Discussion] chriskwarren:
You seem to be more knowledgeable than I am (by multitudes lol). I have a question/opinion before I send my V30 back to Bell for 30 days (I am worried about sending it back as I have gotten many different answers on what is happening with my return, based on who I talk to...I have lots of notes).

I am sitting here now with my backup phone, the ZTE Axon (A1R model), using my Bell Mobility SIM card. I'm in Ajax, next to the 401. I'm seeing the same LTE reception on the ZTE as I did on the V30. ZTE was purchased at Canada Computers (the V30 from my carrier directly). This is giving me pause before I return the device, as maybe there is something else going on that I missed.

My colleague has the Samsung Galaxy S7 Edge (purchased from Bell as well), and he is seeing almost full signal on LTE+ sitting right here. I have used Samsung devices a lot, and I just came from a Galaxy S7.

Is there a chance that the V30 does not have the same band or LTE support as the Samsung devices do for Bell Mobility in this area? I just installed a couple of LTE apps (Rx Monitor and LTE Discovery) and I don't see the bands I have connected to like I was able to on the V30.

A colleague of mine (who is away from work until next week now) also has the V30, and the one time I compared my reception to him he had a great connection, while mine didn't. Could it be that my phone was just trying to lock on to a signal at that time?

Any opinions appreciated. I would like to avoid sending the V30 back and waiting a month if I'm just chasing an issue that the next V30 will have. I was offered a refund as well, so I could just move on to another device if the V30 has poor LTE support for Bell, but I'm unsure of how to make that determination in a hurry.
[LG V30 Guides, News, & Discussion] jcsww:
Comparing the same phone in the same location on the same carrier is always one of hte better ways to know for sure. Samsung phones should support most of the same LTE bands. Carrier aggregation though will make a difference, which is at the software level. Different phones also report signal strength differently. Something like LTE Discovery shows you the Dd strength. Those are what need to be compared when using different manufactures and models of phones.

That was something I have always found to be an annoyance with Bell. With each person you speak with, the answer is different and what the previous person told you is always wrong. It amazes me how they still have customers outside of senior citizens who only stick with Bell because they haven't tried anything else and don't want the hassle of switching. If you want a straight exchange, I would keep pressing the Executive Office until you get that. If the first person there doesn't offer you that, then ask for someone higher. Eventually, they will tell you someone will have to call you back in 24 to 48 hours. That is usually worth the wait. Best of luck with whatever you decide.

I do have to head to Oshawa today. I will try to remember to push my 6P on to Bell and take some screenshots of my signal strength as I pass through the GO station.
[LG V30 Guides, News, & Discussion] ChazzMatt:
30 days just to get a new SIM card? I walk into an AT&T store and walk out with a new one in a few minutes. Do you live way out in the boonies somewhere?
[LG V30 Guides, News, & Discussion] chriskwarren:
No. I have the new SIM card, and still getting reception issues. Its 30 days to get my device replaced by my carrier, Bell. Their return policies really suck, so I have to get special permission to return the phone (their policy says 14 days OR 50mb data used for a normal return). I reported the issue on day 16, and I have used more than 50mb of data. they wanted me to RMA the device to LG, but I said that was not acceptable for a device that 2 weeks old. I have to ship my device to another province where Bell will inspect it, and then apply the proper credits to my account...up to 30 days, probably 2-3 weeks.

This is why I was a bit neurotic about getting this phone as in the US, the return policies seem much better. I could probably find a better carrier for this, but I won't do better than the plan I have.
[LG V30 Guides, News, & Discussion] jcsww:
I just passed through Ajax on my way to Oshawa. Cell Mapper readings seemed more informative than LTE Discovery. I had it running from Pickering GO to Whitby GO and took a screenshot while sitting at Ajax GO. On band 2 connected to Bell, the range was 87Db to 96Db. Specifically at Ajax GO, the range was 89Db to 93Db. This info was taken using my Nexus 6P with a T-Mobile USA SIM roaming on to Bell Mobility Canada's network.

Edit: When returning any phone, factory reset it and dispute the usage. You can argue that those minutes and data were used on another device that you swapped back to because of the poor connectivity and importance of having a working device.
[LG V30 Guides, News, & Discussion] ChazzMatt:
Sorry, I mis-read.
[LG V30 Guides, News, & Discussion] chriskwarren:
Incredible support, thanks! I'm assuming that " On band 2 connected to Bell, the range was 87Db to 96Db. Specifically at Ajax GO, the range was 89Db to 93Db." is considered a good signal, correct? I used this site to figure it out: http://usatcorp.com/faqs/understanding-lte-signal-strength-values/

Band 2 is what I think I was using with the v30. I think I'll do the return, and pray that I get a phone with no other issues.
[LG V30 Guides, News, & Discussion] jcsww:
That is considered to be a good strong reception. You shouldn't really be concerned until you go above 110Db. My 6P will still hold a connection up to 118Db but my Nexus 5 was always no service at anything above 115Db.

I am just leaving Oshawa shortly. I will pull another reading from Whitby to Pickering again to see if the results are consistent. It is now rush hour so the towers should be more congested, which will provide a bit more incite on how many connections the towers in that area can handle.
[LG V30 Guides, News, & Discussion] jcsww:
fAIRLY SIMILAR RESULTS ON THIS PASS. jUST OUTSIDE OF wHITBY THOUGH, i MANAGED A READING OF 77Db and then 72Db about 2 minutes before Pickering. in Ajax, it wasn't too busy but the reasings were 91Db to 98Db. I have screenshots that I can copy to my PC and attach. On the way back at Pickering though, I couldn't get a reading under 109Db from any of the 4 tours I hit.
[LG V30 Guides, News, & Discussion] chriskwarren:
Thanks! I have sent the V30 I had in. Hopefully the turnaround is quick. The price of the phone has dropped $300 here, if they give a refund I'll take that and just go to the store and pick up another for cheaper lol.

Throughout the day the ZTE Axon did get a slightly better signal with no internet dropouts. So while it did not 'look' as good as the Samsungs I have used, the actual reception was better on my non carrier $189 device than my carrier-supplied $1100 one lol. I took the chance and sent it in, and I did say goodbye first :)
[LG V30 Guides, News, & Discussion] jcsww:
Finally got around to pulling the screenshots from my phone.

This morning / This afternoon
[LG V30 Guides, News, & Discussion] chriskwarren:
I'm sitting at home now with a Xioami Mi A1 (global version) I got at Canada Computers on sale yesterday and I'm getting much better reception at home so far than the V30 I sent back. Looks like I'm getting full bars on LTE, and I'm getting about 50-60mbps consistently on LTE (band 4) vs my V30 which got around 10Mbps on band 4 (or 7...I'm trying to recall as I don't think I wrote it down). I hiked last night and saw no dead spots either on the A1.
[LG V30 Guides, News, & Discussion] jcsww:
Try to avoid using band 7 when possible. It's slow and sucks being up on the higher end of the spectrum. It definitely sounds like the V30 you had was the problem. Although signal levels and reception will vary by phone, it shouldn't differ too much usually. When I get my V30+ and head back to Canada (just before Christmas), I will be in south Ajax for the Canadian family Christmas party on the 23rd. I will take some more readings to see how it differs from my Nexus 6P. I may also pick up an H933 if the promotion of $0 is still on after Christmas if I am exceptionally happy with my V30+.
[LG V30 Guides, News, & Discussion] chriskwarren:
Here at work (Ajax) on the Xioami Mi A1 and getting a better LTE signal (where I had no signal at all on the V30 I had). Using band 4, LTE discovery shows ~-108.0dBm.

Last night on my hike the A1 did drop down to hspa a number of times, but I never lost reception. On that same hike, the V30 would lose LTE and never bother to try hspa.

So I was all happy with my decision to wait the 30 days to exchange my V30 I sent in...but...

Just got an email my my colleague (who has a V30) and he is saying he is noticing lots of dead spots on his V30 as well (bought from Bell, on the same plan as I am). This was the same V30 I compared my V30 to, and saw his was better at holding a lte signal. He is saying that he is currently at another work site (Oshawa, not far from the 401) that has always worked for him in the past on his Note 4, and has no reception now. I emailed instructions to him on how to set the network mode to hspa/3g and see if that helps him, as it did me.

I won't see this colleague until Wednesday where I will try it again. I'm beginning to think that there is poor band support for the V30 here/and or the radio is not switching back to hspa mode quickly enough when there is a poor lte signal. That said, the one time I compared mine to his he had a connection when I did not. I had a good connection (or so I thought) for about a week, and he had a good connection for a bit and seemed to lose it after about a week or so.

Does this make any sense? Should a phone's reception degrade like this? Loose antenna? etc?
[LG V30 Guides, News, & Discussion] jcsww:
That's interesting to know. Where i was in Oshawa was south of the 401 (Lakeview Drive). I have never noticed any issues with signal there on my Nexus 6 or 6P. Once you get farn enough north of the Oshawa Centre though, signal tends to be pretty crappy. With the hardware being the same between models, I am guessing that the only actual difference is the radio software. Because the Canadian model (H933) has to cover a bastardized variety of technologies in a mix and match mess. It makes me wonder if that is the problem.

I will be in south Ajax on the 23rd with my V30+ (H932). Because I loathe family parties, I can sit around and compare my Nexus 6P's reception to the V30+ from T-Mobile. I also take the GO and Via a lot when up this way. Once I have a V30+ to compare it with, we can get an idea as to whether it's the software or not. If Telus still has that deal on with it for $0 after Christmas, I might pick one up to test them side by side. If they don't, my work schedule is fairly flexible on certain days so i could always come out to Ajax to compare devices side by side.
[LG V30 Guides, News, & Discussion] chriskwarren:
Thanks! I'm doubting my trouble-shooting steps now with this issue and I am starting out from scratch. I thought originally that me messing with that dialer code changed something as I didn't notice any change in cell reception until around the time I tried it. Turns out that the code did nothing as the code did not work at all, and now my colleague is seeing the same issues and he did not mess with any dialer codes. I don't think its a carrier issue as we both bought our V30s a week apart, and after about a week I noticed data dropping out and my colleague did not with his brand new device. Now, after about a week, my colleague is noticing what I did. Could be placebo.

He did switch over from LTE to HSPA and he lost all signal when he did so. For me, switching over to HSPA made my connection better. I'll see if he will let me install lte discovery on his phone to get a dBa reading now that I know what else to look for in my renewed troubleshooting.

But I am concerned now that the V30 might not have great coverage in this area (which really should be very good). Maybe its something software could fix at some point, but I find it strange that on a brand new device I (and a colleague) am dealing with issues on cell reception in what i thought was one of the best covered areas in the country. The 401 corridor near Toronto where I work should see good reception. In north Bowmanville where I live I can see spotty reception. I just have not had to think about this stuff in a very long time.
[LG V30 Guides, News, & Discussion] jcsww:
Going all the way back to the LG Nexus 5. I used to flash the T-Mobile radio images to my phone for the best reception up here. A 2 bar difference was worth it. My Nexus 6 and Nexus 6P also run the T-Mobile radio images. I wonder if that is a part of the reason why the signal on my devices is very good by comparison. Until I have the V30+ in hand and am back in Canada. I won't be able to do any more than guess, but it does seem like a likely possibility. If it turns out to be the radio software, then the Canadian carriers can get on LG to release an update to help with the issue. If I end up with two (one from Telus), I know who to complain to if there is a big difference in reception.
[Google Chromecast] jason2678:
I started having this problem in the last week, and I haven't found any solutions here or elsewhere on the internet.

I have multiple chromecasts. One of the old USB stick looking ones and a few of the newer round ones. I've used them for years with a mediatomb server to stream local content to them, and it has typically worked pretty well. Now they've started working really flaky. They'll either drop connection entirely or skip to the next video on the mediatomb server after about 30 minutes of playback. The server is a desktop with wired gigabit ethernet to my router. The chromecasts are all using wifi. I haven't changed the configuration of anything in ages.

The first time I noticed it a movie stopped that my wife had cast using some app (I forget what it is called) from her iphone. I power cycled my router and the chromecast, then cast it from my android using Localcast with similar results. Playback kept stopping after 20 - 30 minutes. I factory reset that chromecast and set it up again, same results. I tried a different chromecast, same results. I set up mediatomb on my laptop to try a different server, same results. I tried ushare and rygel for some other dlna servers on the laptop, same results. Netflix, HBO Go and services like that still seem fine, but these chromecasts just refuse to work right with local dlna servers anymore.

I don't know much about troubleshooting these little buggers aside from all the resetting and swapping stuff I've tried. Previously they always just worked. Is there anyway to get any logs off these things in an unmodified state? Anyone else seen anything like this recently? I'm very suspicious that a chromecast firmware update might have started this behavior, since it came out of nowhere and I've changed nothing on the equipment I control.
[Android General] MannyPanwar:
This Method Is For Rooting Lyf Water 7 i.e LS-5504 running 6.0 android

Proceed At Your Own Risk I m Not Responsible For Any Damage To your Phone

:o To Begin Root Process First DOWNLOAD THESE FILES-

1. TWRP(working ported by me) Zippyshare Link

Mirror Mediafire link

2. Minimal ADB & Fasboot Tool for Android https://devsjournal.com/download-minimal-adb-fastboot-tool.html

3. Sp flash tool https://spflashtool.com/ :eek:

4. Scatter files for our device https://www.mediafire.com/file/qy2be6cxv7e0j9r/MT6753~1.TXT/file Mirror - Zippyshare link

5. supersu zip Click here (this is property of chainfire all credits belong to them)

NOTE - Backup your contacts, messages and data in sd card or pc as it will be gone ;)

Now follow instructions-

1. Install minimal ADB & Fastboot ( i prefer u install it in C:\ drive) Open the file named cmd. This will open a command prompt

2. Power off phone. Once it is off click volume up and power button together ,now screen will show a smalll menu/boot menu. Press volume up to move arrow to fastboot mode and select it by pressing volume down button. You will enter fastboot mode now.

3. Connect phone to pc using data cable. Come back to command prompt. Type this command.

fastboot devices

it will show your device like 5DSOYL.. something like that

now type another command

fastboot oem unlock

Now check your phone it will ask about unlocking bootloader press volume up key to agree

this will delete all data

after this type

fastboot reboot

your bootloader is unlocked now

4. Keep device connected. once phone reboots, open Sp flash tool. select the scatter file (downloaded above) then on recovery tab select the recovery.img (download above). Click the download button and then power off your phone.

Twrp will be flashed, You can access it by Pressing volume up and power button together and selecting recovery in boot mode (where we selected fastboot mode)

5. To gain root just flash su zip through Twrp :p so simple

In case recovery don't get flashed there may be problem in sp flash tool drivers .. plz google how to install them :o

Still working in 2019, files updated to latest version and dead links replaced :good:
[Android General] DevanandaDS:
Any custom ROM available for this model?

I successfully rooted n installed TWRP recovery, now next step is to flash custom ROM so asking
[Android General] ShaikhAaqib:
i have made one but not tested it yet....

i'll test it by tomorrow... if you want i can provide u the link
[Android General] smit451:
Yes Provide Me link i have to test that rom earlier.

Yes Provide Me link i have to test that rom earlier.
[Android General] ShaikhAaqib:
i will upload it tomorrow and give u the link bro...
[Android General] MannyPanwar:
Hello folks. Answering the questions above there is no custom rom for lyf water 7s. lyf water 7s don't has any sort of development on xda. I would advice not to mess around more then rooting because if you phone got hard brick (when it's stuck on logo) it won't be possible for you to flash it as sp flash tool will not recognize your device. Just get a new device.
[Android General] ShaikhAaqib:
true, but it is possible to port a rom for it, just that the procedure is difficult, since not many people use this device there is no development on this i guess..

i tried to port a rom... but i failed, i guess i did not unlock the BL... no idea.. it didn't go well..
[Galaxy S3 Neo Q&A, Help & Troubleshooting] ZarakiSuperSu:
Samsung Galaxy s3 neo. So, my problem is that i recently bought extended 7000mAh zero lemon tri cell battery, and i can't get my phone to recognize it, it thinks it has 2100mAh battery, it's switching off at 1% but after i take battery out and put back in it has plenty of power left. :/ i tried changing Rom, now it's CM 12.1-20150428-UNOFFICIAL-s3ve3g,

Kernel is 3.4.0-cyanogenmod-g5f0621e robert@robert#1

Tue Apr 28 22:17:38 CEST 2015, please help on my stock oryginal rom it didn't worked as well.
[Galaxy S3 Neo Q&A, Help & Troubleshooting] veli123:
Dude.... Extended battery?! These batteries are a big falsh, use ORIGINAL Samsung battery and you'll get more power. I am not joking extended batteries are bogus and drains fast. I switched from extended 2600 mAh (too good to be true) to original new fresh battery. Original one has more power than EXTENDED one...
[Galaxy S3 Neo Q&A, Help & Troubleshooting] ZarakiSuperSu:
Dude if u have nothing smart to say just stay quiet, extended battery lasts me for 2 solid days only issue is that i need to take it out and put it back, surely u were just not smart enough to know how to use an extended battery, and to your's extended 2600mAh its weird capacity so guess it was fake, or if it was really extended poropably after ur phone shut down u could just take battery out, put it back in and have like 30% power still... I know its not crap or fake it really is 7000mAh just my system is taking info about battery from hard coded file in kernel.. Gezzz
[Galaxy S3 Neo Q&A, Help & Troubleshooting] veli123:
I don't know. But I don't believe that 7000 mAh battery can be sold for example $40...
[Galaxy S3 Neo Q&A, Help & Troubleshooting] needforszpit:
Sorry but its no way possibble to use bigger capacity battery with corrected capacity... for example anker 7200mah I have but just with replace trick it use the extended capacity...

The problems is same on charge fase too... 3 time of replaces and reconnect the battery is needed to charge at real 100%.