Has anyone figured out which radio version works best with WIND Mobile in Canada?
My phone seems to randomly lose data connection. To get data back, I turn mobile data off then on again. It happens so frequently, I have it in my Notification window as a toggle.
I have Automatcher v7 to match RIL with radio version. I also have wipe EFS.
Thanks,
Scott
Sent from my HTC Vision using XDA
skewty said:
Has anyone figured out which radio version works best with WIND Mobile in Canada?
My phone seems to randomly lose data connection. To get data back, I turn mobile data off then on again. It happens so frequently, I have it in my Notification window as a toggle.
I have Automatcher v7 to match RIL with radio version. I also have wipe EFS.
Thanks,
Scott
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
You could try to change your APN settings. Also i thought the DZ dosent work on wind because it has differrent frequencies?
Sent from my HTC Vision using xda premium
evilcuber said:
You need to change your APN settings. Also i thought the DZ dosent work on wind because it has differrent frequencies?
Click to expand...
Click to collapse
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?
skewty said:
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?
Click to expand...
Click to collapse
As someone who has friends on Wind... I'm thinking it may be your network. Also, you're not supposed to match the rils unless you're using sense. Which ROM are you running?
Sent from my Transformer TF101 using xda premium
skewty said:
Oops! I meant G2 (T-Mobile). I have a G2.
If my APN settings were incorrect, why would my data work most of the time?
Click to expand...
Click to collapse
Use latest Radio from T-Mobile 26.13.04.19_M, I'm on it, have never lost 3.5 G data connection
I am currently running ILWT but experienced the same running CM 7, ICS Audacity and ICS Quattro.
I have flashed the newest TMobile ROM a few times.. It must be the WIND network here.
Sent from my HTC Vision using XDA
Update
I don't think it is the network. My father's Amaze does not have this problem in the same places.
ILWT has been the most reliable ROM for me so far. I am currently running Andromadus b4 and am considering switching back because of the data drop-out issue. I have tried 5 different radio versions now.
It must be the ROM. Perhaps it encounters some data it can't make sense of and crashes. Perhaps it just needs to restart itself when this happens. A simple mobile data off, mobile data on fixes it almost every time.
I also find the bars reading incorrect. I be driving down the road with my screen on and the charger plugged in, and it will show me full bars. I can pull over and park for a few minutes, bars still full. Then suddenly half bars, no bars. This behavior is from a device that isn't being physically surrounded / shielded and is stationary.
Anyways, my G2 is getting old and it needs a another core to keep up with the way I now use it. I will wait for Jelly Bean but will likely switch to IOS.
Reasons If You Care
The menu button disaster is a big one for me. Also the lack of quick updates from Google for Nexus S and Nexus One. These devices should have had OS updates released on the same day the Galaxy Nexus was released.
ICS should have been backwards compatible for older devices as well. A few #ifdef in the code for fancy screen rendering and such. Big, huge fail!
Google, also, should have required no physical menu button for access to Google apps to enforce the new way. With only like 7% ICS market share no wonder app devs write for GB.
Google's handling of Android updates has opened my eyes.
skewty said:
I don't think it is the network. My father's Amaze does not have this problem in the same places.
ILWT has been the most reliable ROM for me so far. I am currently running Andromadus b4 and am considering switching back because of the data drop-out issue. I have tried 5 different radio versions now.
It must be the ROM. Perhaps it encounters some data it can't make sense of and crashes. Perhaps it just needs to restart itself when this happens. A simple mobile data off, mobile data on fixes it almost every time.
I also find the bars reading incorrect. I be driving down the road with my screen on and the charger plugged in, and it will show me full bars. I can pull over and park for a few minutes, bars still full. Then suddenly half bars, no bars. This behavior is from a device that isn't being physically surrounded / shielded and is stationary.
Anyways, my G2 is getting old and it needs a another core to keep up with the way I now use it. I will wait for Jelly Bean but will likely switch to IOS.
Reasons If You Care
The menu button disaster is a big one for me. Also the lack of quick updates from Google for Nexus S and Nexus One. These devices should have had OS updates released on the same day the Galaxy Nexus was released.
ICS should have been backwards compatible for older devices as well. A few #ifdef in the code for fancy screen rendering and such. Big, huge fail!
Google, also, should have required no physical menu button for access to Google apps to enforce the new way. With only like 7% ICS market share no wonder app devs write for GB.
Google's handling of Android updates has opened my eyes.
Click to expand...
Click to collapse
The issue isn't ICS. The issue is the vendors haven't released proper drivers for ICS. What we're dealing with is code we've hacked up to make things work. If the vendors released ICS source code for our devices things would be much more stable.
We're always working within our means. It's not Android/Google's fault and it's not an ICS issue, it's just circumstance.
Thanks
I realize where most of the issues lie. I am an EE grad so I can imagine how difficult hacking ROMs together without device drivers might be.
Writing ASM for a microproc with the datasheets is bad enough. Without knowing what each control register is for and what each bit controls, it is a guessing game at best. I get that.
I very much do appreciate your work. As you are aware, from reading my post, I run a ROM you contribute to. Thank you. You have prolonged the life / pleasure balance I require from my smartphone.
I would contribute more to the development, but my post count was less than 10. I was actually working towards my 10 posts today to post in the dev forums. (The Andromadus beta 4 thread to be more precise).
skewty said:
I realize where most of the issues lie. I am an EE grad so I can imagine how difficult hacking ROMs together without device drivers might be.
Writing ASM for a microproc with the datasheets is bad enough. Without knowing what each control register is for and what each bit controls, it is a guessing game at best. I get that.
I very much do appreciate your work. As you are aware, from reading my post, I run a ROM you contribute to. Thank you. You have prolonged the life / pleasure balance I require from my smartphone.
I would contribute more to the development, but my post count was less than 10. I was actually working towards my 10 posts today to post in the dev forums. (The Andromadus beta 4 thread to be more precise).
Click to expand...
Click to collapse
Drop by #g2ics on freenode if you're interested
I have the same issues, G2 on Wind as well. I've had some ROMs where it never occured, but then they had some kind of bug that left me unhappy. I'm currently on CM 7.2 RC1, and I keep a "data" toggle in my notification bar. When it drops I toggle it off and on and it connects again pretty quickly. Until about twelve months ago, MMS was unreliable, but I don't seem to have problems with that anymore.
In general I'm not happy with Android, but as the alternatives are all utterly closed systems I guess I'm stuck with it. It would be unbearable if it weren't for the hard work of all the developers around this forum. Thanks, developers
Agreed. Google has been a huge let down for me as well. Updates are slow or non existent in Canada (even on Nexus devices). Look at the percentage of devices that run ICS. JB is what ICS was supposed to be. I may get an iPhone for work. I am excited to compare it to my Samsung S3 on CM10.
Sent from my SGH-T999 using xda app-developers app
Related
Are we going to see this come to Ice Cream Sandwich ever?
I suppose the most logical move will be for the devs to wait until ICS comes out on a T-mobile device that also has wifi calling.
But that aside - does anyone know of any progress with this application?
captainreynolds said:
Are we going to see this come to Ice Cream Sandwich ever?
I suppose the most logical move will be for the devs to wait until ICS comes out on a T-mobile device that also has wifi calling.
But that aside - does anyone know of any progress with this application?
Click to expand...
Click to collapse
I think that one version had it working with the GB wifi call but it has since broken, so I think it will work after kinks are sorted out
Wifi calling is incredibly low on the priority list for most devs right now, but the fact that someone manged to get it working means the outlook is good.
But to answer your other question, yes a Tmobile ICS device with wifi calling will be tremendous help. And I'm sure one is coming
Looking forward to new ICS-Smartphones with Wifi-Calling. I think it comes nearly.
Shouldn't there be a way to access tmo's uma access points using our internet call settings? Might flash back to cm7 just to get the apns...
Sent from my Andromadus ICS HTC Vision using TapaTalk
I think there is some other sim verification that the wifi calling app does that cm7's internet calling does not that allows you to use whatever t-mobile has in place online.
Anyhoo - thanks for the responses - glad to hear it is coming at least sometime in the future!
This is the only reason I'm not upgrading yet. I get poor service at my house.
need help, nothing helped and no wifi yet
Came across this thread. So I thought I'd update you since I last worked on it.
Currently it seems we have to wait for T-mo to release an updated libkineto.so and possibly other libs.
I got it to half work...
SMS/MMS (working)
Recieving a Call (kinda)
Calling out (kinda)
The problems with the actual voice calling are:
-Headset speaker cuts out when proximity sensor kicks in
-When receiving a call it sometimes will work on speaker phone and sometimes there will be intermittent cut outs and long delays. Sometimes it works perfectly fine
-Calling out will only work on the first call and then will require a reboot.
After either type of call the app will freeze and FC.
I'm a novice at developing so there is only so much I can figure out on my own.
However I think it also has some part with how the Roms are working, e.g. Sound cutting out when proxy sensor trips.
If you want to at least know when someone is calling you and send text I attached it, will work across all ICS roms.
Thanks to jerl92 for building a flashable .zip for me
Should be great strides in this with the upcoming release of the One S, all reviews I have seen indicate working wifi calling.
Sent from my HTC Vision using Tapatalk 2
HTC One S has Tmobile Wifi Calling
According to ZDNET we'll get our wish soon as HTC One S for T-mobile has the wifi calling app built in, I can't make a link yet cause I'm a forum noob
One S WiFi Calling
This is a little discouraging
http://forum.xda-developers.com/showthread.php?t=1613767
Read the second post...LAME
BTTRDYZ said:
This is a little discouraging
http://forum.xda-developers.com/showthread.php?t=1613767
Read the second post...LAME
Click to expand...
Click to collapse
Hmm....ok. Strange because Engadget listed Wifi Calling as "good" bloatware on the One S, which indicates an app.
But I imagine that it can still be ported, just implemented through the framework rather than an app. I think. Devs in the development section would know better.
Sent from my HTC Vision using Tapatalk 2
Nospin said:
Hmm....ok. Strange because Engadget listed Wifi Calling as "good" bloatware on the One S, which indicates an app.
But I imagine that it can still be ported, just implemented through the framework rather than an app. I think. Devs in the development section would know better.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Yeah - I'm sure someone will figure out - developers have gotten past much bigger obstacles!
FYI, I've been monitoring this thread looking for the ICS WiFi calling app, but found it elsewhere so thought I'd share in case anyone else is watching this thread. EdKeys has it for Desire/G2 (http://forum.xda-developers.com/show....php?t=1664106) and bigmoew for Sensation (http://forum.xda-developers.com/show....php?t=1654940)
Looks like very recently something has been added to the CM9 repository:
Code:
Merge "pyramid: enable T-Mobile USA wifi calling" into ics
MERGED ON JUN 04TH AT 22:05:33 IN ANDROID_DEVICE_HTC_PYRAMID
_HugoBoss_ said:
Looks like very recently something has been added to the CM9 repository:
Code:
Merge "pyramid: enable T-Mobile USA wifi calling" into ics
MERGED ON JUN 04TH AT 22:05:33 IN ANDROID_DEVICE_HTC_PYRAMID
Click to expand...
Click to collapse
That merge is actually just the params to support wifi calling, and it's not for our device. That said, the entirety of that patch in CM9 is included in what you flash with EdKeys' wifi calling flashable zips.
Has there been anything developed that can be applied to the stock ROM (rooted) to enable the AOSP tether, overriding Verizon's tether?
If not, why?
Is it a kernel issue? Can it be done on a stock ROM at all? Etc...
If you believe it to be possible, can you guide me toward information so that I can dive into this rabbit hole? I have background in development, though I've never touched Android, the OS, or the kernel, so I'm looking for a good place to get started.
I understand that I can just install a custom ROM, but that is not the answer to the puzzle I'm trying to solve.
Sent from my Galaxy Nexus using XDA App
http://www.droidforums.net/forum/galaxy-nexus-development/188611-official-wifi-tether.html
This is not AOSP tether. I have considered poking around in its source though.
As I remember it, my OG Droid needed a kernel modification to run android-wifi-tether where the Nexus doesn't. Figure it might be tapping into something existing.
As I said before, never played around with any of the dev stuff on Android, so feel free to correct my way out left speculation with fact.
Sent from my Galaxy Nexus using XDA App
hgray said:
This is not AOSP tether. I have considered poking around in its source though.
As I remember it, my OG Droid needed a kernel modification to run android-wifi-tether where the Nexus doesn't. Figure it might be tapping into something existing.
As I said before, never played around with any of the dev stuff on Android, so feel free to correct my way out left speculation with fact.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Confused - if it works, why does that matter? Just curious.
I see that devs have it worked out in their ROMS, so I wondered if it was available as a patch in the same way that battery percentage patches have been in the past.
The Android-Wifi-Tether is a good piece of software, but I figure that whatever is built into the OS is probably WAY more stable. I've always had problems with the software for one reason or another and I'm currently having stability issues on the Nexus.
I'm also interested to be able to learn more about how tethering operates on the backend because I'm currently having issues with my tethering speed.
http://forum.xda-developers.com/showthread.php?t=1436598
I could possibly avoid the speed issue by installing another ROM or trying to wipe and see if that fixes it, but that would not actually SOLVE the problem. I want to know why.
Note, should my speed issue go away I would still be interested in getting AOSP tether running.
TLDR; I'm curious too.
you should try this: https://market.android.com/details?id=com.koushikdutta.tether
it can't be blocked by verizon, and it's made by the creator of clockwork mod.
I did try Tether in an attempt to determine if android-wifi-tether was the culprit of my speed problems and I had the same slow results. Aside from that, my interest is in getting the AOSP tether into a patch. I'm setting up to poke around inside the source code now.
Wish me luck!
http://source.android.com/source/initializing.html
The only difference between carrier tether and aosp tether in ICS is provisioning.
http://www.galaxynexusforum.com/for...e-wifi-hotspot-using-unrooted-phone-free.html
Just add a tether widget using Switch Pro Widget and it overrides the check. Easy, free tethering.
adrynalyne said:
The only difference between carrier tether and aosp tether in ICS is provisioning.
Click to expand...
Click to collapse
I tried the tether widget you shared. I'm getting 4G speeds with it, but still not with any other tether program...
Can you point me to some more info about the above quote? I'm not being a smart-butt. Just genuinely curious as to the deeper answer of why. It seems as though the other tether apps are pulling from the 3G radio.
I just thought of a way to test it... Make a phone call while tethering and see if it dies. Not sure if the Nexus has SVDO, but I'll turn off LTE to ensure that it's riding on 3G and make a second test to confirm.
I can't make a call right now, so I'll try later and post results.
I'm still interested in how this is circumvented by the widget and why the 3G is being used be the other tether programs, if this is actually what is happening.
Hmm...
Funny business going on. I just tried android-wifi-tether once more for kicks and now it's running on 4G speeds.
Rebooted the phone to make sure that it stuck and it did.
Not sure why, but still interested to know.
Out in left field (but still reasonable) speculation is welcome.
Sad that I will not get to try and test my 3G theory. I do have my clockworkMod backup and might try it all tomorrow and see what results I get.
hgray said:
I tried the tether widget you shared. I'm getting 4G speeds with it, but still not with any other tether program...
Can you point me to some more info about the above quote? I'm not being a smart-butt. Just genuinely curious as to the deeper answer of why. It seems as though the other tether apps are pulling from the 3G radio.
I just thought of a way to test it... Make a phone call while tethering and see if it dies. Not sure if the Nexus has SVDO, but I'll turn off LTE to ensure that it's riding on 3G and make a second test to confirm.
I can't make a call right now, so I'll try later and post results.
I'm still interested in how this is circumvented by the widget and why the 3G is being used be the other tether programs, if this is actually what is happening.
Click to expand...
Click to collapse
I can confirm also that using a WiFi hotspot toggle will override the Verizon hotspot check. I saw this on another forum and tried it out. It works flawlessly. Apparently this worked on Thunderbolts on VZW but not on other devices. If I had to guess, they implemented the check in a very rudimentary way that is bypassed by using a toggle. The toggle likely just executes a command to enable the hotspot whereas the toggle in the settings has a check in place first and then the command is executed. Either way, it works and I don't have any issues at all.
A more apt title for this thread would be "Verizon tether patch", seeing as AOSP has tethering and doesn't need any patching to enable it, like you do on American carrier-phones.
After digging around in some source code and stumbling upon some relevant topics both here and other forums, I see that this is something that happens before compile. I suppose it would be possible to replace recompiled versions of these files, but I don't know enough about what I'm doing here to make that happen at this point.
A few other people have been down this road of inquisition for ROM development. The answers were out there, I just didn't have the right keywords until I started poking in the ICS source code.
Is Samsung EVER going to fix Wi-Fi disconnect issue??? My phone goes to sleep, on wake up my wifi will not reconnect until i turn it off/on. That's BS. This issue has been ever since ICS update came out.
delfin12 said:
Is Samsung EVER going to fix Wi-Fi disconnect issue??? My phone goes to sleep, on wake up my wifi will not reconnect until i turn it off/on. That's BS. This issue has been ever since ICS update came out.
Click to expand...
Click to collapse
Have you even bothered to troubleshoot your own issue? Obviously since wifi works fine for almost everyone including me it's something with your setup. What do you have your wifi sleep mode set to? Try changing your frequency mode to just 2.4. Have you tried any different networks?
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
no they probably won't...must suck for you not knowing how to navigate through this forum. I've been enjoying a wifi that is always on even during deep sleep...8+hrs for a minute. (thanks agat)
ok so here is a link to a post ....check it
http://forum.xda-developers.com/showpost.php?p=32757404&postcount=37
suggestions...run agat kernel 0.6.2
My WiFi stays connected all night except for even I tell it to shut off with a cron job between 3 and 7 in the morning.
Sent from my SPH-D710 using xda premium
I'm running blazer ics right now and mine does that sometimes, usually after being asleep for over an hour or so. I have my wifi set to stay awake never. Honestly, it's so quick to reset I just don't care enough to fix it lol.
Sent from my SPH-D710 using XDA
Change "Keep Wi-Fi on during sleep" to Always.
Problem solved.
Sent from my SPH-D710 using xda premium
It's a known bug to some. I had a thread about this issue I believe. It had left for a few builds and then reappeared to some on the FI25 build. At one point we narrowed it down to a certain routers but no real evidence. It doesn't matter what your settings are in, even if you keep your settings on "keep awake always". The WiFi just stays as if connected but really isn't. It'll show greyed out bars or not active. I gave up and ignore it.
Laughing at some of you comments here. YES, I HAVE TRIED EVERYTHING. Different routers, all kinds of wifi settings, even used a root explorer to change some wifi settings. Still issues. I am ignoring it now and was hoping for a fix and it's pissing me off. Looks like it may be a hardware issue on some phones
delfin12 said:
Laughing at some of you comments here. YES, I HAVE TRIED EVERYTHING. Different routers, all kinds of wifi settings, even used a root explorer to change some wifi settings. Still issues. I am ignoring it now and was hoping for a fix and it's pissing me off. Looks like it may be a hardware issue on some phones
Click to expand...
Click to collapse
Just a heads up, adding this kind of relevant info to the original post when you make it is helpful
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
ty080279 said:
no they probably won't...must suck for you not knowing how to navigate through this forum. I've been enjoying a wifi that is always on even during deep sleep...8+hrs for a minute. (thanks agat)
ok so here is a link to a post ....check it
http://forum.xda-developers.com/showpost.php?p=32757404&postcount=37
suggestions...run agat kernel 0.6.2
Click to expand...
Click to collapse
I'm running this kernel and mine still disconnects.
Mattix724 said:
Change "Keep Wi-Fi on during sleep" to Always.
Problem solved.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This problem is deeper than a simple setting in the advanced wifi menu.
Sent from my SPH-D710 using Tapatalk 2
Check your router settings.
Sent from my SPH-D710 using xda premium
Bannjio said:
Honestly, it's so quick to reset I just don't care enough to fix it lol.
Click to expand...
Click to collapse
Plus I get a bit more of battery life
Tappin' Typin'
Mattix724 said:
Check your router settings.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
What exactly should I be looking for in my router settings? Btw, wifi still disconnects on Parandroid JB...wtf. Everything worked fine on GB.
I still have the issue where wifi just sucks down my battery worse than 3G when it idles, but the phone gets plenty of deep sleep. It's happened across roms, fresh wipes and only on ICS and never on any gingerbread setups I've used. I've tried 3 different routers, on different frequencies. I've spent countless hours combing through battery and cpu monitors. My final verdict is that ICS was for the most part a total **** show for this phone, and it's only usable because of the selfless devs who devote their free time to tweaks and builds that get the best they can out of it.
Sorry op, but in my anecdotal example, there is no answer for particular wifi problems on ICS with this phone.
Sent from my SPH-D710 using XDA
MustWarnothers said:
I still have the issue where wifi just sucks down my battery worse than 3G when it idles, but the phone gets plenty of deep sleep. It's happened across roms, fresh wipes and only on ICS and never on any gingerbread setups I've used. I've tried 3 different routers, on different frequencies. I've spent countless hours combing through battery and cpu monitors. My final verdict is that ICS was for the most part a total **** show for this phone, and it's only usable because of the selfless devs who devote their free time to tweaks and builds that get the best they can out of it.
Sorry op, but in my anecdotal example, there is no answer for particular wifi problems on ICS with this phone.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I just sure hope that the official JB rom for this phone will fix my wifi issues. It's weird, but some users have no issues with wifi and some do. I wonder if hardware is different. I'm not eligible to upgrade till July next year..kinda want to check out that LG Optimus..but at the same time want to see what GS4 (whenever it comes out) will have to offer
delfin12 said:
I just sure hope that the official JB rom for this phone will fix my wifi issues. It's weird, but some users have no issues with wifi and some do. I wonder if hardware is different. I'm not eligible to upgrade till July next year..kinda want to check out that LG Optimus..but at the same time want to see what GS4 (whenever it comes out) will have to offer
Click to expand...
Click to collapse
What channel and encryption type are you using (for your main connection)? Also what brands of routers have you tried it on. I don't think it is you, but I am just curious.
I use to use Linksys routers, but the last 2 I had were turds different models, and sent them in for RMA to verify the unit wasn't just a bad unit, now I won't use ANY Cisco product unless I have to (after the routers overheating in the middle of winter in my basement with proper ventilation and sending them back a few times, and their new 'secure' firmware that only allows you to connect via their website back into my local router).
lol don't listen to these people telling you to check the router settings...
It is a bug in ICS (most roms i have tried), i suggest downloading an app called Wi-fi keep alive.
nsxla said:
lol don't listen to these people telling you to check the router settings...
It is a bug in ICS (most roms i have tried), i suggest downloading an app called Wi-fi keep alive.
Click to expand...
Click to collapse
i'll try that as my phone got this bug also.
I didn't happen in FH13 Stock rom, but when i upgrade to FI27 this bug is starting out!
weird thing is this bug only occured on my office wi-fi (Linksys WAP54G). No problem occured when I use wi-fi at my home.
I heard if you stand on your head while doing the macarena your wifi won't disconnect. :thumbup:
We are legion, for we are many.
Sent from the DarkSide of the GalaXy with a MEK device
4hn said:
i'll try that as my phone got this bug also.
I didn't happen in FH13 Stock rom, but when i upgrade to FI27 this bug is starting out!
weird thing is this bug only occured on my office wi-fi (Linksys WAP54G). No problem occured when I use wi-fi at my home.
Click to expand...
Click to collapse
Ya the app seems to work, most of the time...Just make sure you launch it after a reboot? - Good enough for me though, also i have all the work arounds checked in advance settings, didn't have the patience to experiment.
Hey everyone, got another official rom for you guys.
I've been building for a few weeks now, all running pretty smoothly on the AT&T variant. Hit me up if you guys find any issues with the Sprint build. I don't have one myself, so I am unable to test.Official CM based, so e975 kernel.
Check it out here: http://codefirex.com/index.php?p=/discussion/258/rom-ls970-4-3-cfx-toolchain-4-8-y-codefirexperiment-nightlies
The good news: Data and GPS seem to work right off the bat, across reboots.
The bad news: It seems that I can't send texts. Also, the signal icon in the statusbar never shows any bars (though it does show the 3G icon). It appears as if I have a dead signal 100% of the time, even though I'm able to browse the internet (albeit very slowly) and make calls.
Thanks for your work!
Sent from my LG-LS970 using xda app-developers app
I got an MMS but no SMS would go through.
But I love AOSP mode
Sent from my LG-LS970 using xda app-developers app
YES!!! MORE OFFICIAL ROMS
Sent from my LG-LS970 using Tapatalk now Free
Link is down.
EDIT
Must have been the site, it's back up now.
prowlingfox said:
The good news: Data and GPS seem to work right off the bat, across reboots.
The bad news: It seems that I can't send texts. Also, the signal icon in the statusbar never shows any bars (though it does show the 3G icon). It appears as if I have a dead signal 100% of the time, even though I'm able to browse the internet (albeit very slowly) and make calls.
Click to expand...
Click to collapse
I have weird connection problems with this ROM as well. It always boots up with the wrong phone number so I can't use any cell radio related functions. I sent some logs to Synergye but not sure if they helped.
Sent from my LG-LS970 using XDA Premium 4 mobile app
I'll take a look at the issue this week / weekend. It's probably some stupid mistake, and I should have it fixed soon, I am just not familiar with CDMA at all yet, and don't have a device to test with myself.
SnowLeopardJB said:
I'll take a look at the issue this week / weekend. It's probably some stupid mistake, and I should have it fixed soon, I am just not familiar with CDMA at all yet, and don't have a device to test with myself.
Click to expand...
Click to collapse
Out of curiosity, I just compared sources between CM and cfXe and not really sure what I was looking for, I removed one line from the cfXe sources, built it, and boom, everything is now working:
device/lge/ls970-common/ls970-common.mk
remove line 187, ro.telephony.ril_class=LgeLteRIL \
I'm not entirely sure of the consequences, but I was getting 3G and 4G, and SMS and MMS were sending both over 3G and Wifi. Also, I noticed a dead touch area on the screen, not sure if it is my device only, but the easiest way to get there is to go to settings, and then try to click on bluetooth.
edit: looks like I have a busted digitizer
Anyone mind testing out this build? It looks like it is not quite there from my side, but I figured I may as well have someone test it out to be sure. The issue is that it is using the GSM ril instead of the ls970 specific CDMA ril. If this does not work, I should be able to get another one out real soon that does fix the issue.
http://http://downloads.codefi.re/snowleopardjb/CFXE-ls970/testbuilds/full_ls970-cfxe-OPENMASTER-20131017.123401.zip
SnowLeopardJB said:
Anyone mind testing out this build? It looks like it is not quite there from my side, but I figured I may as well have someone test it out to be sure. The issue is that it is using the GSM ril instead of the ls970 specific CDMA ril. If this does not work, I should be able to get another one out real soon that does fix the issue.
http://http://downloads.codefi.re/snowleopardjb/CFXE-ls970/testbuilds/full_ls970-cfxe-OPENMASTER-20131017.123401.zip
Click to expand...
Click to collapse
Eh, I'll do it. I got nothing better to do. Brb.
EDIT: the link is messed up, as you wrote it....there's an extra http://. Just thought I'd let you know. But i'm downloading now.
EDIT2: god f****** damn the new TWRP, giving me the option to wipe internal storage.... I knew this would happen eventually. Ughhhhhhh.
---------- Post added at 03:28 PM ---------- Previous post was at 02:49 PM ----------
First things first. Upon initial setup, the first thing that it asks you to do is to insert the device's SIM card. Obviously that doesn't apply to us CDMA folks. It allows you to skip this step, so I did. after a few seconds the phone connected to sprint and 3G data appears to be working. Signal bars are working. I was able to sign in to my google account. I haven't rebooted because I can't test much right now, but the basics seem to be working on initial boot. Can't test GPS right now. Also can't test SMS right now, apologies.
SnowLeopardJB said:
Anyone mind testing out this build? It looks like it is not quite there from my side, but I figured I may as well have someone test it out to be sure. The issue is that it is using the GSM ril instead of the ls970 specific CDMA ril. If this does not work, I should be able to get another one out real soon that does fix the issue.
http://http://downloads.codefi.re/s...ull_ls970-cfxe-OPENMASTER-20131017.123401.zip
Click to expand...
Click to collapse
Testing this build out myself since I also have nothing to do. So far, everything is extremely fast, fluid, and stable! Have working data and everything (But then again, I'm one of the few lucky ones who never had any problems with data ). Gonna test out MMS soon. Only real problem I have with 4.3 AOSP ROMs really is the SMS issue where texts don't send over 160 characters. But I flashed the 4.2.2 messaging apparently, which usually fixes that. So far so good, though! I'm really digging it.
Sent from my Amazon Kindle Fire2 using xda app-developers app
From what I can tell, that "fixed" data, but is still not quite correct. It is most likely just using a generic ril, and not the CDMA RIL that it is supposed to. I am going to do another test build real quick here, then hopefully push the fix before the next nightlies run.
EDIT:
Can someone test out this real quick? I am almost positive this should fix the issue, but I just want to be sure before I push.
http://downloads.codefi.re/snowleopardjb/CFXE-ls970/testbuilds/full_ls970-cfxe-OPENMASTER-20131017.155310.zip
Thanks for your work!
Sent from my LG-LS970 using xda app-developers app
SnowLeopardJB said:
From what I can tell, that "fixed" data, but is still not quite correct. It is most likely just using a generic ril, and not the CDMA RIL that it is supposed to. I am going to do another test build real quick here, then hopefully push the fix before the next nightlies run.
EDIT:
Can someone test out this real quick? I am almost positive this should fix the issue, but I just want to be sure before I push.
http://downloads.codefi.re/snowleop...ull_ls970-cfxe-OPENMASTER-20131017.155310.zip
Click to expand...
Click to collapse
For me, phone kept force closing upon reboot wouldn't even let me continue with the setup process :/
Sent from my LG-LS970 using xda app-developers app
SnowLeopardJB said:
From what I can tell, that "fixed" data, but is still not quite correct. It is most likely just using a generic ril, and not the CDMA RIL that it is supposed to. I am going to do another test build real quick here, then hopefully push the fix before the next nightlies run.
EDIT:
Can someone test out this real quick? I am almost positive this should fix the issue, but I just want to be sure before I push.
http://downloads.codefi.re/snowleopardjb/CFXE-ls970/testbuilds/full_ls970-cfxe-OPENMASTER-20131017.155310.zip
Click to expand...
Click to collapse
Keep getting telephony force close immediately upon booting. I think it was this commit that broke it:
https://github.com/codefireXperimen...mmit/f3a34a05ce018779901ba03cf5b200f269b0fb5c
This commit seemed to fix everything:
https://github.com/codefireXperimen...mmit/19fe84d354927b0552cde51f5e8db2c4ccf1b3ff
tonyp23 said:
Keep getting telephony force close immediately upon booting. I think it was this commit that broke it:
https://github.com/codefireXperimen...mmit/f3a34a05ce018779901ba03cf5b200f269b0fb5c
This commit seemed to fix everything:
https://github.com/codefireXperimen...mmit/19fe84d354927b0552cde51f5e8db2c4ccf1b3ff
Click to expand...
Click to collapse
I just realized that I was comparing the wrong cm branch. Thanks for pointing that out.
Anyway, the next nightly (10/21) should have it fixed. Commit is here, for anyone interested.
https://github.com/codefireXperiment/device_lge_ls970/commit/fc0faba106e50589bfae13f7234fcf146a176cd4
SnowLeopardJB said:
I just realized that I was comparing the wrong cm branch. Thanks for pointing that out.
Anyway, the next nightly (10/21) should have it fixed. Commit is here, for anyone interested.
https://github.com/codefireXperiment/device_lge_ls970/commit/fc0faba106e50589bfae13f7234fcf146a176cd4
Click to expand...
Click to collapse
Cool, was going to just test with manual adjustment, but I'll sync and compile now to test it out. I'll report back.
so are you guys going to be maintaining the device tree?
hazedabeast said:
so are you guys going to be maintaining the device tree?
Click to expand...
Click to collapse
I will be. I am the official maintainer of the AT&T and Sprint LGOG for CodefireXperiment.
Got a Note 3 right after they came out.
Had an issue with the first one, not the least of which was the pervasive WiFi disconnect issue many of us have been seeing; in my case also had extreme battery drop all of a sudden - like 45% in an hour - not abnormal use.. So, swapped it about 20 days ago for another one.
Seeing the same WiFi connectivity issue I saw with the first one and then all of a sudden got a pop up :
"Prevention Information"
An application has been forced to stop for an unauthorized attempt to access system in your device. It may be safe to delete an application obtained from an unauthorized route. Check Now? (with a Do not show for 30 days check box; Cancel or Ok buttons)
If you click cancel pop up comes back after about 10 mins more or less; if you click Ok you get brought to a list of what you have downloaded to weed through whatever you've installed.
Full disclosure: This device is out of the box, not rooted; stock Rom. Only none play store apps installed were Adobe Flash and Amazon App store. I use WiFi extensively for WiFi calling at my office, since there isn't a carrier on the planet can get me a decent signal. I live and die behind WiFi calling it's why I went T-Mobile to start with.
* So I proceed to scan hell out of this, using Lookout, Sophos and MalwareBytes can't find anything..
* Ok so I uninstall everything I've been experimenting with thinking maybe the mix is a problem. Doesn't solve it
* So then I do a software Backup and restore - and go to put back the one app I need the most for my Hosted Exchange connectivity to work the best for my needs adding them back one at a time to see what's causing this . Of course I turn WiFi back on to connect to my network and signing into my Google Account Google Play takes off to restore all my stuff and do all updates for anything stock on the phone. (Phone Vendors WAKE UP; Stop making the default Google Play behavior Up Date Automatically when on WiFi, let the user decide before taking off to do what you think is best) And - The pop up is back just as I get the 1 app I need on the phone. (email support for the app saying it's them - MANY APOLOGIES to Nitro Desk, it's not them.
* Very long story and many soft and hard resets, to try control the behavior, later; including running 2 miles up the road to control Google Play auto update on WiFi, but, only be on the T-Mobile network for the initial startup....
With nothing but a minimal start-up and No Apps installed other than what Google Play demanded to be able to work at all out of the box when signing in; once I got the phone back to the office and started WiFi for my network - Blammo ! the pop up is back.
This "error" or warning message is from the base Android/Samsung/T-Mobile deployment configuration for a Note 3 when starting WiFi at all.
So, I happen to be near the T-Mobile store I bought this at and go in to tell them about this and the guys there running a Note 3 say they all get the same issue.
My conclusion is that this is a miss-configuration of software and/or permissions at the core OS level when starting WiFi; likely contributing or the primary cause of WiFi connectivity issues on this device; as reported in this and other forums.
I have screenies of this condition and would love to pass this to T-Mobile and Samsung engineering, but, unlikely I can get at them to do so; hopefully they are already aware of this and working on a fix.
The other interesting thing I noticed is that when doing a hard reset: during the start of recovery mode I get an "error" then no command message under the little droid as it settles down to the menu.
Also at the end of the recovery mode process for wipe data/factory reset I get an "error" message in red as well.
Again, seems to me there's a serious flaw in their Core programming setting up proper permissions for the base WiFi stack to start without triggering a security violation.
It doesn't matter if you connect to an AP or not. Just starting WiFi the pop up will come up in 60 - 90 seconds.
This is consistently reproducible.
T-Mobile is sending me another phone; but, I believe it will behave the same way - hope not, we'll see.
cef1000
You really need to SEARCH before posting. There are many threads about Prevention Information and it has nothing to do with WiFi.
krelvinaz said:
You really need to SEARCH before posting. There are many threads about Prevention Information and it has nothing to do with WiFi.
Click to expand...
Click to collapse
That may be, but, in this case it is 100% reproducible under these conditions and happens if WiFi is turned on at all before any updates and before any additional apps are installed, other than the ones the Play store insists on bringing in to work properly once initially signing in, happens to me in this very limited and controlled startup of the device and only when starting WiFi and no other time in that controlled condition; before any updates or Play Store apps are installed.
It also happens after they are; so it seemed,to me at least, to have value because of the controlled diagnostic startup; since the condition is 100% reproducible using these steps and under these limited initial startup conditions, at least on the device I have in my hands at the moment.
A replacement should be here sometime today and will attempt to reproduce it on the replacement; T-Mobile tech support seems to think it will behave the same way as well; FWIW to anyone.
Thanks so much for the input and advice; duly noted.
Best regards,
cef1000
Knock yourself out....
You might try doing a simple Google Search for samsung "Prevention Information" and see just how many threads there are about this issue. It is not just the Note 3 but a number of other Samsung devices as well.
Actually it has everything to do with wifi. Knox is thinking wifi is trying to collect information from your device as if it is a type of virus. Samsung is fully aware of the issue & there is an update coming based around that specific issue.
Sent from my SM-N900T using XDA Premium 4 mobile app
sIpInWiT mYdRoId said:
Actually it has everything to do with wifi. Knox is thinking wifi is trying to collect information from your device as if it is a type of virus. Samsung is fully aware of the issue & there is an update coming based around that specific issue.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1 Thank you slpn...
I'm glad to hear there's some fix in the works. Do you have a link handy for that? It's clear that the shipped Knox/SEAndroid configuration shipped on this device (and perhaps other Samsung models) really wasn't tuned very well before release.
OP, if you want to know more about this read some of the other threads here about Knox - the Everything Knox thread in this forum is pretty good IIRC, and the Samsung Knox whitepaper is an interesting read too (here). Basically, Samsung rolled their own solution for bring-your-own-device enterprise users, which is based in part on the SELinux extensions to Android (SEAndroid) along with some lower-level supervisory logic that's probably somewhere in the boot loader / modem / etc. [speculation] and some degree of hardware support such as the "knox warranty void" flag.
Unfortunately they developed this alongside/outside the reference implementation of SEAndroid, wrote their own APIs for interaction, etc. and don't seem to have done it terribly well. I'm tempted to ask that Samsung provide some way to actually control it, or provide a signed development FW that won't trip the hardware flag, as it really is an intrusion for non-enterprise customers. >.<
sIpInWiT mYdRoId said:
Actually it has everything to do with wifi. Knox is thinking wifi is trying to collect information from your device as if it is a type of virus. Samsung is fully aware of the issue & there is an update coming based around that specific issue.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Actually I've gotten the notification without wifi although it usually happens when I do turn it on.
Totally agree though that a simple search would have saved a HELLS of a lot of trouble. Smh
Yes it's a bug but it's not really that big of an issue. I can almost guarantee it will be fixed soon with some kind of minor update.
Well I have two other issues besides the "prevention information" for some reason my note 3 keeps giving me a unstable wifi connection when the connection to the wifi is good for example on my note 2 is perfect mo issues no lags on the note 3 however I get that unstable wifi connection, and for my second issue I get a damn google+ app crash every time im on the phone or any app . This note 3 has become a nightmare with bugs . I was wondering if anyone else has the same issues besides the prevention information ???
Sent from my SM-N900T using xda premium
westkhalifa13 said:
Well I have two other issues besides the "prevention information" for some reason my note 3 keeps giving me a unstable wifi connection when the connection to the wifi is good for example on my note 2 is perfect mo issues no lags on the note 3 however I get that unstable wifi connection, and for my second issue I get a damn google+ app crash every time im on the phone or any app . This note 3 has become a nightmare with bugs . I was wondering if anyone else has the same issues besides the prevention information ???
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
I think I had the unstable connection problem a long time ago. I may have made my phone "forget" my wifi network and obviously have connected to it since and have not have that problem. So it's possible simply "forgetting" the network, scanning, and then connecting to it again could fix it?
How often do you use Google+? Is it possible that if you hardly use it you could just sign out of the app and then it won't search for your location so much? I see the new G+ update says something about refreshing friends location more often or something, could be tied in to that?
I dont use google+ at all. It updated on its own and it started crashing since. I just turnt off all my auto updates and I uninstalled the last google+ update lets see if that does the trick .
Sent from my SM-N900T using xda premium
westkhalifa13 said:
I dont use google+ at all. It updated on its own and it started crashing since. I just turnt off all my auto updates and I uninstalled the last google+ update lets see if that does the trick .
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
You can take it how you'd like cause i know how some are when they hear about an update, not saying your one of these people who flame on the other person who try to provide helpful info about an update, but that is also being included in the update i spoke of a few posts above.
What is going on is your phone is scanning your signal & even if you have a full WiFi signal, instead of just leaving you on WiFi like you'd like, it boots you off of WiFi saying internet is unstable if it considers the data connection as being a stronger signal. its a real ignorant move and overlook they made when adding this function. if on WiFi they should let you choose if you want to change connections,or better yet not even bother you to choose between the 2 cause it will interfere with what your doing at that time while you have to choose which connection you want to use. But this is involved with the update we are getting. Verizon already got an update that had to do with WiFi issues with this being one of the issues it fixed.
If you haven't been told yet though, go in to WiFi advanced settings in your WiFi connections menu, and turn off auto connect & always scanning, then dial *#0011#, click your bottom left button on the white part of the phone you'd usually use to bring up the settings menu option, choose WiFi, turn off WiFi power save mode, WiFi power save mode being tuned off cause your battery to drain about 25% faster but this is proven to work. But after a day or 2 always leave WiFi auto connect off & always scanning off, but you can then dial *#0011# & turn WiFi power save mode back on & it's almost as if those functions done together trains your phone to not boot you off WiFi anymore. This seriously works and definitely helps many i have offered the information to. Me and about 3 others figured out how to do this in a thread about 2wks after the phone was released because the wifi booting us off was killing us. People had told us to just turn off auto connect but that would just stop the pop up, but you'd still be getting booted off from WiFi but just wouldn't be told by the pop up yet you'd know because the page you'd be loading on the browser would just stop loading, or say something your using like Facebook would lose signal & tell you an error occurred. Hope this large posts helps you if you read it or anyone else who stumbles upon it.
westkhalifa13 said:
I dont use google+ at all. It updated on its own and it started crashing since. I just turnt off all my auto updates and I uninstalled the last google+ update lets see if that does the trick .
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
You have to actually go into the Google+ app to see if you are signed in, unfortunately it will automatically sign you in if you are not already. So even if you accidentally open G+ or some other program or app causes it to open, you still need to actually sign out of it. Hopefully uninstalling the updates does the trick.
Auto connect in wifi advance settings is the network switch box right ???
Sent from my SM-N900T using xda premium
westkhalifa13 said:
Auto connect in wifi advance settings is the network switch box right ???
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Yes thats it.
Sent from my SM-N900T using XDA Premium 4 mobile app
i had a wifi problem with my Note 2 before and now it is better with my Note 3.