As the title says, my tilapia's mobile data (3G/HSPA) connection occasionally stops transferring data while in the middle of a large download, whether it's a simple file downloaded from a browser, a Play Store application or a YouTube video. Turning airplane mode on and off always fixes it. (Clarification: the signal doesn't drop, just the data. The signal indicator stays blue for a while after the connection drops, then turns gray.)
It doesn't happen on all ROMs. It happens on Purity 5.5.0, AOSP 4.3 (tested with Androguide.fr's ROM), CyanogenMod's August 7th nightly, IceColdJelly (July 23rd), RootBox (August 5th, unofficial build) and others I'm forgetting, but Paranoid Android is immune (3.67 and 68 tested). I haven't updated my radio or bootloader to the 4.3 ones.
I haven't tried using alternative kernels yet, so it might be that. (Edit: it's probably not the kernel, just flashed M-kernel mr1 and the problem is still there.) In the mean time, if someone has any ideas about what's going on...
Stock?
AndyM3 said:
As the title says, my tilapia's mobile data (3G/HSPA) connection occasionally stops transferring data while in the middle of a large download, whether it's a simple file downloaded from a browser, a Play Store application or a YouTube video. Turning airplane mode on and off always fixes it. (Clarification: the signal doesn't drop, just the data. The signal indicator stays blue for a while after the connection drops, then turns gray.)
It doesn't happen on all ROMs. It happens on Purity 5.5.0, AOSP 4.3 (tested with Androguide.fr's ROM), CyanogenMod's August 7th nightly, IceColdJelly (July 23rd), RootBox (August 5th, unofficial build) and others I'm forgetting, but Paranoid Android is immune (3.67 and 68 tested). I haven't updated my radio or bootloader to the 4.3 ones.
I haven't tried using alternative kernels yet, so it might be that. (Edit: it's probably not the kernel, just flashed M-kernel mr1 and the problem is still there.) In the mean time, if someone has any ideas about what's going on...
Click to expand...
Click to collapse
Well i know its a PIA but if i were you i would try going back to stock and see if you still experience the same issues! It could be ROM based issue your seeing on certain roms. Also one kernel that works PERFECTLY wont always work for another person with the same device. Also have a look at what radio is in use for your device. I own the WiFi version. But just like your smartphones id assume the tilapia has a radio/modem that gets flashed during ROM installs.
First thing is see if STOCK does it. IF it does id assume a failing 3G radio in your unit sadly!
Related
A test/stock anykernel for CM6 inc is up on rom manager under the Koush section. Please test it out and let me know how it compares. I am working on tracking down some instability issues.
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Used it for a day...
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
sucker4pa1n said:
I'd have to say one of the biggest downfalls was that it didn't have most features within the kernel enabled. I didn't notice any immediate problems even with the stock kernel, unless what I ran into (described below) might be involved.
When trying to initially download the new kernel via ROM Manager, I was in a location where cell was -120 dBm (basically non-existent) but I had Wifi. Wifi always seemed to take forever to link up, unless I went into settings (then it'd find the AP immediately and connect). ROM Manager basically said it couldn't do anything, despite having Wifi. I don't know enough about the inner Android workings to know if that's unrelated or not.
With the new one I noticed mainly I had very few governors to work with. TBH I only spent a day with it because I couldn't stand how often I ended up having to charge it. I don't OC so that sort of thing has never been an issue - just UC
Edit -- I should mention I'm using 2.15.00.09.01 baseband and CyanogenMod-6-09202010-NIGHTLY-Inc build. Haven't tried newer dailies yet.
Click to expand...
Click to collapse
2.15.00.09 radio literally KILLED my battery. I went back to 2.15.00.07 and battery life is great again. FYI.
Everything is good for me with this kernel. No issues. Flashed it last night.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
At the moment, I'm using Miui but wanted to note that this is the only kernel which allows Pre-9 Wifi tether to work on Miui (in my hands, King's #1 and #2 AOSP kernels gave me errors with Wifi Tether). Thanks for providing this kernel, Koush. Will give it a try with CM and see how that goes.
I had a soft reboot last night with this new kernel while I was on facebook. 0 wifi used.
Radio 2.15.00.07
Not sure if it's the kernel or just the latest nightly, but I'm loosing my data connection quite often. Otherwise, its running great.
dnoyeb said:
Having issues with built in tethering says error. Pre 9 seems to work however after toggling wifi.
Anyone else?
Click to expand...
Click to collapse
My built in wifi tethering isn't working either....sad day. I was loving how fast my phone charged
New version, number. 11 is online, testing now.
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
mikeacela said:
I haven't had any problems with this kernel yet even on wifi. I have also noticed decent battery life.
Droid Incredible
S-off
.77 hboot
Latest radio
Ruby Rom
Click to expand...
Click to collapse
Funny, I'm running the test2 on Ruby as well. Been rock stable for 4hours. Practically a record for my phone on Ruby. Hope it makes it through the night.
Using the "test2" kernel.
Built in tethering works for me.
I'm running the 9/27 nightly.
No other issues so far.
P.S. I would love if internal memory was mounted properly in Windows.
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Another question would be, does anyone know if test kernel #1 or #2 is the test kernel in rom manager?
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
showing up as a 245-998mhz one with compcache optional... Not that I put much credence in quadrant scores, but I'm pulling over a 1300 on that. So plenty quick.
Also does anyone know if its undervolted?
Sent from my INCREDIBLE using Tapatalk
Ty07allstar said:
Does anyone know if this new kernel is underclocked?
Sent from my INCREDIBLE using Tapatalk
Click to expand...
Click to collapse
#2 is running at default clock.
So far looking good on test#2 for me (9.26 nightly). I just had a meeting in a location where the phone has frozen up nearly every time I was running CM 6.02 or any previous build and it worked fine. If I make it out to lunch, then back home later today without a freeze I think we may have a winner. Or at least I'll have a winner...
I grabbed the test kernel on friday night via the ROM manager, am I running the latest test, or is there a new one with the same name? In other words do I have to redo it to get the test #2 I am seeing comments about?
I am running test2 and my only issue is with wifi cutting out and erroring out when running things like streaming media in the background, but no reboots. Tt just cuts out the wifi, and resumes relatively well upon turning the screen back on. For some reason the screen being off sets off a timer that cuts out the wifi after a while. I've tested this with both Pandora and Slacker. No cut outs when running over 1x CDMA (3G doesn't work in my office) except when my signal becomes nonexistant.
I'm not sure if this is the same as the well known "Nexus One 3G problem". I'm running CyanogenMod 6. I have been having occasional trouble on my home carrier (WIND Mobile Canada) where every once in a while, even though the 3G or H icon appears, I can't access anything and when I try the ping test under Testing/Phone information it fails.
The only way I'm able to get the Internet back is to disable mobile data (via widget) and re-enable. Then it lasts again for a while.
I'm currently on vacation in the US and using a T-Mobile SIM. It seems this problem is even worse on their network. Sometimes I only get maybe 2-5 minutes of a 3G connection before it freezes out like this. I've been leaving it on EDGE just to keep it stable, but this is obviously not an ideal solution.
About two weeks ago I started trying nightly builds of CM6 as I was interested in the FM Radio, and I have noticed this issue much more since then. It might be related, but it could also be a coincidence, and I don't want to start messing around with multiple ROM flashes while on vacation if that's not the problem in the first place. Any ideas on what to do?
Thanks
Charles
its a bug with 2.2.1,my nexus does this too. it will get stuck with the data up arrow lit up when the data stops working,turning data off and back on fixes it. there is even a post in the google bug tracker about it. I know for sure it happens in both FRG83 and FRF91,but I'm not sure exactly when it started. 2.1 roms for the N1 don't do it,and my g1 doesnt on 1.0-2.1,but on froyo roms it does exactly the same thing as the nexus.
I hope someone (google or a dev) can fix this,because its really annoying. my g1 is back to donut because its faster,and I'm considering going back to a 2.1 rom on the N1. I've confirmed the issue on ChromaticDream (g1),CM Nightlies (I've tried 198,200,201,202,203,220),CM6.0.0,Enomther's TheOfficialNexus (10/11/10),and a few others.
I thought I was the only one who noticed this bug. Does it occur in the stock (non-rooted) versions of 2.2.1 as well?
Just an update, although I do periodically experience this on my home provider (WIND Mobile Canada), it turns out that T-Mobile is having 3G issues in Portland this exact week and everyone's experiencing it. So the fact that 3G is nearly unusable on my trip is TMo's fault and not Android's.
UPDATE: I downgraded my radio to the official froyo radio (4.0-something lol) and my timeout problems are no more so far....
I have the same problem but with since I'm using nightlies 215 the problem is gone (i'm using 508 radio)
but lately I'm using nightlies 221 and 223 and the problem is back
I settled on 204 for vacation because I didn't want to fiddle with the ROM 10 hours away from my desktop comp! Now that I'm home, keep this thread updated with which builds seem to have a stable 3G connection.
I just flashed 225 with 512 radio and I can say this build is stable, no more intermittent connection lost. 225 nightlies is fast as well
Good to know. I'm on the 5.08 radio; is there a significant difference with 5.12?
I flashed my device the other week with the nightly build of cm-10.2-2013-12-02 and it is fantastic. Not only does it get twice the battery life the thing is so much more responsive and fluid, however (yes there is a however), the WiFi does not always cooperate. It will show it is connected but the browser or anything that uses a connection will not receive anything. If I disable the WiFi then the phone uses its data with no issues at all. Of course there are limits to data use so the WiFi is much needed. Does anyone have a .zip of the 03,04,05,06 cm10.2 builds? Unfortunately now that cm11 is being rolled out the nightly releases of 10.2 are nowhere to be found. I was hoping hat maybe one of these later releases fixed the issue.
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. I successfully rooted my device and installed Team Canjica's CM10.2 ROM (4.3) from the thread on XDA Developers but the WiFi wasn't working. I then installed Maclaw's CM11 ROM (KitKat) because I thought that might solve the issue but it didn't. Here are the details:
Device scans for nearby wireless routers.
I type in the password for my home router.
Device saves router. "Saved, Secured" message displayed.
I tap on my home router in the list to connect.
Device says "Connecting" for a couple of seconds and then goes back to saying "Saved, Secured".
I browsed through the forums and some users suggested switching WiFi Frequency to Auto and turning off WiFi Optimisation but neither of those methods worked for me. The ROM was installed successfully and all other features are working properly so I don't think that is the issue. And my router settings are also alright since I am able to connect to it from my Nexus 7 (2013) properly. Can someone please provide me with a working solution for this issue? I will start receiving very high data usage bills soon because my data plan isn't unlimited. Thank you!
Is your ssid hidden (not broadcasted) by any chance? i had those troubles on hidden home network. Sometimes it worked after a while, sometimes it didn't. What helped me is to broadcast ssid for a moment, get connected with phone, remove broadcast (it will reboot router so phone will lose wifi for a moment). Then somehow it got connected normally
Sent from my SGS Adv. using xda-developers app.
idedItp from
I just checked my router settings and SSID Broadcast is enabled. I tried flashing OmniRom 4.3 thinking that this may be because of a problem with CyanogenMod but the problem still persists. Is there any additional kernel that I was supposed to install perhaps?
CyanogenMod 11 version ?
jeremymichaeldlima said:
I just checked my router settings and SSID Broadcast is enabled. I tried flashing OmniRom 4.3 thinking that this may be because of a problem with CyanogenMod but the problem still persists. Is there any additional kernel that I was supposed to install perhaps?
Click to expand...
Click to collapse
Which version CyanogenMod 11 are you using?
jeremymichaeldlima said:
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. !
Click to expand...
Click to collapse
Just a detail to those who have not upgraded to JB stock and think it is impossible to use it without problems:
All bugs and freezes in Stock JB currently are perfectly finished.
I use STOCK, only with modified kernel (cocore 8.2) without freezes or bugs in months of use.
Enjoy the developer's work (cocafe), because without it JB probably would be impossible in SGA. However we have JB 100% functional and bug-free.
About KK and WIFI bugs:
The only KK (or based) ROM that used without WIFI bugs was RR 20140313.
In fact, the only issue is incall vol. in my experience.
WiFi Direct, Camera -> Panorama is laggy , Screen Recorder not working Not Tested
I also noticed that the battery is worse durability.
But I went back to JB Stock -- personal preference.
ADR USR said:
Just a detail to those who have not upgraded to JB stock and think it is impossible to use it without problems:
All bugs and freezes in Stock JB currently are perfectly finished.
I use STOCK, only with modified kernel (cocore 8.2) without freezes or bugs in months of use.
Enjoy the developer's work (cocafe), because without it JB probably would be impossible in SGA. However we have JB 100% functional and bug-free.
About KK and WIFI bugs:
The only KK (or based) ROM that used without WIFI bugs was RR 20140313.
In fact, the only issue is incall vol. in my experience.
WiFi Direct, Camera -> Panorama is laggy , Screen Recorder not working Not Tested
I also noticed that the battery is worse durability.
But I went back to JB Stock -- personal preference.
Click to expand...
Click to collapse
Actually I did try that method. Flashed Samsung's latest stock firmware I9070XXLQL (ITV) and then rooted and installed CoCore. To be honest overall performance was much better and UI smoothness was improved. But after a couple of days of regular usage with just a few basic applications such as a note taker, train arrival time, WhatsApp etc. the device started freezing up a couple of times a day again. I admit it worked much better than before but freezes and hangs were still quite frequent. Running OmniROM 4.3 now with no issues so far except for dialer FC, laggy panorama and non functional WiFi hotspot.
jeremymichaeldlima said:
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. I successfully rooted my device and installed Team Canjica's CM10.2 ROM (4.3) from the thread on XDA Developers but the WiFi wasn't working. I then installed Maclaw's CM11 ROM (KitKat) because I thought that might solve the issue but it didn't. Here are the details:
Device scans for nearby wireless routers.
I type in the password for my home router.
Device saves router. "Saved, Secured" message displayed.
I tap on my home router in the list to connect.
Device says "Connecting" for a couple of seconds and then goes back to saying "Saved, Secured".
I browsed through the forums and some users suggested switching WiFi Frequency to Auto and turning off WiFi Optimisation but neither of those methods worked for me. The ROM was installed successfully and all other features are working properly so I don't think that is the issue. And my router settings are also alright since I am able to connect to it from my Nexus 7 (2013) properly. Can someone please provide me with a working solution for this issue? I will start receiving very high data usage bills soon because my data plan isn't unlimited. Thank you!
Click to expand...
Click to collapse
This means probably you have typed wrong password. Also check that in keyboard it capitalise first letter automatically. forget the network and connect again
WIFI not working with cm-11-20140521-UNOFFICIAL-janice and cm11.0_janice.nova.201406
Same wifi problem with cm-11-20140521-UNOFFICIAL-janice and cm11.0_janice.nova.20140601. Wifi not connecting even after giving the right password (used to work correctly with jb4.1.2 and still works with desktop) only showing saving and connecting wifi. Then the wifi connection is shown to be saved. If wifi does not work with cyanogenmod11, then what's the use of upgrading?
Is wifi is not working in any custom kitkat Rom?
Please suggest a solution.
Try couple times to connect. I remember sometimes I had to reconnect 2-3 times before it gets connection. And the problem with kernel was about WIFI not turning on at all, it was not even search SSIDs.
Hello All,
Just got a nexus 6 and went ahead and installed a custom rom (Pure Nexus).
Not sure if its a ROM issue or not (Trying a different rom shortly), but my wifi is terribly slow. I put it next to my amazon fire tablet and ran a speed test multiple times.
Amazon - Avg is 15-20
Nexus is 5-7
I have read some forums that says changing the band helps or forgetting the network and readding but no luck.
Anyone else have any tips before I have to send it back for a new one?
How old is your router?
Strephon Alkhalikoi said:
How old is your router?
Click to expand...
Click to collapse
Less than a year. ATT UVerse provided router.
No problems here, I did a 135 down and 50 up on Comcast router
Looks like something with the Rom. I put Chroma on it and now get around 20 down. I do not think its app related as I just restored all using TB.
Going to clean flash pure and try again.
It's not Pure Nexus, but something else. I'm getting 160 down, 12 up (802.11ac) on Pure Nexus. Have you updated your device's baseband to the latest?
Stock ROM, 802.11n, reaching ISP cap of 60/10 on web speed tests.
Strephon Alkhalikoi said:
It's not Pure Nexus, but something else. I'm getting 160 down, 12 up (802.11ac) on Pure Nexus. Have you updated your device's baseband to the latest?
Click to expand...
Click to collapse
Found out it was a rogue app that caused it. Thanks for your responses. Can you point me to the latest baseband? I saw the Modem Collection thread here but the latest looks to be for the M preview back on 7/10?
Go to Google's firmware page and download the latest firmware package. Extract the files inside. I believe there will be an additional archive in the firmware package that you can extract that will contain the radio image.
I was having slow WiFi issues too. I updated the firmware on my router and switched the channel and now it flies.
That's not so easy to do when the entire 2.4GHz band is congested with connections, as it is in my area. Simply changing the channel didn't work for me, and I had to get new hardware that supported 5GHz. The gamers and video watchers in the house all appreciated it.
Other phone is same?
my problem previously was the same..i tried it with stock and aosp based roms, then i went to asked my sister to call our isp.. and the technician was able to verify the problems.. it was our internet cable.. they replaced it and it worked back to normal..
I had a similar problem, but only with the 2.4Ghz band, I live in an apartment complex and in Los Angeles so it's even worse. Luckily nobody uses the 5Ghz band so that works fine for me.
Update but found out that the issue is that my wifi slows down when my BT is on. Does not have to be connected, just have to be on...
Another Update is that I found out the combo is...
Wifi Connected + BT on (Does not have to be connected) + RetailMeNot App
I froze RTMN and now there is no slowness.
So the app is the culprit, not the combination of bluetooth and WiFi. Good thing you got it sorted.