Any one figure out how to flash the T-mobile Wifi Calling to the CM7, tired using the Nexis one and it says something about it failing and needing the correct code. I really don't know how to code to try to get it to work. I have little to no signal in my house and I can't seem to figure it out. The apk install force closes and give errors once system is loaded.
Try this it is pulled from eagleblood rom see if it will work with CM7 its a flashable install of the file that you need to flash through CWM.
http://www.multiupload.com/6I34S746Q8
Dowloading now will update if good or not. If this works I owe you a million...
Nope This applications wifi calling force close...
There has to be more to it than what was extracted....
Anyone else got any ideas
I tried that on CM #3 and it didn't work
I tried putting the original one from the g2x to cm7 - it did not work.
I was wondering - maybe someone can make it work if they get the one that comes for the nexus 1 or some other phone? One, thats actually designed to work for cm7 ?
here is the link to the one that works on nexus one HERE
I played around with getting this working last night, but basically only got as far as Wi-fi Calling loading, but not working. In other words, it would give an error about an Invalid SIM, and naturally wouldn't work. I might play around with it a bit more tonight and look at the logcat a bit more, but I suspect there is some glue code that is missing to make it work. It might make more sense to seriously consider getting it to work once CM7 gets a bit more stable on the phone.
trasnam said:
I played around with getting this working last night, but basically only got as far as Wi-fi Calling loading, but not working. In other words, it would give an error about an Invalid SIM, and naturally wouldn't work. I might play around with it a bit more tonight and look at the logcat a bit more, but I suspect there is some glue code that is missing to make it work. It might make more sense to seriously consider getting it to work once CM7 gets a bit more stable on the phone.
Click to expand...
Click to collapse
How did you did not get FC?
Latest nightly thats gonna drop will have wifi calling. Don't know if its the T-Mobile wifi app. Hopefully its in build 11
Sent from my G2x running Cyanogen mod.
question.com said:
Latest nightly thats gonna drop will have wifi calling. Don't know if its the T-Mobile wifi app. Hopefully its in build 11
Sent from my G2x running Cyanogen mod.
Click to expand...
Click to collapse
#11 is up!
EDIT: Got it working, WiFi Calling is built in in CM #11, works just fine.
Nightly build 11 is loaded with T-mobile Wifi Calling thanks everyone for the extra support.
Related
What's the deal with wi-fi calling working sporadically with CM7 based ROMS? Or...am I the only one experiencing this? Maybe 1/5th of the time I'm connected to wifi will it work. It's not my router or lan (I know what I'm doing in that realm) +my wife's G2X was working the whole time she had the unmolested phone from T-Mobile. Even after I flashed hers with a 2.3.3 (two days ago) it's worked as it should.
Bump d bump.
I'm not using CM7, but it's happening to me, too. From what I've read over the last few days, this is more of a hardware issue than a ROM issue. For me my 4G often stays on while the wifi is enabled. My wife has a G2x running the same kernel and ROM as mine, and hers has no problems. It's really annoying.
You're not using a CM7 derivitive and you're having issues? Odd. I've only experienced it on CM7 based ROMs. Every 2.3.3/ota/stock based ROM connects with nary a problem.
Sent from my LG-P999 using XDA App
Have you tried using one of the kangs ..there's fitsnuglys and rustys ... I pretty much use fits' kangs, he uses only certain commits in his kangs and from what I understand rustys contain all off the commits up to date... I've never really had a problem with wifi calling and I use it a lot at work...
I haven't. This is my 1st smartphone. 1st time rooting/custom rom'ing and the "kang" sounded too scarey! Might have to give it try though, i miss sixaxis.
Thanks for the tip.
I've had similar problems where the 4G icon stays on with the Wifi and wifi calling enabled along with not being able to get mms to send or receive but sms works fine with wifi calling enabled. I also had the mms problem on the rooted tweaked OTA rom.
Scoobyracing03 said:
I've had similar problems where the 4G icon stays on with the Wifi and wifi calling enabled along with not being able to get mms to send or receive but sms works fine with wifi calling enabled. I also had the mms problem on the rooted tweaked OTA rom.
Click to expand...
Click to collapse
I've had some of the same problems in the past... I've also had mms work over wifi no problem but I've flashed slow many I can't remember which one it was.. LOL.. I really have to start keeping track... IMHO my phone functions better for me when I run a custom rom than a stock .. wifi calling is a must for me because my garage gives me horrible reception and I can't be missing customers calls and I usually only have that problem when running a stock rom...
swuln said:
Have you tried using one of the kangs ..there's fitsnuglys and rustys ... I pretty much use fits' kangs, he uses only certain commits in his kangs and from what I understand rustys contain all off the commits up to date... I've never really had a problem with wifi calling and I use it a lot at work...
Click to expand...
Click to collapse
Thanks!
It works! Well, it worked all night and into the morning. Have never had that with any other CM7 ROM. I wonder what Fits' kang does differently. Any "gotcha's" I need to know about?
Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
slacka-vt said:
Anybody try either of these yet? I've tried the Droid Inc2 (Vivow) build and it's great. Thats how I found the Xoom builds. I haven't seen anyone officially post them in the Xoom Development section. Milestone build date is 2/7/2012 . Might have to give it a try.
https://sites.google.com/site/androidopenkangproject/downloads-1/milestones
Click to expand...
Click to collapse
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
nadiros said:
I have used their crespo (Nexus S) daily for awhile now and it is the best ROM I have ever used period.
The wingray version however needed some work...I say needed because the version I tried still had 3G icons etc in the status bar and other issues. These guys (Roman) are
frikkin OCD on perfection so when this was overlooked I stayed away til now. I dont even think he has a Xoom.
I'm sure they will get it caught up and then will simply kick ass like the rest of their work. I am about to try the latest build 25 and will report back.
Click to expand...
Click to collapse
I'm glad to see I wasn't the only one bugged by the 3G signal showing in the status bar on Wingray. It wasn't a huge deal, but one of those little things you always notice once you see it the first time. There were a few other things, but overall it's a nice build.
I also use AOKP on my Nexus S as a daily driver and I'm very happy with it. No big issues to call out. Once the wingray builds progress a bit more and those few little bugs are worked out, I'll most likely switch to it as my main rom.
Build 25 - 3G icon bars still there.... feels superficial however I didn't test much further . I will continue to periodically check in on them... but like I said - for this aspect to be overlooked then they're not paying attention to wingray for some reason
I am used the Kang rom for a while primarily because it has volume button wake built in. But after a while that tweak just stopped working so now I'm back on Bugless Beast for Xoom.. There's still plenty room for improvement for the Kang rom so I'll try it again at a later stage.
I've built from source and removed the 3G radio icon. It's something I'm sure they'll get to. I noticed someone posted a bug report on that to them already. I posted what they need to do to get rid of it. I might post my build but only after getting permission to do so from them. Run's great with my oc kernel.
Well from what I see they (Team Kang) have discontinued their Wingray builds. Rootz wiki has a pitiful thread that has dwindled and I see only a Stingray release for Xoom as far as the latest build 30.
WTF !
Anyone know whats up?
Great so far but one question to those using it.
Allow apps to write to SD card is in the feature list.
How do I access this? Using various apps I can only write to media memory. Even if I change the path to /mnt/external1/. It just creates that folder within the internal memory.
Any help would be appreciated.
youtube fix attached until i can bake it into the rom and reupload, expect a few more changes once the reupload happens
hey guys
updated with usb mass storage quickfix
back again with a new rom port. this is cyanogenmod 9 for the heroC.
please do not expect cm9 to be a magic cure all for all the problems we still face on our older devices. this runs equally as well as eligorom (evervolv) and will most likely stay at the same pace as evervolv
i take no responsibility for your phone crashing and burning in an epic fashion, or the naked zombie from miami starts a worldwide zombie outbreak. or war, or famine, or disease, or anything of the sort. try at your own risk, dont bother me if your phone blows up
dont give me any credit, give the following people mad props and donate to them if you wish to:
erwinp for youtube fix
stritfajt for getting the camera working
mongoosehelix and all the crew over at the eris forums
1ceb0x for the kernel minfree tweaks and the crew over at the hero gsm forums
dsixda and his kitchen
matt, jaybob, dastin and the heroc crew
zeppelinrox and his v6 supercharger script
tvall and the crew at the g1 forums for the rom
all the people who test this rom and give me feedback
im sure i forgot people, im sorry if i did and if i forgot you please yell at me and ill make sure to thank you
what works:
touchscreen
sdcard
radio (data and calls)
adb
camera preview and taking pics
fixed keyboard
wifi
sound
buttons
audio
root
vibration
bluetooth
zeppelinrox's supercharger script
minfrees are set at boot, no need to change them
video playing from sdcard (software encoding)
displays correct carrier, and hopefully mms should be fixed
usb mass storage (had to use an app, not ideal, but working)
youtube (non hd)
what im working on:
need someone to test mms with stock app
what doesnt work
hardware acceleration
youtube hd (almost unrealistic, at least it works)
probably others
works with problems:
camcorder (displays preview but will not record)
long press home displays large previews, not sure why just yet
other stuff im sure
when you flash this, remember i did not sign it, so if your using clockworkmod recovery toggle signature verification
i reccomend downloading Script Manager from the market and running V6 supercharger. the reason behind this is while minfrees are set already, trebuchet could use being bulletproofed.
this is the gapps i use from evervolv eris: http://www.mediafire.com/?qbpc1zthauh4c1h but feel free to use whatever ones you want
and now for the link:
CM9HEROC v1-1
http://www.mediafire.com/?zutjrhbizhuhhqu
md5sum: 2d9fb865dae038a9c87e4e13db2b5a4c
happy flashing!
Thank you
will pull my Hero out of the draw and give this a shot!
Does camera autofocus work or do we still have to set focus to infinity?
i havnt tested it out yet, but seeing how there is little to no difference at all between evervolv, aosp, and cyanogenmod ics, if we run into camera problems in one ics rom, we will have it on all ics roms
im going to take the safe road and say no autofocus doesnt work, still gonna have to choose infinity. we're amazingly lucky to have camera on ics, and stritfajt did his best to give us what we have.
I was getting nothing but fc's when I flashed this :/ I have firerats at 170 50, and nothing is different from flashing other ics roms. I was able to get through the gapps setup, and settings worked fine. The fc's I remember seeing were browser, email, trebuchet, and the gapps process.
Sent from my HeroC using XDA
hey shakes,
yeah fc's are an unfortunate part of our ics experience right now. if you flash just cm9heroc, you dont get half the fc's as flashing gapps also.
gapps are slowing down our ics roms pretty noticeably bad. im not 100% sure what to do about it at the moment, but im investigating.
when you get those fc's, just hit wait, and then wait a minute or 2 for everything to chill out on your phone, and you shouldnt have many (or hopefully any) force closes after that.
(this is my assumption that you had just flashed the rom and gapps and got all the fc's immediately)
can anyone test if mms is working through the stock app? much appreciated
oh hey and im going to be uploading another build with a way of fixing usb mass storage, not my ideal way, but it works. plus a few build.prop tweaks.
Which sources/manifest are you using? I've been off and on working on cm9 with our TeamICS repos on github. It compiles and boots fine but every app force closes and then the phone starts melting. I haven't had enough time to figure it out but seems you got it all working! Look forward to testing this out.
I'll try just flashing cm9, but wouldn't trebuchet (the launcher) still fc? And these aren't fc's where you're given the option to wait, it's just the dialogue that basically says such and such app stopped working, just letting you know, hit okay to dismiss. Haha. I'll take another look later today and see what's going on, right now I need my phone so I'm running your everevolv rom.
Sent from my HeroC using XDA
Shelnutt2 said:
Which sources/manifest are you using? I've been off and on working on cm9 with our TeamICS repos on github. It compiles and boots fine but every app force closes and then the phone starts melting. I haven't had enough time to figure it out but seems you got it all working! Look forward to testing this out.
Click to expand...
Click to collapse
+1
Same too on the GSM hero side
hey kayant and shellnutt
i ported this from g1. i dont have the internet speed to download the repos or else i would be working on a true cm9 port built from source. sorry for the inconvenience.
shakes,
the only time ive gotten trebuchet to force close on me is when i first boot the phone and unlock the screen too fast. if you can, try to get a logcat and let me know if you find anything out of place.
I'm not sure if I can, I'll definitely look into it though. Any chance of an update for this?
always a chance for an update to this, i just have to have something to update from since i cant build from source.
if anyone knows how to build from source, has the internet speed to dl and the processor and memory to build, PLEASE build cm9 from source. then we can pull in all the fixes that are going to make it into future versions of cm9.
if anyone manages this, please upload your work.
whoshotjr2006 said:
always a chance for an update to this, i just have to have something to update from since i cant build from source.
if anyone knows how to build from source, has the internet speed to dl and the processor and memory to build, PLEASE build cm9 from source. then we can pull in all the fixes that are going to make it into future versions of cm9.
if anyone manages this, please upload your work.
Click to expand...
Click to collapse
This is why we were merged with evervolv, so that any changes they make for devices like ours get to us.
Sent from my HERO200 using XDA
there has to be a way to pull those changes from evervolv over to cm9 though, they are basically sitting on the same base. really its just frameworks that are different, and not different by too far.
i respect everything that the evervolv team is doing and i appreciate the hell out of them for keeping us in mind even with how old our phone is, but many of us are used to the cyanogenmod feel after using it forever on many different phones.
as long as some device like ours has a cm9 built from source though, ill continue to port it on over to heroc and hopefully keep everything evervolv has working consistent through changes.
Hey ya'll, I was just snooping around here in the hero forum since I just flashed a rom on my wife's sprint hero. I see ya'll have a cm9 port over here as do we Evo'ers too. I am using CM9 from Team D.I.R.T over there in evo land. It is great and I thought it would be worth mentioning that "videocam illusions" works great with CM9 on the Evo 4g. We use it to replace the native camcorder. It is free in the Google Playstore. You can give it a try, nothing to lose. Maybe you will get lucky.
thanks cityneversleepz ill have to give it a try, been super busy havnt had time to mess with my phone in a while
I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.
Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app
Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.
had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.
I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
Official builds are out and can be found here...
https://download.cyanogenmod.org/?device=d850
I used the 6.0 micro build gapps from here
http://opengapps.org/
SupaAvenger79 said:
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
I used the 6.0 micro build gapps from here
http://opengapps.org/
Nightly Build available here..
https://drive.google.com/folderview?id=0B4rZYkaJF5V0Z3RlR08yclZiVUE&usp=sharing
Click to expand...
Click to collapse
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
crash4fun said:
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
Click to expand...
Click to collapse
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
[Thanks! Will definitely follow this until CM puts out an official build. Couple other guys that were building unofficial seem to have stopped for the time.
SupaAvenger79 said:
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
Click to expand...
Click to collapse
Ah, yes it appears to get a lock for me as well, but then won't navigate. I've tried messing with gps.conf in several different manners but no luck.
I'm about to abandon the G3 because there is no official CM support. This is where Cyanogenmod is getting bad press - they claim to offer an alternative OS with the latest updates, but some phones are just left in the dust because no one wants to be the maintainer. Best Buy has started selling the 6P - may head over and pick this up!
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
KennyG123 said:
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
Click to expand...
Click to collapse
Sure thing
https://github.com/CyanogenMod/android_kernel_lge_g3
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
scsgoal31 said:
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
Click to expand...
Click to collapse
Yeah I am hoping the problems are not D850 specific or we will never see a fix. I will keep posting builds semi nightly until CyanogenMod starts posting an official build or until I get a new phone in August. I really think this is still a good phone and wonder why the community went to hell on this one.
Have a Happy New Year everyone.
I've been using CM13 for almost a month and its been great. However I only just got an SD card for Christmas. Now, I'm assuming moving apps to the SD card has changed since it let's you format as internal storage now. However that doesn't work for me. Does anyone know how to move apps to the SD card without formatting it as internal storage?
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
slabity said:
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
Click to expand...
Click to collapse
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
https://source.android.com/source/initializing.html
Then I made a local manifest to include proprietary drivers from https://github.com/TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
SupaAvenger79 said:
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
Then I made a local manifest to include proprietary drivers from TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
Click to expand...
Click to collapse
Strange. That's exactly what I did too.
I'll give it another shot and see what's going on. I'd like to take a crack at fixing some of the bugs.
Looks like tonight's build will fix the power charging issues. Yay!
Just posted the the 12/29 build and GPS is fixed we can now find our nearest Hardee's with ease. Thanks @invisiblek
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
xVermicide said:
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I had data problems too on Tmo, a quick APN adjustment fixed it:
https://support.t-mobile.com/thread/95900?start=0&tstart=0
thanks, I applied the changes so I'll see if I have anymore problems. if not then this 13 is my new daily driver.
Sent from my LG-D850 using Tapatalk
Just flashed, great so far! Thanks OP!
Sent from my LG-D850 using Tapatalk