Hey all,
WiFi Tethering for me is still not working at all on CM10 or AOKP, I've tried going from Official JB and CheckROM JB, bit no cigar.
What installation steps/precautions do I have to take to make it work?
Thanks in advance all.
Beans
Sent from my GT-I9300 using xda premium
So far as i've seen on the CM10 thread, it used to work (september?) but has since stopped at the result of some merges or cleaning of code. Consensus seemed to be that there was no obvious problem to fix, and not enough enthusiasm to really investigate without more sources from Samsung. (and since this is wifi driver code, that may be some time in coming).
Would be great to hear otherwise, but i think it's a case of wait, make do with BT tether, or back to stock based ROM.
Anyone confirm or otherwise?
Related
I'm very tempted to try out an ICS ROM and wonder which I should try. Some swear by Onecosmic's ROM saying it's smoother and more stable than Passion. It's 911 and e911 seem to both work but GPS seems to be broken. Passion seems to be getting the most traffic. e911 is broken though 911 works. GPS is way better than Onecosmic, if I understand correctly, but kernel dependent.
Which are you using and why? Or should I wait for more issues to be fixed, e.g. mute/unmute?
I ran Onecosmic's for a while. 2.11 was pretty good. They then produced a 3.1, but didn't bother to change the build.props values from i9000, guaranteeing problems and showing a lack of seriousness in supporting the Vibrant, so I tried the CM9 kang. Build 14 was good, but 15 was terrible (looked like build.props was incorrect), decided to stay with CM7 until an ics rom has CM permissions management. No experience with Passion.
I agree a lot with what cashmundy said. Neither onecosmic nor the cm9 teamhacksung have vibrants and are builing for the I9000 so we are just getting I9000 ports with no true support from the rom dvelopers. Not that either is a bad rom but the Vibrant community is the ugly step kid in the development. Neobuddy and Nelson are building ICS Passion on their Vibrants and supporting it well. Passion is based on cm9 as far as I can tell with Neobuddy working it for the Vibrant. Nelson is constantly trying to improve the kernel and latest is based on rev 3.1.10. Passion has it's bugs and each new version fixes some and regresses on others but it's a Vibrant rom worked on by Vibrant devs and is the most complete IMHO.
I honestly havent tried OC's rom. Been really happy with Neo's Passion. It seems everyone has a different quirk. Some people's GPS works, some don't, some have the mute/unmute bug, some don't. My GPS works AND don't have the mute/unmute bug. One of the lucky few it seems.
ICS Passion v12
I like it a lot after CM dropped further development. It seems to move around faster and is clean. The mute/umute doesn't seem to be an issue for me. Haven't tried GPS except to play with Angry GPS. Seems like I was picking up satlellites, best I could tell. I read something about a unlocked Samsung phone from China not working on 911, but did on 112 (international emergency). I'm beginning to wonder that if Samsung won't share the codes...DOES 911 work on the stock ROMS??? I'm thinking I can live without 911, since my option of returning to the Eclair ROM makes me ill... .
Seems like 911 is broken passion v11 onwards
ICS passion it should be, as cashmundy said, its dedicated to Vibrant. I have working GPS but the Mute/Unmute issues bugs me. I am still on v11 btw.
Both roms are good, I think that passion has more tweaks. Both are stable less mute and unmute bug which is keeping me on trigger 822. But other than that everything else works great. Just irritating that a phone does not do the simplest feature of answering a call correctly.
Sent from my SGH-T959 using xda premium
how can I put the firmware in order to avoid a bug with the microphone?
In general, there is such of the ICS?
There is a new Onecosmic version out, 4.1. I'm pulling it down to see if the build.props still say i9000 instead of t959.
One important philosophical difference is that Onecosmic is explicitly AOSP and only AOSP, whereas Passion is using some or all of CM9. That's reason enough to choose Passion for me. I'm just waiting for permissions management to get ported.
PS: download of Onecosmic version 4.1 finished, took a look inside with Ghost Commander (must-have tool) and the build.props is correct for T959.
Give me the link.
sada23 said:
Give me the link.
Click to expand...
Click to collapse
http://i205.photobucket.com/albums/bb137/linkrocks1997/link.jpg
...why the wifi problem is sporadically happening in the JB ROMS?
I have tried most of the leaked and modded ROMS from early CM10 to Faryaabs Supernexus builds to the latest leaked firmware on 29th Aug.
However, whichever leak it was that first exhibited a wifi problem for the (unlucky) select few seems to have knackered my chances of connecting to wifi properly on all subsequent JB ROMS - even if wifi worked before. eg. Supernexus build 2 was all good on the wifi front, I only had probs with a few bugs and the camera lag. I flashed it again today though to find that it doesn't want to let me connect to my router.
This was the same with Omega v16, v16.1 and v17.
It seems to be reported that it is connected to router security settings and I know there is a 'fix' out there for it but the fix that I tried only made the wifi slightly better and was peppered with 'unable to establish secure connection' warnings when out and about.
Can anyone add to this or highlight an alternative solution? I have spent the last 30 or so evenings religiously reading the forums and if anything I'm a bit confused and bewildered
I'm on Omega v13 atm and cannot fault it (but I want Google Now) and I attach a snap of my current set up in case it has a bearing on where I'm going wrong.
Sent from my GT-I9300 using xda app-developers app
Lolpoppa said:
...why the wifi problem is sporadically happening in the JB ROMS?
I have tried most of the leaked and modded ROMS from early CM10 to Faryaabs Supernexus builds to the latest leaked firmware on 29th Aug.
However, whichever leak it was that first exhibited a wifi problem for the (unlucky) select few seems to have knackered my chances of connecting to wifi properly on all subsequent JB ROMS - even if wifi worked before. eg. Supernexus build 2 was all good on the wifi front, I only had probs with a few bugs and the camera lag. I flashed it again today though to find that it doesn't want to let me connect to my router.
This was the same with Omega v16, v16.1 and v17.
It seems to be reported that it is connected to router security settings and I know there is a 'fix' out there for it but the fix that I tried only made the wifi slightly better and was peppered with 'unable to establish secure connection' warnings when out and about.
Can anyone add to this or highlight an alternative solution? I have spent the last 30 or so evenings religiously reading the forums and if anything I'm a bit confused and bewildered
I'm on Omega v13 atm and cannot fault it (but I want Google Now) and I attach a snap of my current set up in case it has a bearing on where I'm going wrong.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
No?
Well if it helps anyone I eventually found a work around.
After numerous different combinations of ROM, kernel and modem is finally got wifi working on a JB ROM
I was using Omega v13 and then I flashed the latest Siyah kernel ( http://db.tt/PgmwhO96).
After this I have been able to flash JB based ROMS over the top with no issues with wifi whatsoever
Sent from my GT-I9300 using xda app-developers app
Lolpoppa said:
No?
Well if it helps anyone I eventually found a work around.
After numerous different combinations of ROM, kernel and modem is finally got wifi working on a JB ROM
I was using Omega v13 and then I flashed the latest Siyah kernel ( http://db.tt/PgmwhO96).
After this I have been able to flash JB based ROMS over the top with no issues with wifi whatsoever
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Try ROMOW Rom , Wifi with WPA2 encryption works fine since version 3
I'm new to rooting and running custom roms. Has anyone tried any of the latest version of CyanogenMod 10 for the evo lte. Is it stable is it fully functioning. Sorry for the noobness but we all start somewhere. Thanks
I have been running it all day, I don't know the differences from the previous nightlies, probably the same tiny bugs. I haven't played around with it too much.
I have always been curious as to what the differences are between the MANY JB ROMS we have here. They all have the same problems...
I've been using codefire cm10 JB ROM now for around 3 weeks it seems to me that everything is working fine so far. you should try it out I haven't had any problems yet... I'm going to stick with it
Sent from my EVO using xda app-developers app
Jrobb2007 said:
I'm new to rooting and running custom roms. Has anyone tried any of the latest version of CyanogenMod 10 for the evo lte. Is it stable is it fully functioning. Sorry for the noobness but we all start somewhere. Thanks
Click to expand...
Click to collapse
Ive been using the CMX CM10 JELLYBEAN ROM as my daily driver for the last six weeks and it is great. Personally i think the bugs are totally minor. Nothing you cant deal with really. I liked the CodefireX tweaks. I just update the Rom using the GooManager and for some reason they changed it from NIGHTLY to EXPERIMENTAL for whatever reason. Also noticed the CMX tweak are gone from the update? dont know why. Anyone here know? otherwise the ROM is really fast and stable enough.
Am I alone here? It looks great and is speedy as hell. But after I leave the house and I'm not on wifi any longer all the problems start popping up. Terrible signal (even confirmed using OpenSignal), only hold 3G half the time and NEVER get a 4G connection in the places I always get one on a ICS ROM. Also, camera is worthless. And MMS doesn't work almost always.
I really appreciate all the work everyone puts into it. I couldn't do any of the stuff these people are doing. I've tried CM10 and ParanoidAndroid and I can't wait until they hit a stable/primetime state. Just not there yet.
But if it's just me please somebody chime in! I have done PRL and profile updates on stock ROM before flashing so I don't believe it's that. Stock ROM and Mean ROM both give me great signal/data and 4G.
right now I'm on codefire jb release date 26 plus I flashed the duocoreAOSPmod my phone is fast, and also I used the 3g uncap codefire tweak. I'm not having any 3g speed problems.
the reason why I'm still on #26 is because when I flashed the 04 nightly the WiFi will not work it just says error. So hopefully they fix that then I will update. If not I really would hate to discard codefire cause I like it a lot.
Sent from my EVO using xda app-developers app
I need some assistance trying to narrow down what is causing my issue. I posted this in the TMobile SGS3 Q&A section but I wanted to post here to get more exposure and perhaps someone more knowledgeable can chime in. I believed this to be a AOSP JB kernel issue but I also tried CM9 on my phone and the problem persists.
For some reason my phone will randomly disconnect from my WiFi connection when running an AOSP rom. The actual WiFi service will remain on; I can see available networks but it will not reconnect to my saved AP unless I toggle WiFi off/on, and even then it will randomly disconnect again. The same thing happens with CM, and ALL CM-based roms. I have tried Faux, Imoseyon, Trinity, stock, and Ktoonsez kernels and none seemed to fix this issue.
Stock TW roms, both ICS and JB, keep my connection just fine. I also used the same CM nightly build on my GS3 and my Galaxy Nexus for testing purposes. The GS3 will lose connection while the GNex does not, so I figured it had something to do with the kernel since those are usually phone-specific.
As for the WiFi signal, I don't have any issues neither at work nor at home with TW-based roms. This only happens on AOSP. Any insight you guys have regarding this issue is appreciated. Thanks!
I ran a logcat but to be honest, I do not know what to make of it. would anyone happen to understand where my issue is?
Link to original thread
Infamous_Cheez said:
I need some assistance trying to narrow down what is causing my issue. I posted this in the TMobile SGS3 Q&A section but I wanted to post here to get more exposure and perhaps someone more knowledgeable can chime in. I believed this to be a AOSP JB kernel issue but I also tried CM9 on my phone and the problem persists.
For some reason my phone will randomly disconnect from my WiFi connection when running an AOSP rom. The actual WiFi service will remain on; I can see available networks but it will not reconnect to my saved AP unless I toggle WiFi off/on, and even then it will randomly disconnect again. The same thing happens with CM, and ALL CM-based roms. I have tried Faux, Imoseyon, Trinity, stock, and Ktoonsez kernels and none seemed to fix this issue.
Stock TW roms, both ICS and JB, keep my connection just fine. I also used the same CM nightly build on my GS3 and my Galaxy Nexus for testing purposes. The GS3 will lose connection while the GNex does not, so I figured it had something to do with the kernel since those are usually phone-specific.
As for the WiFi signal, I don't have any issues neither at work nor at home with TW-based roms. This only happens on AOSP. Any insight you guys have regarding this issue is appreciated. Thanks!
I ran a logcat but to be honest, I do not know what to make of it. would anyone happen to understand where my issue is?
Link to original thread
Click to expand...
Click to collapse
Are you using any kind of signal extender or an acess point? I've seen similar problems with android getting confused on wich point they need to connect, if the answer is yes try to turn off the extender before connecting to see if that's what's causing the issue. Unfortunatelly I don't have simple steps to solve this, it's all trial and error, turn off the devices individually and start connecting until you get an order that suits your phone.
Hope it helps!
Thanks for the input. I don't use either of those. The phone connects directly to the router. The router sits in the same room so signal is always strong and no other devices connected to the router have any issues. This is definitely a bummer because I would love to run AOSP as my daily driver. I will keep troubleshooting.
Sent from my SGH-T999 using Tapatalk 2
Anyone know what ROMs have working GPS? I prefer 4.1 ROMs.
Sent from my SGH-T959 using xda premium
ppillow said:
Anyone know what ROMs have working GPS? I prefer 4.1 ROMs.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I'm still using Slim ICS with 4.0.4. The GPS is ok, it works but still not great. I don't think my phone will ever be great though. I want to try out SlimBean but it seems they are having GPS issues among other things.
Honestly, I've found that GPS can be a real hit or miss depending on your specific phone.
All hardware is not created equally, unfortunately. I'd suggest testing a few different roms and find which works best
for you specifically...because I've had luck with GPS on roms where users have reported bad GPS, and no GPS on roms where
awesome GPS was reported.
Good luck!
ppillow said:
Anyone know what ROMs have working GPS? I prefer 4.1 ROMs.
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I would use either PA or CM10, but you need to flash the 3 gps fix files located somewhere in the PA thread. I would not use Slimbean 3.0 if you really need GPS since even if you do flash the files, no satellites come in view at all. I got a lock below 10 sec outside driving on monday at 7:30 pm. Accuracy was about ~25 feet, so it was really good. I was on CM10. Anyway, both have really good GPS as long as you have the 3 GPS files. They are called: GPS - Experia Files, YAGF2, and cwm-cm9-gps-wrap. Flash it in the order I wrote it in. They arent hard to find. Just type the names into Google. Or look in the PA thread. Good luck bro, and as Xenoism said, it also varies with device. If your device was made before Nov 2010, you probably wont get a lock no matter what unless you did the hardware fix. Even with the hardware fix, you'll still need these 3 files.
EDIT: Because I'm nice, I found the post where Jrafael posted the GPS files. It is here: http://forum.xda-developers.com/showpost.php?p=33575684&postcount=504
I have great gps with SlimBean and the 3gps fixes, its even better than my Galaxy Nexus. However, I owned a couple Vibrant and they all seem to have difference performance. Try the hardware gps fix if you're brave.
Note that for SlimBean if you patch mismatched patches it can make GPS stop working completely, only patch gapps from their own site.
eksasol said:
I have great gps with SlimBean and the 3gps fixes, its even better than my Galaxy Nexus. However, I owned a couple Vibrant and they all seem to have difference performance. Try the hardware gps fix if you're brave.
Click to expand...
Click to collapse
Which version of Slimbean are you on? 2.9 works fine, but 3.0 is stone dead. (From my experience and a bunch of other members) I flashed the files and rebooted, tried getting a lock and not even one satellite appeared. Usually on other roms i get locks in less than 10 secs and after deep sleep, less than 20. I dont think he'll need the hardware fix if his phone is built after Nov 2010. But if its built before, then he'll definitely need it if he needs GPS that bad. That or get a new phone with GPS or buy a GPS :good: