Develop Bugs

Slow wi-fi speeds?

So I recently got CM6 on my Touch Pro and right now I'm using the market and it's downloading at an appallingly slow rate D: It's roughly 10KB/s or perhaps slower. Did I do anything wrong here? :<

Dannysaurus said:
So I recently got CM6 on my Touch Pro and right now I'm using the market and it's downloading at an appallingly slow rate D: It's roughly 10KB/s or perhaps slower. Did I do anything wrong here? :<
Click to expand...
Click to collapse
Nope. Wifi just sucks. It's always one of the reasons why Android always locks up for me, actually.

*crai*
So, wifi on Android just sucks? :< It's better on WinMo though, which I don't really get.
Since wifi is painfully slow on Android, how else would I get applications on it? A much faster method xD

Wifi seems fine for me... Faster than 3g, which is all I really ask for when using it...

I take it you're using a TP too >.< Whaiii *cries*

Dannysaurus said:
I take it you're using a TP too >.< Whaiii *cries*
Click to expand...
Click to collapse
I used to. RAPH800, wifi was definitely faster than 3g. I'm on a RHOD now tho.

arrrghhh said:
Wifi seems fine for me... Faster than 3g, which is all I really ask for when using it...
Click to expand...
Click to collapse
Maybe because you're not using a RAPH. A search in the thread would show that other people have the problem, and not just me lol...

i haven't noticed any wifi issues with the builds. always faster than 3g for me.

gm112 said:
Maybe because you're not using a RAPH. A search in the thread would show that other people have the problem, and not just me lol...
Click to expand...
Click to collapse
I said I used a RAPH previously... I've only had the RHOD for about a month now, had a RAPH for 2 years before that. So I'm not just shooting off the hip assuming... I ran XDAndroid on my RAPH for a loooooong time.

Well uhm, I'm using a Touch Pro but that's as far as I know. Perhaps I used a wrong startup? What would I use instead?

nothing there will make a difference.
do a test. using the regular browser (not opera or anything) goto mobilespeedtest.com or speedtest.net and do a test and see what it tells you. would help if you also have a computer on the same router to test against.
you can test 3g and wifi and your computer to see the differences in speed.

arrrghhh said:
I said I used a RAPH previously... I've only had the RHOD for about a month now, had a RAPH for 2 years before that. So I'm not just shooting off the hip assuming... I ran XDAndroid on my RAPH for a loooooong time.
Click to expand...
Click to collapse
And so did I. I could make a video demonstrating how unstable the wifi/radio is, lol. I've had far too frequent crashes for someone to tell me that it's "stable" .
EDIT: Here's some other people reporting the problem.
I2essurected said:
I have had the same issue multiple times. I find it happens more when I am travelling over a distance and the radio has to find new towers to connect to all the time.
Battery Drain on new kernel is great for me too, just wish the mic in-call worked, at the moment I am not using Android because of it :-(
I2es
RAPH100/Tocuh Pro T7272
Click to expand...
Click to collapse
Annndd.. there's probably a good chance this will get ignored because "it works for me".

Perhaps wifi is unstable on the 110, but I seriously doubt it. Besides, that dude is talking about the radio finding new towers, what does that have to do with wifi?
I find the radio is unstable as well. I actually thought it was just a CDMA thing. I thought we were talking about slow wifi speeds tho... Now I'm just confused.

gm112 said:
And so did I. I could make a video demonstrating how unstable the wifi/radio is, lol. I've had far too frequent crashes for someone to tell me that it's "stable" .
EDIT: Here's some other people reporting the problem.
Annndd.. there's probably a good chance this will get ignored because "it works for me".
Click to expand...
Click to collapse
i think you are starting to get confused here. are we still talking about wifi or have we moved on to 3g now?
honestly almost nothing here is truely stable. our ril still needs alot of work and that is what talks with the towers.
wifi however shouldn't have any real issues. wifi is working on every model of the supported devices and as you can see, this is the first thread regarding wifi issues.
the wifi is supported by the kernel. kernel changes shouldn't make a difference as the wifi drivers haven't changed. however the devs are trying to get hopspot support working which may impact wifi. if you are having issues, report a bug.

hamagc said:
i think you are starting to get confused here. are we still talking about wifi or have we moved on to 3g now?
honestly almost nothing here is truely stable. our ril still needs alot of work and that is what talks with the towers.
wifi however shouldn't have any real issues. wifi is working on every model of the supported devices and as you can see, this is the first thread regarding wifi issues.
the wifi is supported by the kernel. kernel changes shouldn't make a difference as the wifi drivers haven't changed. however the devs are trying to get hopspot support working which may impact wifi. if you are having issues, report a bug.
Click to expand...
Click to collapse
It's both wifi and 3G that's unstable for me. Anytime I use the internet through either method, the phone has weird issues. It's easily reproduced.

gm112 said:
It's both wifi and 3G that's unstable for me. Anytime I use the internet through either method, the phone has weird issues. It's easily reproduced.
Click to expand...
Click to collapse
what type of issues? system rebooting into android? rebooting into winmo? force closes? radio crashes?
i do not want to blame the device but my g/f who just gave me her diamond had alot of issues running xdandoird. come to find out her phone had issues in general and had nothing to do with xdandroid.
this may or may not be a similar issue to your. that will be for you to let us know.
if you have the time, rename your data.img to data.img.bak and launch haret.exe. it will build a new data.img and from there run the same basic tasks that cause issues for you now. since our build is still in the "building it" stage, some apps will cause issues without you noticing. the only real way to tell if an issue is the system or if it is an installed app is to test it with a clean system to see how things come out. this doesn't always solve the problem and if it does not let us know.
your said you have a raph110, Stinebd who is one of the main developers on this project has a raph110 so if there are any real issues with xdandroid and that device, it will be known. as such i have not heard from him with any real stability issues using the radio or the wifi (i believe he no longer has service on the device however).
if your one of the luck cdma users there are more issues as there are no real devs working on the cdma side of things for our devices. there are alot of radio stability issues as the ril is not complete and is a hacked hack version of the gsm radio made to work on the cdma network.
hope this makes sense.

Sowwy D: Was moving and getting new ISP's. Horrible wait :<
Anywho, for all those going "It works for me" Yeah well... It doesn't. I'm getting 14mbps wireless, but on the phone I'm getting 84kbps which is... Odd. I'm currently using the SuperFroyo port. I've had experience with the xdandroid version and it's wi-fi was actually pretty good compared to this. Kernels perhaps?

[Q] Another wifi bug thread, I've tried everything possible.

Hi!
I know there are plenty of threads about the wifi on this phone, I've read every one of them, posted in many places and have had no good outcome.
Here is my (lengthy) story.
Had annoying wifi bugs on stock 4.1.2, seemingly general lack of interest from the phone in connecting to wifi, but would generally connect after a reboot of both modem+phone+ disabling PSM (even then, not always )
6 months on stock go by, thought flashing a custom rom would fix everything and all would be well again, so I flashed PA.
An even more annoying bug showed up,
Turn wifi on > doesn't automatically connect, so I manually go to the wifi settings page and try connecting.
Before trying to connect - Full signal.
While trying to connect - Goes down to one bar while connecting > fails > then goes back to full signal.
Does occasionally connect, but it's rare. Rebooting both phone and the modem does nothing at all, seems to have a mood of it's own.
It's not just my wifi, but wifi at college too, other devices connect to the same access point just fine.
What would fix this? Will pretty much try most things now,I tried flashing NEAK too.
I don't have a data plan either, so my phone is basically useless without wifi, I've resigned to using my laptop all the time.
Thank you for reading this so far, I'd be thankful for ANY advice.
TL;DR :- Annoying wfi bug, tried every 'solution' I've heard of, nothing worked, never buying a Samsung again :crying:
(Attached images of the phenomenon)
UPDATE:- Just like stock, it will only connect if I am a foot away from the router, irrespective of how much signal I have. Even if I have a full signal elsewhere, it won't connect

dude u r running AOSP :silly::silly:
try TW Rom and see if the problem exists

yahyoh said:
dude u r running AOSP :silly::silly: try TW Rom and see if the problem exists
Click to expand...
Click to collapse
We meet again!
Like mentioned in the post, the only reason I flashed an aosp based ROM was in the desperate hope it'd rid the phone of its WiFi problem.
Thought a custom ROM would do what Samsung refuses to do.
Hope someone has a valid solution for this.
Sent from my Galaxy Note II using Tapatalk 2

Anyone?
I forgot I already had the range issue for quite a while, even on stock.
I had tried everything, including static IP, wps, and whatever else was stated to work.
Does anyone know of a working solution to this? Is this a hardware/software issue?
Sent from my Galaxy Note II using Tapatalk 2

Android 4.3 WiFi Issue

Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!

I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app

Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.

geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?

http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2

What I really wanto to know if this issue is posted in the official google bugs tracker

Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4

stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.

I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.

FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app

Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.

FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app

FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4

I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.

I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..

memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.

stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?

stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4

memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?

stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844

Verizon Galaxy Nexus wireless tether on CyanogenMod 10.1.2

Asked in the official thread on the development forums, but so far no replies after several days. I am wanting to get some form of tether working on this ROM, but so far nothing works. From trying the built-in tethering function to using Android-Wifi-Tether, nothing is working. I know there are some tether issues with JB ROMs on this phone, but usually they are easy to overcome with a patch from the ROM devs themselves.
Has anyone gotten tether to work on this specific ROM, and how did you go about doing it.
Thanks

NeoandGeo said:
Asked in the official thread on the development forums, but so far no replies after several days. I am wanting to get some form of tether working on this ROM, but so far nothing works. From trying the built-in tethering function to using Android-Wifi-Tether, nothing is working. I know there are some tether issues with JB ROMs on this phone, but usually they are easy to overcome with a patch from the ROM devs themselves.
Has anyone gotten tether to work on this specific ROM, and how did you go about doing it.
Thanks
Click to expand...
Click to collapse
I used to use CM 10.1. I dont think I ever went to 10.1.2 but I dont think it makes a difference. I just remember going to 10.2. But every CM ROM I was on, the native tethering worked fine for me. I'm on Verizon though. I dont know if that makes a difference either.
EDIT: Saw you were on Verizon. It should work unless I'm forgetting something

So far I have tried CM 10.2 nightly 9/15 and 9/17 and the 10.1.2 stable release and the native tethering doesn't work on any of them. I can connect using it, but the connection is limited and no data is transferred at all. I was using a custom ROM from MWalt and I had to use his native tethering patch to get it to work on JB roms.

NeoandGeo said:
So far I have tried CM 10.2 nightly 9/15 and 9/17 and the 10.1.2 stable release and the native tethering doesn't work on any of them. I can connect using it, but the connection is limited and no data is transferred at all. I was using a custom ROM from MWalt and I had to use his native tethering patch to get it to work on JB roms.
Click to expand...
Click to collapse
I dont know whats going on with your phone then. I've never had an issue with tethering and I've never used a patch. What are you trying to tether to? Some devices may have issues with the type of signal the Galaxy Nexus puts out. For example, there is a thread around here about tethering issues with the Xbox.

Have tried my laptop, a tablet and a 3DS. None of them work. I can see the network and connect, but no data is ever transferred. On ICS roms I didn't have to do anything to get tether to work right out of the box. But starting with JB, I have had to use either patches or workarounds to get the native tethering to work on any ROM I try.

NeoandGeo said:
Have tried my laptop, a tablet and a 3DS. None of them work. I can see the network and connect, but no data is ever transferred. On ICS roms I didn't have to do anything to get tether to work right out of the box. But starting with JB, I have had to use either patches or workarounds to get the native tethering to work on any ROM I try.
Click to expand...
Click to collapse
Sorry man. I have no idea whats wrong. The only thing I can recommend is maybe try flashing the stock image and see if it fixes anything. I know thats not what people want to hear. But unless someone else says they are having the same problem, it would seem to be only happening with your device. Another possibility, I guess, could be your radios. Did you flash any other radios on your device?

I am using this radio from 3/5. What radio are you using, and is it safe to back down to a prior one?

NeoandGeo said:
I am using this radio from 3/5. What radio are you using, and is it safe to back down to a prior one?
Click to expand...
Click to collapse
I'm pretty sure those are the ones I am using too. I wouldn't revert to older ones until someone with more experience says its ok. I dont want to say yes and have your phone break. I dont know what to tel you though. If you have the time, I'd say just start from scratch and see if it fixes it.

Start fresh as in going back to stock 4.2.2 or whatever the latest is? I tried that between flashing the different CM versions but with JB roms I have to apply a patch before native tethering works for some reason. I will try different radios when someone confirms you can back down to an earlier set without issue.

NeoandGeo said:
Start fresh as in going back to stock 4.2.2 or whatever the latest is? I tried that between flashing the different CM versions but with JB roms I have to apply a patch before native tethering works for some reason. I will try different radios when someone confirms you can back down to an earlier set without issue.
Click to expand...
Click to collapse
Alright. Sorry I couldnt be more help.

Your help is appreciated. At least I know that I can tether, just depends on if I want to move to certain ROMs or not. Hopefully I can get CM to tether as its one of the best running ROMs I have used for this phone.

The only time I had an issue tethering on CM is when I ran AK kernel. Stock cm kernel and Franco kernel always worked fine however. I'm not sure what the difference was....
Sent from my Galaxy Nexus using xda app-developers app

jsgraphicart said:
I used to use CM 10.1. I dont think I ever went to 10.1.2 but I dont think it makes a difference. I just remember going to 10.2. But every CM ROM I was on, the native tethering worked fine for me. I'm on Verizon though. I dont know if that makes a difference either.
EDIT: Saw you were on Verizon. It should work unless I'm forgetting something
Click to expand...
Click to collapse
same here

Wifi only works properly on Sense ROMs

I have the Verizon HTC One M8 with s-off and rooted. I really want to use an aosp ROM, but I have wifi problems on all of them. I know that other people were also having issues with wifi disconnecting, but that is not my problem.
The wifi range is terrible. I have to be close to the wireless router to use the internet. When I am close the speed is perfect, but as soon as I move a few rooms away it cannot download anything. The phone still shows it is connected to the wifi with full bars but its impossible to even load a webpage. When I use my iPad from the same distance I can play HD video no problem.
The strange thing is the issue does not exist when I am using a Sense based ROM (stock, ARHD). I apologize if this is a common issue that I am unaware of but any help would be appreciated!

Its been a very well known and reported issue since the release of any AOSP based ROMs. Its not really strange that it works on Sense ROMs considering Sense ROMs are specifically made for this device. AOSP based ROMs have to be made to work on this device. You'll just have to be patient and wait for it to be fixed. Other than that, nothing can be done at the moment.

Dang, I thought for most people the issue was with wifi dcing! Oh well, next time I will make sure to look into it more before making a post. Also, where is a good place to look for updates pertaining to issues like this?
Thanks!

For updates you can look in a few places.
http://www.cmxlog.com/11/m8/
http://review.cyanogenmod.org/#/q/status:merged,n,z
https://github.com/CyanogenMod