I'm using a Samsung Galaxy S II GT-I9100, ROM: Rootbox JB v3.2, Kernel: 3.0.15-CM-g39df795 [email protected]
I can't work out at which point it happened, but at one point of flashing JellyBean ROMs onto my phone (currently RootBox) my Wifi and USB tethering stopped working properly.
When I connect to either, I get local-only. I can ping the phone and get connections back and forth between any laptop and the phone. But I cannot get any connection to the internet. The laptops simply cannot reach the gateway.
I've tried wiping and reinstalling the ROM clean, but that also made no difference. I can flash back to ICS if needed but I think I had teathering working on an old version of RootBox.
I don't think it's the ROM doing it however as I tried other ROMs like XTreme ROM and a Cyanogen Mod ROM and they also didn't work with tethering.
Does anyone know what I can do to fix this or find the cause of the issue?
**It appears that is is being impacted by the ROM. When I clean install Cyanogenmod 9 on my phone, tethering works. But when I go back to RootBox (CM10 based rom), it stops working. I'll repost over there.
Related
Hey everyone,
I just updated to the newest MIUI build and its amazing. The only problem I am running into is that tethering does not work for me anymore. I tried the built in features in MIUI, Wireless Tether, and Barnacle WiFi Tether and none of them worked. The guide i followed went like this if that helps (because I came from stock):
1. Flash CWM 3.0x
2. Flash ROM/Kernal/GAPPS
I never rooted the phone if that matters? Either way, im on the ROM with no issues but that. Any help is appreciated!
For wireless tether, go to the settings, and change the Device-Profile to Google NexusOne. Hope it will work for you.
Actually its worse than I thought, I cannot turn on WiFi, its broken? weird..
Its MIUI 1.7.29 FascinateMTD.
Maybe broken in that version?
Fixed: It was the custom kernal. Re-flashed the ROM and WiFi and tether work.
I have just flashed cm7 (stable) onto my phone (was using liteningrom before)
It all works fine except wifi / 3g. I cannot seem to download apps without 4/5 reboots and messing around with settings. Is this a common issue? could not see anyone with this issue for this build.
I was also thinking the change of rom may be the culprit so are there any settings in clockwork recovery that I should have done or do I need to hook phone up to kies to update the KE thing?
Sorry, I am still pretty new to SGS2 custom roms.
My university has a secure Wifi network which can only be accessed by an certain app (Xpress Connect). I guess the app downloads and installs the needed certificates. However I cannot connect to the wifi via that app, nor on any other way.
I tried it under 2.3.6 KK5 and 2.3.6 KLA and a ICS ROM.
The interesting thing is, it perfectly works with CM9.
Does anyone know what the problem could be? Is it because it does not work on gingerbread? (I don't believe that). Is it because I used an unofficial custom ROM?
Or is it because Samsung and TouchWiz screw it up? I mean it works under aosp (CM9).
So what do you guys think? I do not desperately look for a work-around, since I am fine with CM9, but I want to hear you ideas about where the problem is.
Hey, I searched but didn't really find the answer, heres the situation:
Whenever I run CM10 based roms I have two reoccuring issues: ( don't have these issues on Sense Roms )
1. Wifi: It will show wifi devices but we I connect it just says "Saved" not connected and isn't allowing me to use Wifi
2. ASOP Keyboard, I get a Android Keyboard has stopped working message. Tried clearing cache etc still does it ( this one is not as big as I use swiftkey3 anyway )
Currently running JellyBam latest nightly with Komodo Kernel, S-Off, and GAPPS 20121130
thatenglishguy said:
Hey, I searched but didn't really find the answer, heres the situation:
Whenever I run CM10 based roms I have two reoccuring issues: ( don't have these issues on Sense Roms )
1. Wifi: It will show wifi devices but we I connect it just says "Saved" not connected and isn't allowing me to use Wifi
2. ASOP Keyboard, I get a Android Keyboard has stopped working message. Tried clearing cache etc still does it ( this one is not as big as I use swiftkey3 anyway )
Currently running JellyBam latest nightly with Komodo Kernel, S-Off, and GAPPS 20121130
Click to expand...
Click to collapse
Try Unchecking avoid poor connections and also choose to 2.4ghz channel. That might help you.
thatenglishguy said:
Hey, I searched but didn't really find the answer, heres the situation:
Whenever I run CM10 based roms I have two reoccuring issues: ( don't have these issues on Sense Roms )
1. Wifi: It will show wifi devices but we I connect it just says "Saved" not connected and isn't allowing me to use Wifi
2. ASOP Keyboard, I get a Android Keyboard has stopped working message. Tried clearing cache etc still does it ( this one is not as big as I use swiftkey3 anyway )
Currently running JellyBam latest nightly with Komodo Kernel, S-Off, and GAPPS 20121130
Click to expand...
Click to collapse
Having the exact same Wifi problem as well. Tried the CM10, Komodo rls18 and Komodo rls21 kernels with the 12/26 CM10 Jewel build and no luck with any of those combos. I am S-ON and used fastboot to install the kernels. Didn't have the wifi issue on either StockwGoodies or MeanBean sense roms. Gonna go back to the latest MeanBean release for now.
Hi,
We have 2 Vibrant phones. 1 is on Paranoid Android 2.54 (via stock eclair, ICS Passion, Slim Bean 2.9 & 3.0) and works perfectly.
The second one was on ICS Passion for a long time and I have finally got around to (trying LOL) to update it.
Here is where the weirdness begins - Flashed PA 2.54 no problems, flashed and booted up, but no wi-fi, well no wi-fi icon, and it can find a couple of wi-fi networks belonging to my neighbours, but won't find my network, 2 rooms away. The network is obviously all good, I am sending this from my laptop through said network.
Obviously I need an internet connection to get through the phone setup, so I power down, throw the SIM back in and boot up only to find no cell data either.
Skip the google account setup and get to the home screen to check things further and I find:
Calls in/out work, and most things are running, but wi-fi won't co-operate, and nothing in the APN list? Baseband and IMEI all look normal, too.
Try to flash Slim Bean 2.9 as I put the zip on the phone at the same time as a fallback and I get EXACTLY the same thing...
Anyone able to shed any light on what would cause this? Anything else worth trying? I'd like to avoid Odin as it honestly scares me reading all the problems people on here have with it...
At this point I've tried flashing both ROMs a few times with exactly the same results, I also can't go back to the ICS nandroid as the partition setup has changed and the restore doesn't work...
Thanks in advance for any help anyone can give.
Cheers...
I ended up flashing a 4.2 ROM (slim 4.2 beta 1) and it made the problem go away, I'm guessing something in the 4.1 base was broken and not getting overwritten on new installs?
ROM seems pretty sorted for a beta, few minor things not working, but hopefully it gives us a clean upgrade path...
Thanks.
I had the same issue with Slim 4.2 Beta 2. If anyone has a solution other than flashing the modem, please post.
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
I have installed slim and other ROMs but not had this issue. Currently on jellybam
Sent from my GT-I9300 using xda premium
wendleburger said:
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
Click to expand...
Click to collapse
The weird part is that every other Slim Bean has worked great. I'll keep my fingers crossed for beta 3.