An hour ago this was going to be a totally different post.
I'm using an ATT branded, black HTC One. My SIM is for T-Mobile. Like many others, I'm experience issues with sending/receiving MMS. I had been using Android Revolution HD 71.1 and would be unable to send MMS. Strangely, though - my ability to send them seemed locations specific. At work it was no problem, at home it would fail every time.
Unless I disabled WiFi. With WiFi disabled, they seemed to send no problem, but with WiFi and Mobile Data simultaneously enabled it would return errors. Disabling WiFi while at home was an inelegant solution, so I tried downgrading to Android Revolution HD 30.6, which is Android 4.3 rather than 4.4.2. This seemed to have done the job. Until it no longer worked.
Same issue. Wifi disabled - fine. Wifi enabled - unable to send MMS. Everything else works fine, phone calls, mobile internet, etc.
This was meant to be a post advising others how to fix this problem. Instead I'm right back where I started.
This is very frustrating. Especially since I thought I had found a solution only for it to fail once again.
Miguel_Lancaster said:
An hour ago this was going to be a totally different post.
I'm using an ATT branded, black HTC One. My SIM is for T-Mobile. Like many others, I'm experience issues with sending/receiving MMS. I had been using Android Revolution HD 71.1 and would be unable to send MMS. Strangely, though - my ability to send them seemed locations specific. At work it was no problem, at home it would fail every time.
Unless I disabled WiFi. With WiFi disabled, they seemed to send no problem, but with WiFi and Mobile Data simultaneously enabled it would return errors. Disabling WiFi while at home was an inelegant solution, so I tried downgrading to Android Revolution HD 30.6, which is Android 4.3 rather than 4.4.2. This seemed to have done the job. Until it no longer worked.
Same issue. Wifi disabled - fine. Wifi enabled - unable to send MMS. Everything else works fine, phone calls, mobile internet, etc.
This was meant to be a post advising others how to fix this problem. Instead I'm right back where I started.
This is very frustrating. Especially since I thought I had found a solution only for it to fail once again.
Click to expand...
Click to collapse
When I was running the T-Mobile 4.4.2 with Sense 5.5 I had issues receiving MMS when connected to WiFi. They would always fail, I would have to disconnect from WiFi and then the MMS would automatically receive. But, since the update to the T-Mobile 4.4.2 Sense 6.0 OTA rom, all the MMS now work as normal whether I'm connected to WiFi or not.
I do know that the SMS app called ChompSMS has a specific T-Mobile setting that will temporarily switch from WiFi to cellular to send/receive MMS and back again. Maybe you can try that if you don't want to run the stock ROM.
@Miguel_Lancaster
Try upgrading to the latest tmous firmware. 5.14.531.1 ,might help. I will include the latest tmous radio and radio config. I have an att phone/sim, but i'm running gpe firmware and rom. I hope this helps.
It had seemed when I first got the device up and running that everything was fine with MMS (that was using 4.4.2, Sense 6.0), but either after a certain number of messages, or while in certain areas I would have to turn off WiFi to be able to send MMS.
That's why I tried downgrading to 4.3 with the alternate version of Android Revolution HD (essentially a tweaked version of the stock HTC ROM). What I find odd about the two version of that ROM (30.6 vs. 71.1) is that the installer for one includes an model selection screen and the other treats them all alike. 30.6 allows me to choose between International, ATT/Developer, Sprint, T-Mobile, etc.
Initially I chose ATT/Dev as that's the hardware model of my HTC One and wasn't keen to deal with a soft-brick. As stated in my first post, this seemed promising initially but shortly after ran into the same bug. I flashed one more time and tried using the 'T-Mobile' model selection during install. This has proven the most reliable method for me thus far. I suppose it would have to do with the radio being flashed between versions? It's curious to me that a similar option is not included in the other ROM version -- something I wanted to address in that ROM's development thread, but am prohibited from doing currently due to my post count.
Anyhow, 4.3 with Sense 5.5 seems to finally be working for now. Android 4.4.2 and Sense 6.0 did have some some aesthetic differences that I preferred, in addition to seeming marginally faster. I'll deal with an older version of the OS though if it means my phone functions properly.
Thank you both for your replies.
One thing that may be worth mentioning is that I've yet to enable Group MMS in my messenger settings this go-around. I suspect that its coincidental, but I'm reluctant to see what happens if I do enable it.
Maybe I'll try again with 4.4.2 in the future, but all this flashing, re-flashing, and settings tweaking becomes pretty tedious. In relation to that point: Does anyone have any experience with the built in HTC/Google app backup/sync. For some reason I've never really trusted any all-in-one solutions to be reliable, especially between ROMs or Android versions. Perhaps I should trust them more?
P.S.
CID Getter app lists my CID as CWS_001 --
don't know why I never bothered checking that until now. Could changing it to TMO_001 be helpful at all or does it not matter?
I broke MMS again, but this time I figured out how!
AdBlock Plus seems to be the culrpit.
As soon as I installed it MMS stopped working again. Unless WiFi gets turned off. Or ABP. If ABP is disabled everything works fine.
I did some research and it seems to be that ABP filters traffic on port 80, the same port that MMS send/receive.
I tried changing my APN settings for T-Mobile to operate through port 8080 as a workaround, but that didn't help. For now though, seems that AdBlock Plus is the perpetrator. I'm gonna try one more time with 4.4.2 and see if I can duplicate the same results.
Miguel_Lancaster said:
I broke MMS again, but this time I figured out how!
AdBlock Plus seems to be the culrpit.
As soon as I installed it MMS stopped working again. Unless WiFi gets turned off. Or ABP. If ABP is disabled everything works fine.
I did some research and it seems to be that ABP filters traffic on port 80, the same port that MMS send/receive.
I tried changing my APN settings for T-Mobile to operate through port 8080 as a workaround, but that didn't help. For now though, seems that AdBlock Plus is the perpetrator. I'm gonna try one more time with 4.4.2 and see if I can duplicate the same results.
Click to expand...
Click to collapse
Hi Miguel, I can confirm that AdBlock Plus will prevent you to send and receive MMS. Looks like the app block traffic on the port used by MMS. I have personally experienced this issue, and disabling AdBlock Plus solved it. There is also a few thread here that discuss that issue (irc, I posted in those). This issue was also reported hundred of times on AdBlock Plus forum, not sure if there is any solution (except for disabling it): https://adblockplus.org/forum/viewtopic.php?f=11&t=11755#p66133
edit:
http://forum.xda-developers.com/showthread.php?t=2326679
http://forum.xda-developers.com/showthread.php?t=2335038
http://forum.xda-developers.com/showthread.php?t=2301551
alray said:
Hi Miguel, I can confirm that AdBlock Plus will prevent you to send and receive MMS. Looks like the app block traffic on the port used by MMS. I have personally experienced this issue, and disabling AdBlock Plus solved it. There is also a few thread here that discuss that issue (irc, I posted in those). This issue was also reported hundred of times on AdBlock Plus forum, not sure if there is any solution (except for disabling it): https://adblockplus.org/forum/viewtopic.php?f=11&t=11755#p66133
edit:
http://forum.xda-developers.com/showthread.php?t=2326679
http://forum.xda-developers.com/showthread.php?t=2335038
http://forum.xda-developers.com/showthread.php?t=2301551
Click to expand...
Click to collapse
Yup, it's a shame that such a well documented bug has gone unfixed.
Good to finally have figured out my problem, only took a few days of tinkering to finally narrow it down to ABP and be able to make a relevant search to back up my hunch.
Related
After updating to the 4.3 OTA update on my HTC One (originally Sense, but converted over), I can no longer use tethering on the device. The OTA update when through by itself and didn't require me to flash the ROM manually.
Other devices will connect to the HTC One's Wi-Fi connection perfectly fine, but can't access the internet. It was working fine before the update and I do have tethering on my Fido cell plan (I tried the sim in an iPhone 5 and the tethering works fine). All of the APN settings are the same from before the update. I've tried different APNs, but that hasn't worked either.
Anybody else seeing this issue with either their genuine Google Play edition or converted Sense HTC One running 4.3?
coffee_coffee said:
After updating to the 4.3 OTA update on my HTC One (originally Sense, but converted over), I can no longer use tethering on the device. The OTA update when through by itself and didn't require me to flash the ROM manually.
Other devices will connect to the HTC One's Wi-Fi connection perfectly fine, but can't access the internet. It was working fine before the update and I do have tethering on my Fido cell plan (I tried the sim in an iPhone 5 and the tethering works fine). All of the APN settings are the same from before the update. I've tried different APNs, but that hasn't worked either.
Anybody else seeing this issue with either their genuine Google Play edition or converted Sense HTC One running 4.3?
Click to expand...
Click to collapse
I'm on Rogers and it's working just fine for me. It's a converted HTC One by the way. I'm not running a true GE ROM. But it's a custom GE ROM. Sinless 3.1 To be exact.
I did have the exact problem you speak of before though. I simply wiped out all tethering settings and re did them. I've also switched to Bluetooth tethering instead. Seems to work a little better for me than the WiFi hotspot.
coffee_coffee said:
After updating to the 4.3 OTA update on my HTC One (originally Sense, but converted over), I can no longer use tethering on the device. The OTA update when through by itself and didn't require me to flash the ROM manually.
Other devices will connect to the HTC One's Wi-Fi connection perfectly fine, but can't access the internet. It was working fine before the update and I do have tethering on my Fido cell plan (I tried the sim in an iPhone 5 and the tethering works fine). All of the APN settings are the same from before the update. I've tried different APNs, but that hasn't worked either.
Anybody else seeing this issue with either their genuine Google Play edition or converted Sense HTC One running 4.3?
Click to expand...
Click to collapse
I've got an issue with tethering, nothing I do seems to work. It works on 4.2.2 though
I just posted this in the general GE talk, but I can't use my WiFi after using the native tethering.. its like the native program isn't restarting the WiFi drivers properly
Sent from my Nexus 10 using Tapatalk 4
M3drvr said:
I'm on Rogers and it's working just fine for me. It's a converted HTC One by the way. I'm not running a true GE ROM. But it's a custom GE ROM. Sinless 3.1 To be exact.
I did have the exact problem you speak of before though. I simply wiped out all tethering settings and re did them. I've also switched to Bluetooth tethering instead. Seems to work a little better for me than the WiFi hotspot.
Click to expand...
Click to collapse
Unfortunately, both Bluetooth and USB tethering don't work either.
Scratch that! Crazy. Last night I was tethering and right while I was Bluetooth tethering it just stopped. After an hour. And now I can't ever get it to work again. I guess I'm joining in the crowd that can't.
M3drvr said:
Scratch that! Crazy. Last night I was tethering and right while I was Bluetooth tethering it just stopped. After an hour. And now I can't ever get it to work again. I guess I'm joining in the crowd that can't.
Click to expand...
Click to collapse
I'm unfortunately in the same boat. If I slap the SIM card in my other phones it can tether effectively, I'm guessing something changed in 4.3?
gusto5 said:
I'm unfortunately in the same boat. If I slap the SIM card in my other phones it can tether effectively, I'm guessing something changed in 4.3?
Click to expand...
Click to collapse
I just thought its crazy it was working for an hour and then all the sudden it stopped. I even pulled a logcat of when it doesn't work it and the dev can't see anything wrong. I'll even attach the logcat here to see if anyone can find anything. You'll have to look for the tethering labelled sections unfortunately i didn't trim it down.
M3drvr said:
I just thought its crazy it was working for an hour and then all the sudden it stopped. I even pulled a logcat of when it doesn't work it and the dev can't see anything wrong. I'll even attach the logcat here to see if anyone can find anything. You'll have to look for the tethering labelled sections unfortunately i didn't trim it down.
Click to expand...
Click to collapse
I don't think you're crazy. I believe it's specifically to do with tethering while on LTE. I have it working on 3G/H+ without a problem
Sent from my One using XDA Premium 4 mobile app
I couldn't get it working for either. I typically only use H+ and shut off my LTE. There is a fix though for this.
IMO this thread should almost be a sticky as this affects many many people! Here you go:
http://forum.xda-developers.com/showthread.php?t=2398011&highlight=tethering
Hello all,
I live in Europe so after buying my HTC One, I proceeded to root it and SIM Unlock it (Successfully).
All was well and good, until a month or so later the phone begins to behave strangely.
When I hit Home there is a stutter and pause and the home panels appear as though the process had just been started (When it should be kept in the background). The App drawer would refuse to populate with apps and the phone would freeze and heat up (Extremely hot) at random times and for random lengths of time.
Having used Cyanogenmod on my Desire HD I decided to give it a go and bypass my problems altogether. It worked great! No more crashes or anything like that. Except I cannot pick up any GSM signal. Through messing with the mobile network settings I can get it to show "3" (my network) as the local network, but I cannot receive or send messages or calls.
After a lot of experimenting with tonnes of ROMs I have figured out that no custom ROM will give me a signal!
But every ROM that is based heavily on sense (Like Viper 1.1.0 for the HTC One) experiences the same crashes I had suffered with initially.
Does anybody have any ideas about this issue?
I use TWRP recovery and Factory Reset (via TWRP) before every flash.
Bump?
I am currently on stock and my phone continues to crash regularly for anything between 2-20 minutes. The issue has gotten a lot worse and my backup from months ago (just after SIM Unlock) does not help the issue. I don't know what the root cause is but it is something to do with Sense so I need to use another ROM. Does anybody have anything to add to the Signal/Reception issue I'm having with custom ROMs?
Okay one last bump.
Tried all the Sprint HTC One specified ROMs I could find, still no service.
Tried different radios, every network setting under phone info and mobile settings. Countless reboots.
APN settings never appear, rarely does the phone pick up my 3 Network but never has reception.
My recent desperate google searches are actually brining me back to this thread!
Stock sense is still spontaneously crashing when I restore to it, for when I need to use my phone again.
Hey, I know I'm talking to myself at this stage but to anyone who gets here in the meantime and has the crashing issue...
Installing something like Apex or Nova launcher instead of HTC Sense seems to solve it.
I guess blinkfeed had decided to become suicidal or something.
Anyway, the GSM issue is still there with other ROMs.
Sent from my HTCONE using xda app-developers app
Like i posted in your previous thread, did you try downgrading to a ROM having build 1.29?
Settings> About > Software Information > More > Build number
indy1811 said:
Like i posted in your previous thread, did you try downgrading to a ROM having build 1.29?
Settings> About > Software Information > More > Build number
Click to expand...
Click to collapse
Yes. I am currently running a stock that is Software Version 1.29.
I have tried a 1.31 version of stock too but the same issue exists across all the versions I could find, concerning the crashes. The only solution so far has been to change the Launcher.
Thanks, for checking out this thread too.
GMach234 said:
Yes. I am currently running a stock that is Software Version 1.29.
I have tried a 1.31 version of stock too but the same issue exists across all the versions I could find, concerning the crashes. The only solution so far has been to change the Launcher.
Thanks, for checking out this thread too.
Click to expand...
Click to collapse
One final thing i can think of...
Did you try editing your build.prop file?
I changed these settings:
gsm.sim.operator.alpha
Vodafone
gsm.operator.iso-country
in
ro.ril.hsupa.category
6
ro.ril.hsdpa category
10
gsm.sim.operator.iso-country
in
gsm.operator.numeric
40486
ro.telephony.default_network
3
gsm.sim.operator.numeric
40486
These are settings for my telephone operator in India. You might want to google for your settings...Have a look at the other settings as well.
I'm having issues with wifi after converting my HTC one to a Google Edition.
I'll connect to my school wifi fine, but every single time, after a certain amount of time it just stops working. I'll still be connected to the wifi network, but I can't connect to the internet.(When I'm at home, I don't have this issue)
My friend also has the HTC One stock, and wifi works fine. My gf has a nexus 4, so it uses stock android with no problems.
What is with my HTC One GE that isn't working?
I've tried a factory reset twice now, and it didn't help at all.
Help is appreciated! This is super annoying and is literally hindering my productivity because I don't have enough data to just use cellular service.
Help please
Sent from my HTC One using Tapatalk
What happens on stock Sense firmware? If you are S-OFF, flash Dev edition RUU and test.
lettuceman44 said:
I'm having issues with wifi after converting my HTC one to a Google Edition.
I'll connect to my school wifi fine, but every single time, after a certain amount of time it just stops working. I'll still be connected to the wifi network, but I can't connect to the internet.(When I'm at home, I don't have this issue)
My friend also has the HTC One stock, and wifi works fine. My gf has a nexus 4, so it uses stock android with no problems.
What is with my HTC One GE that isn't working?
I've tried a factory reset twice now, and it didn't help at all.
Help is appreciated! This is super annoying and is literally hindering my productivity because I don't have enough data to just use cellular service.
Click to expand...
Click to collapse
Yeah. That is a Google Play Edition Issue on 4.4 KitKat and above... you won't be able to fix this issue (except rewriting a part of GPE)
This here helped me in Wi-Fi's like your school wifi:
[root] Pry-Fi
but if you disconnect and reconnect you have to re login because you have a new Mac...
LibertyMarine said:
Yeah. That is a Google Play Edition Issue on 4.4 KitKat and above... you won't be able to fix this issue (except rewriting a part of GPE)
This here helped me in Wi-Fi's like your school wifi:
[root] Pry-Fi
but if you disconnect and reconnect you have to re login because you have a new Mac...
Click to expand...
Click to collapse
Gah, not what I was hoping for
I was hoping it was a specific issue I had, not an actual android issue.
Why is it only GPE that is affected by this? Explains why my GF's nexus 4 works well.
This is a bummer. I guess I have to revert back to stock.......I get disconnected and reconnected from wifi all the time due to the wifi not being 100% everywhere on campus.
Thanks for the help, at least I know now that I can't do anything about it, time to go back to stock.
Are the revert to stock guides in you're sigs work from a GPE to stock?
i know how you feel
lettuceman44 said:
Gah, not what I was hoping for
I was hoping it was a specific issue I had, not an actual android issue.
Why is it only GPE that is affected by this? Explains why my GF's nexus 4 works well.
This is a bummer. I guess I have to revert back to stock.......I get disconnected and reconnected from wifi all the time due to the wifi not being 100% everywhere on campus.
Thanks for the help, at least I know now that I can't do anything about it, time to go back to stock.
Are the revert to stock guides in you're sigs work from a GPE to stock?
Click to expand...
Click to collapse
it's not just the GPE, I switched my AT&T HTC One to Developer Edition and have lost wifi since 4.4. I downgraded back to stock and worked my way up the updates with no luck. back to dev edition now 4.4.2 and still no luck
robbie09 said:
it's not just the GPE, I switched my AT&T HTC One to Developer Edition and have lost wifi since 4.4. I downgraded back to stock and worked my way up the updates with no luck. back to dev edition now 4.4.2 and still no luck
Click to expand...
Click to collapse
I just went back to stock sense 4.3 and I'm having the same issues still. Before conversion I had no issues.
Why is it still happening?
Could a factory reset work? I assumed when I flashed the ruu it just wiped everything.
lettuceman44 said:
I just went back to stock sense 4.3 and I'm having the same issues still. Before conversion I had no issues.
Why is it still happening?
Could a factory reset work? I assumed when I flashed the ruu it just wiped everything.
Click to expand...
Click to collapse
Run the full RUU if available.
What do you mean by that? I converted my phone from GPE back to stock using the AT&T ruu.
Sent from my HTC One using Tapatalk
I really need to fix this issue, it's becoming a liability
I don't know what else to do
Sent from my HTC One using Tapatalk
Bump again.
Sent from my HTC One using Tapatalk
Still looking through the internet for help, still found none.
similar issue
I'm on ViperOne 4.4.2 with similar issues. Only my router is a meter away from me, so the connection is excellent. Wifi on phone keeps disconnecting, but what is interesting, it does so like it's scheduled to do so. For an example - it'll work fine for an hour, more or less, & then it'll start to play games - disconnect, reconnect, scan for networks & show nothing, or try to connect & fail, or even get stuck at 'turning on'. Every problem that I have with my wifi can be temporarily 'fixed' with a reboot, then wifi will work fine for some time & start to disconnect again. HELP?
BTW this started after 4.4.2 update. I've downgraded back to 4.2.2, to 4.3 & now I'm back on 4.4.2, no changes. Did this update **** something up in my phone's hardware or what?
http://android-revolution-hd.blogspot.com.es/2014/02/how-to-fix-wi-fi-htc-one.html
I have a similar problem to what was initially discussed in this thread. Company wifi has multiple routers throughout the building/department - when I first connect to the system everything works great, but after moving to a different room and connecting to a different router (same network/wifi) the internet connection is lost. I stay connected to wifi, with strong signal, but don't have any data connection. In order to get internet back I have to turn the wifi off and back on - everything works fine until I walk into a different room and connect to a different router.
I'm on an HTC One Google Edition - don't remember having this problem before rooting the One from Sense to GE, but I wasn't streaming radio broadcasts of baseball games over the internet until a week ago, which was when this became a real annoyance.
I recently took the plunge and updated to Cloudyfa's CloudyG3 2.0+ Rom and it is super awesome. There is a HUGE General Discussion thread here:
http://forum.xda-developers.com/showthread.php?p=56644031
Here is the main Rom thread:
http://forum.xda-developers.com/showthread.php?t=2783192
It is for all variants but it is a port of the GSM G3 rom. So some things aren't 100% on our VS980 roms. Just to be certain, everything is working for me but it takes a few tweaks, hence the point of this thread.
Here are the main issues off the top of my head:
Cellular doesn't work out of the box
You have to manually change it to LTE/CDMA. It took a few times to get this to work. I also use an app from the Play Store called "TellInfo" which lets you select "LTE/CDMA/EvDo/GSM/WCDMA" (which seems to work best for me). You also have to go into Settings > Tethering & Networks > Mobile Networks and select "Data Enabled" and "Data Roaming". The Network mode that seems to work best is "Global" mode.
I would advise that you check with your data plans to make sure you aren't being charged a crazy amount of money to roam on other networks. At this point (I travel), I haven't racked up any additional charges.
MMS doesn't work with the stock Messaging App
This requires downloading Textra or Hangouts for SMS/MMS handling. I like Textra.
Verizon Visual Voicemail doesn't work
I get a really weird text message when I get a voicemail. I assume this is trying to communicate to the Verizon Voicemail app. It doesn't work. I have to resort in manually checking voicemail the old fashion way. I am looking for better options
Other random facts
The keyboard no longer has arrow keys in the nav bar when typing. I've read the G3 rom keyboard is supposed to let you swipe the spacebar for left/right movement... but it doesn't work nor do I see any options.
WiFi File Sharing is gone from the G2. The G3 took this feature out, which is really really sad. A good alternative is "Samba Filesharing". Same thing except can't be launched from the Notification Shade
Otherwise, the rom is beautiful and pretty. The Xposed G3 Tweaksbox has tons of options for some really neat features. Everything else works the same/better then stock G2 software. I don't know if I could go back to the stock G2 rom after using this for a few weeks. Outside of the small issues listed above (SMS/MMS being the only semi-big one) it works and looks so good that it is a keeper.
Any additional tips and tricks to making the CloudyG3 rom work better on our VS980 Verizon LG G2s, please share!
For a Lollipop Theme using G3 Tweaksbox:
Theme: http://forum.xda-developers.com/devdb/project/?id=5684#downloads
Notification Icons: http://forum.xda-developers.com/showthread.php?t=2717736
@player911
Although I appreciate the time you spent working this up for people, its in the wrong section.
This really should be in the Verizon specific General section (maybe q&a?)
Just to add on a bit. Any time I flash one of his ports, I just change the build prop.
I use ROM toolbox pro, light would work, but the app you really need (that's built into it) is root explorer.
I change the tele device to 10, country to US (make sure its caps) and carrier to vzw, and I never have an issue with LTE sticking or anything of the sort.
Obviously you would change the country if you don't live in the US.
I haven't done any of these changes and if seems fine...
Sent from my VS980 4G using Tapatalk
Thats weird I've been running this rom on my vs980 for a few weeks now. Everything worked perfect for me without having to mess with any settings at all. Also messaging worked without a hitch. Only thing i noticed while driving was the signal would say roaming sometimes. A reboot would correct this issue. Think it has something to do with the 3g to 4g hand off.
Jeff Zaugg said:
Thats weird I've been running this rom on my vs980 for a few weeks now. Everything worked perfect for me without having to mess with any settings at all. Also messaging worked without a hitch. Only thing i noticed while driving was the signal would say roaming sometimes. A reboot would correct this issue. Think it has something to do with the 3g to 4g hand off.
Click to expand...
Click to collapse
If it is roaming that means you're in a 3g area
I tried this for awhile on more than one occasion and every time, my sms would eventually take hours or days to receive. It was maddening. Did not matter what app I used, fixed apn settings, tried everything. It would work for a day or two then messaging totally fell apart.
Sent from my VS980 4G using Tapatalk
Lawlrus said:
If it is roaming that means you're in a 3g area
Click to expand...
Click to collapse
Are you actually roaming though? Or does it just say so?
mulhiny said:
Are you actually roaming though? Or does it just say so?
Click to expand...
Click to collapse
Its cosmetic.
The reason it does it, is because the ROMs he builds are based off of international builds. So they don't cater to vs/ls980 as they use cdma
Edit: Same reason why the stock messengers won't send mms
---------- Post added at 07:14 PM ---------- Previous post was at 07:05 PM ----------
Also, I just flashed the new cloudyg3 2.1, (I think?) and it looks like all the normal changes I make to the build prop are already done.
Country and tele device number.
I am having MTP issue. It refuses to go into MTP mode.
Does anyone know how to fix this?
I put build.prop fix in and it did not make any difference.
Otherwise, it appear to be pretty good. But battery drain seem a bit higher than stock.
Lawlrus said:
Its cosmetic.
Click to expand...
Click to collapse
Great to hear..I'll note that the G3 tweaksbox has an option to kill the roaming icon and then you can use the Verizon icons..perfect.
Since flashing this last night I've had no troubles. GPS, LTE, MTP, everything is working...
"Verizon Visual Voicemail doesn't work
I get a really weird text message when I get a voicemail. I assume this is trying to communicate to the Verizon Voicemail app. It doesn't work. I have to resort in manually checking voicemail the old fashion way. I am looking for better options"
anyone solve this? Same problem for me with any custom rom.
Does anyone know how to get the automatic login working for the my verizon mobile app? I tried inatalling the verizon login from the play store and that didnt work, so I tried restoring a backup of the app from stock and that didnt work. I converted both to system apps and that didnt work either! ? Anyone please help its important that i get this working.
mrdunn said:
"Verizon Visual Voicemail doesn't work
I get a really weird text message when I get a voicemail. I assume this is trying to communicate to the Verizon Voicemail app. It doesn't work. I have to resort in manually checking voicemail the old fashion way. I am looking for better options"
anyone solve this? Same problem for me with any custom rom.
Click to expand...
Click to collapse
I gave up on VVM a while ago. Had to call Verizon and have them deactivate it. Now I just get a regular notification when I have a VM.
The only good alternative to actual VVM I've found is Google voice.
How does CloudyG3 perform compared to an AOSP rom on our G2? I'm running AICP right now and love the stock feel, but have some issues like GPS. Is the G3 UI that much better than AOSP?
com.android.phone keeps crashing on me.. basically making the phone useless on this rom. Anyone else have this issue? If so.. any luck fixing it?
Lawlrus said:
@player911
Although I appreciate the time you spent working this up for people, its in the wrong section.
This really should be in the Verizon specific General section (maybe q&a?)
Click to expand...
Click to collapse
Well my intention was to put it in the VS980 General Section. Im not sure if it got moved or where it currently is, as I am on mobile.
I am running 2.0 and heard 2.1 has the phone force close that prevents usage. It appears some people experience this while others dont. Could depend on previous rom.
Im in no rush to update. I'll check out the build prop changes. I have root explorer. Although I thought that this was the purpose of the aroma installer.
I have selected the Verizon icon set in G3 Tweaksbox but still see the occasional Roaming icon. Not a big deal. Still works fine.
arctic84 said:
com.android.phone keeps crashing on me.. basically making the phone useless on this rom. Anyone else have this issue? If so.. any luck fixing it?
Click to expand...
Click to collapse
I had the same exact issue so I was forced to downgrade to 2.0, and the dev didn't really seem to know how to fix it, although 2.0 is truly great on the VS980. Would be great to be able to run 2.1, although I was able to get it to work as soon as I changed it from global mode to any other mode that started to crash.
arctic84 said:
com.android.phone keeps crashing on me.. basically making the phone useless on this rom. Anyone else have this issue? If so.. any luck fixing it?
Click to expand...
Click to collapse
2.1 worked fine for me no issue for two days. You either didn't clean flash, or did something wrong.
Sent from my Vs980 running Validus 4.4.4
Lawlrus said:
2.1 worked fine for me no issue for two days. You either didn't clean flash, or did something wrong.
Sent from my Vs980 running Validus 4.4.4
Click to expand...
Click to collapse
KK baseband - check
full wipe - check
2.1 rom - check
What am i doing wrong?
arctic84 said:
KK baseband - check
full wipe - check
2.1 rom - check
What am i doing wrong?
Click to expand...
Click to collapse
You tell me. It works fine.
You restoring system apps and or data?
Using xposed modules?
Flashing a different kernel?
Removing system apps?
Flashing any mods such as status bar with the ROM?
You check md5?
Using twrp 2.8.1?
Sent from my Vs980 running Validus 4.4.4
So I have the T-Mobile variant of the LG G4. I had it unlocked straight from the carrier a while ago and all seemed well. Recently I noticed a huge amount of battery drain and 4G LTE usage from T-Mobile's pre-installed apps--mainly com.tmobile.pr or something which is the "My Account" app (imagine being at 60% left with 27% of the drain having been an app and only 9% the screen. Yeah, it was that bad)
This I obviously found unacceptable, so I went ahead to try and uninstall the bloatware. Lo, much to my dismay, Tmobile has locked it down so you can't uninstall the bloatware, and you can only disable it. This alone irked me enough that I wasn't satisfied with just a disabling. I knew I wouldn't rest until I had obliterated it.
I've had plenty of android phones over the years and done my fair share of rooting and flashing ROMs and the like, but I hadn't touched that aspect of my G4 because I wanted a dependable device for school and I didn't want to mess around with it. I knew I'd have to root it to get rid of the tmobile bloatware so I went and did that using the Low effort root method (http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765). When this was done a lot of my background processes started to continuously crash. I decided to go ahead and put TWRP as the custom recovery and just go ahead and get some dependable 6.0 ROM, and I found a couple of them.
When I flashed the first ROM, the play store services were crashing so I found the google apps package for marshmallow and flashed that too. It seemed to fix the issue. Yet when I would click on my School's WiFi at the setup (which is WPA2 Enterprise) it would crash and say "Unfortunately WiFi has stopped working." I thought that perhaps I mucked something up in the flashing of the ROM, or that maybe there was an issue with the ROM in general, so I decided to just flash another ROM entirely (after factory resetting it all the way). Along the same time as this I found a slightly more modified and feature packed version of marshmallow by this lad here (http://forum.xda-developers.com/g4/development/h815-genisys-rom-1-0-classic-v10g-t3192649). I decided to go ahead and use this one since it had a h811 version there, that involved flashing a h815 and then flashing a patch.
The "Unfortunately WiFi stopped working" issue persisted, however. I found this odd. I then noticed that if I click any other network that ISN'T the WPA2 enterprise network my school is working that everything seems to work fine.
I went ahead and factory reset it all the way again in the hopes that would fix it. No luck.
I booted it to safe mode and tried to connect to the WiFi network from there. No luck.
I downloaded a third party WiFi app off cellular and tried to connect from there. No luck.
I can't enter the WiFi's name and try to enter directly because it crashes there too.
I can't "Forget" the network as it's never joined that network before so there's nothing to forget. It does let me enter the advanced options but a direct press causes it to crash.
So throughout ROMs and wipes and safe modes and all, this one issue has persisted, where my phone's WiFi will crash when it tries to connect to my school's WPA2 Enterprise network. I've tried plentiful fixes short of flashing back to a 5.0/5.11 stock (which I'm hesitant to do because I read something about phones bricking after they downgrade from Marshmallow using the .kdz files or something?).
I'd really appreciate any help that y'all can provide. I've read these forums for ages but this will be my first time making an account because I can't find anybody else with the same issue and its proving to be quite a pain.
tl;dr wifi isn't working with only one particular network and no fix I've tried under this sun has worked so far. help will be appreciated pls
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
esjames said:
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
Click to expand...
Click to collapse
I got the brown leather variant from Tmobile and it only says H811 as far as I can tell. Not sure of if its the "n" version or not.
I have not tried that rom but ill be sure to give it a go, hoping it will help solve the issue. I did some additional testing and can confirm the issue lies with all WiFi networks that employ WPA2 Enterprise security.
Will there be any issue with the Rom when downgrading from Android 6.0? I was reading about phone's bricking when trying to downgrade certain versions or bootloaders on the tmobile variants.
I'm pretty sure going back to stock 5.1 will be fine. The Tmo variant hasnt been upgraded to 6.0 yet and the ports don't update the bootstacks. Read here --> http://forum.xda-developers.com/tmobile-g4/development/global-marshmallow-6-0-port-to-h811-t3232760
Update: It seems that any Android 6.0 flash cuts off the ability to connect to Enterprise wireless networks. I went ahead and flashed to the debloated stock rom on the thread you mentioned, but it cut off the ability to record video. As such, I went for the xTreme version that you mentioned, and flashed the camera restores and all.
Everything works fine now as far as I can tell. I also got rid of the Tmobile applications draining the battery and all that. All should be well. Thanks again for the help