since i can't post in his actual thread, what tethering app works with mmuzzy's 4.2 rom. the one i have always used for 4.0 and 4.1 no worky on 4.2
tHaNkZ!!!
:victory:
I believe that Android built-in tethering should work without a problem, it does on mROM
My tethering isn't working when I try to use any 4.2 Rom.... and it seems like the issue isn't being addressed or looked into because for every 1 person who is having this issue, there are 100 who are not. There's obviously something specific to our devices we must have done previously for it to only affect a few of the people who are attempting to flash to Jellybean 4.2, so hopefully it will get noticed by someone who can figure out a solution to the problem.
Related
I have a d2tmo GS3 and been running CM10 nightlys. It is alright but I sometimes have BT trouble between the phone and the car and so I am looking to see if there is another ROM that will work better for me.
I am mainly looking for a relatively vanilla JB ROM. Don't need or care to much about fancy stuff. Its ok if it has extra features as long as they don't cause problems. More than anything else, I want a stable ROM that works correctly.
There are two problems I am having with BT.
The first is that the phone does not always auto connect for music with my car. It used to also have trouble connecting for phone, but a recent nightly build seems to have fixed that.
The second is that when it does connect, it automatically starts playing a random file (it did this with the stock ROM as well). For some reason my Nexus S didn't do this with either ICS or JB vanilla Android. My understanding is that this is cause the phone is getting an autoplay signal from the car. I am hoping there is an Android version that can be set to ignore this request.
Frosty.
aviphysics said:
I have a d2tmo GS3 and been running CM10 nightlys. It is alright but I sometimes have BT trouble between the phone and the car and so I am looking to see if there is another ROM that will work better for me.
I am mainly looking for a relatively vanilla JB ROM. Don't need or care to much about fancy stuff. Its ok if it has extra features as long as they don't cause problems. More than anything else, I want a stable ROM that works correctly.
There are two problems I am having with BT.
The first is that the phone does not always auto connect for music with my car. It used to also have trouble connecting for phone, but a recent nightly build seems to have fixed that.
The second is that when it does connect, it automatically starts playing a random file (it did this with the stock ROM as well). For some reason my Nexus S didn't do this with either ICS or JB vanilla Android. My understanding is that this is cause the phone is getting an autoplay signal from the car. I am hoping there is an Android version that can be set to ignore this request.
Click to expand...
Click to collapse
I'm actually having the same problem with auto-connect I have a thread going as well. I am running wicked JB which is TW based so close to stok and thats my only problem so far
Just to be clear, when I say "vanilla JB" I mean JB like google intended, not neccesarilty GS3 stock rom.
psykhotic said:
Frosty.
Click to expand...
Click to collapse
Does Frosty allow your phone to ignore BT autoplay requests?
Wicked
Sent from my SGH-T999 using xda premium
Frosty or Wicked. Both have been very stable for me.
Frosty is incredible give it a shot.
Tethering keeps throwing me an error on CM10 - as expected, Dman has said that he removes it from all of his roms.
Is there a workaround for this? I looked around and found the fix for the ICS leak, but I'm not eager to give that a try unless someone can confirm it works with CM10.
It works for me in cm 10 with foxfi from playstore. In cm 10.1 it doesnt work though
Oddly enough, the stock wifi tether in the settings started working after installing FoxFi
Tyfighter said:
Oddly enough, the stock wifi tether in the settings started working after installing FoxFi
Click to expand...
Click to collapse
Wow same thing worked for me even after uninstalling foxfi the native app works. Nice
pacman rom has always worked for me without needing to install anything .... I need it for work from time to time so that holds me to 4.1 ..
The CM 10.0 build available also has a flawless Wifi and USB Tethers. (Haven't tested the BT one)
This issue may effect more than just sprint GNex users, i'm not sure. Ever since 4.2.1 has hit our developers hands i've had nothing but issues tethering my internet. Unfortunately for me tethering is my only means of internet, so this poses quite a problem for me. One easily solved by going back to a 4.1.x rom, but who whats to downgrade, what's the fun in that?? I have messed around with different 4.2 roms and found a few that act differently and i'm hoping that the devs can collaborate and get a system together what works flawlessly like 4.1 did.
First rom up: Paranoid Android 2.99 PIE 4.
No tethering at all on this rom. Tethering turns on and technically works fine but there is an error with SecPhone.apk and data is dropped on phone until tethering is turned off.
2nd Rom: Black Bean 7.
Half-ass tethering. Tethering runs well enough at first, but any drop in data, and my phone can't reestablish a data connection. Again causing a problem with SecPhone.apk.
3rd Rom: CMK v2.
Tethering seems to function flawlessly on this rom. Connection reestablishes after a call just like it should. I'm hoping that whatever this dev did to make the tethering work we can get on all of our 4.2.1 roms.
So my next question. Can I fix the issue by installing CMK's SecPhone to PA and have tethering working? Does the problem lay in the SecPhone app or is it just an innocent bystander crashing when something other go haywire?
Try sourcery rom. Has the tethering capabilities of cmk and all the features if PA plus much more. Auto hide navbar and keep screen off when plugging in charger are a few exclusive features with many more.
Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?
Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.
Aerowinder said:
Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.
Click to expand...
Click to collapse
Yeah, that bug alone didn't happen when I first started using 10.1. Not sure when it started to be honest.
Update google search for the keyboard I think
mt3g said:
Update google search for the keyboard I think
Click to expand...
Click to collapse
That's very possible. It's one of the first things I try when I get the latest nightlies, so I probably try it each time before I have updated anything.
Is there any reason to think that the hot-spot issue will be resolved in 4.2.2?
Ya, and I don't know, it might be coding that is needed within AOSP, does wifi tether encrypted not work on the Nexus 4 or GNEX?
Just an update for anyone who is searching and finds this thread by some chance...
It looks like 4.2.2 did not fix the HotSpot issue, but it did fix the Bluetooth streaming. I tried the SmoothRom 4.2.2 release, to test these things.
PAC-man rom 4.2.1 is my current favorite rom, and they did somehow fix both of those issues recently. Probably had something to do with 4.2.2's release this week. So if someone is looking for a 4.2 rom with working Bluetooth, and WiFi tether encryption, you might want to give that rom a try.
It is right here:
http://forum.xda-developers.com/showthread.php?t=2015525
4.2.2 has working everything. On Liquid Illusion you need to flash a custom kernel that is updated to have encrypted hotspot.
Sent from my SGH-T999 using xda premium
ArkAngel06 said:
Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?
Click to expand...
Click to collapse
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.
milesmarrero said:
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.
Click to expand...
Click to collapse
Thanks for the info, but updating to the newest Google App from the PlayStore fixed it for me.
Your solution would probably fix the need to reflash.
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