Develop Bugs

[Q] Help - Portable Wifi Hotspot not working!

My wife's just got a tablet so wants to get it connected via her Wildfire.
We tried turning it on last night but it's not working properly - the hotspot functionality itself seems be enabled properly, but in Wireless and Networks, the text under the 'Mobile network' option keeps cycling between 'Connected' and 'Use phone for data connection...'.
The text 'Wi-Fi hotspot active' keeps appearing and disappearing from the notification area.
We appear to be able to successfully connect the tablet via wifi to the Wildfire but there's no internet access.
The handset is completely stock and unbranded (Froyo, build 2.22.405.1). Internet access in general is fine and my wife's data plan specifically allows tethering (GiffGaff UK, using a Gigabag).
Has anyone else encountered this issue and found a way around this? Am willing to start rooting and flashing other ROMs if it will solve the problem.

for tethering try the Barnacle wifi tethter app from market - works for me

I'll give that a try when I get home and report back here.
Have you ever tried it using the in-built functionality and either found it to work or not? Considering I've not had problems with my own handsets (previously a Desire, now a Sensation) it seems odd that I can't get it to work on my wife's Wildfire.

I used the built in one on stock rom with no problems at all on 2 wildfires, I used to use all mine then leech from the girlfriends. Could it be a problem with her apn setting? Maybe call customer service and check its set correctly for tethering.
Personally I'd tell her its broke though and flash it like I did the girlfriends purely because I'm a flashaholic!!
Sent from my HTC Wildfire using xda premium

Just in case anyone was wondering (or for the benefit of future searchers)... I finally got the Hotspot working after I installed a custom ROM (DK Custom Froyo v4.7 - I didn't want anything too different to Stock).
Custom kernels etc. didn't work (in fact, the one I tried destabilised the handset), neither did other options such as Barnacle on the stock ROM.
Thanks everyone for trying.

[Q] Anyone else having severe (wifi) tethering issues. Link to GoogleCode Bug

edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?

luck02 said:
edit: can't post links, too much noob.
go to google code, search for -- Issue 38563: Upgrade to 4.1.2 broke tethering --
My tethering appears to have gone to crap since 4.1.2
There are quite a few variables so I'm not sure where the problem is, on top of that the issue is not 100% consistent.
It appears that when I am not tethered I get a decent ping on my phone (150ms, 95%)
Shortly after initiating a tether my connection goes straight to hell (300-3000ms 50%)
My laptop is often even worse than my phone.
This is usually with a full 5 bars of 'H'.
I'm gathering the ping stats from my phone with terminal emulator.
I'm using a MacBook Air.
I will try to reproduce the issue with my nexus 7 when I have some spare time.
Anyone else experiencing something similiar?
Click to expand...
Click to collapse
http://code.google.com/p/android/issues/detail?id=38563

I, like many others have had this problem since 4.1.2, rolled back to 4.1.1 and WiFi tethering worked again. Back to 4.1.2, stopped working again. Installed 4.2 on Gnex yesterday hoping for fix but still no good.
As 4.1.2 is "old hat" now I have started new issue at Google for 4.2 here
code.google.com/p/android/issues/detail?id=39618
Please anybody with same problem go there and add to report.
DO NOT turn it into a *****ing thread like so many here on xda.!!! The item to which luck02 referred for 4.1.2 at code.google.com is just full of twats ranting about their phone suppliers charges for data and crap like that.
code.google.com is to report faults and bugs and by everybody contributing pertinent information maybe Google will look for a fix. Trolling and whinging does nothing but obscure the facts...... please respect this. Just tell them model number, build and describe fault - thanks

Well there is definitely some ranting and twats involved but to my mind that's just part and parcel of being on the internet. Ignore and contribute as you can. Has anyone tried the CM build on the GNEX? Also, has anyone confirmed / denied whether third party wifi tether applications resolve the issue (requires root)?
Actually even more importantly, has anyone isolated where the breakage is actually occurring? I'm assuming it's something in the drivers / networking layer that is screwing up the routing between incoming data and the wifi layer...
I will probably downgrade if nothing else works.

So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.

luck02 said:
So I got frustrated and rooted / installed clockwork recovery.
Moved to CM 10 and still have the same issue. I'm thinking it's actually a carrier issue for me at this point.
My carrier term expires in January and I'll probably go to a different carrier then.
Will follow up with more information as I have it, I may roll back to an older version of CM to confirm the problem is still occurring.
Click to expand...
Click to collapse
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
Even made my own Odin package using radio from 4.1.1 (even tho supposedly same as 4.1.2) system and other files from 4.2 - same result, nothing worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Tried two WiFi tethering apps with exact same result... shows tether as working, greyed out WiFi icon on tab and no go on laptop or desktop....I have spent hours on this to no avail

Have you tried any network diagnostics while not tethered?
I may be getting carrier and 4.1.2 issues. I was running some ping tests while not tethered yesterday. Full 5 bars of 'H+' running CM10 and I was getting horrible signal. More than 50% dropped packets and long ping times.
I'll roll back to an older CM sometime soon and see if there's a difference over the next couple of days.
Thank you,
stinky73 said:
Definitely not carrier for me, proved by numerous attempts and firmware this weekend. Gnex running 4.1.1 everything works perfectly. Let phone do ota to 4.1.2, broke WiFi tethering and Bluetooth to vehicle completely. Reinstalled 4.1.1 thro Odin and re-partitioned at same time so completely clean install, WiFi tethering and Bluetooth worked perfectly. Continued on complete wipe track by then installing 4.1.2 thro Odin with re-partition (thus removing possibility that incremental upgrade to 4.1.2 was to blame) still no WiFi tethering or Bluetooth.
Did same for 4.2 using Odin still didn't work. Returned to 4.1.1 using Odin, everything worked.
To eliminate doubt used same sim card in two HTC phones running 4.0.4, both showed correct working and tethering and Bluetooth. Conclusion, not carrier/ supplier related, but surely random hardware/ firmware incompatibility on some examples of Gnex for unfortunate souls such as us
Click to expand...
Click to collapse

I'm Noob, I got problem same error on 4.2 and 4.2.1, this issue over half a month.
I have google some website, found have several people like us have this issue and still no idea to fix it...
Mostly couldn't connect to laptop or Mac Book. For me is PlayStation Vita (firmware 2.0 Wifi only)
My PS Vita could deal with my galaxy Nexus on 4.1.2 , but 4.2 is could reach Internet correctly.
I have tried several Wi-Fi Device to connect my Galaxy Nexus,
My PC , My PS3, My PSP, My Uncle Galaxy Nexus 4.1.1 (Samsung image) are working fine.
Only my PS Vita couldn't...
But base on others, have same issue on other device, so I did think this issue may cause by 4.2.
Base on this issue, I have try "wifi-tether" , whatever this download on Google play! or "3.3 pre-2" on their website.
I have it running on Factory 4.2 , 4.2.1 Rooted + Super user, this couldn't work correctly.
Running on KALO 2.0 ROM, this have error on "Clamping MMS"....
No Luck for me.
My GNexus is only one device at the moment, which could let my PS Vita online... I have some PS Vita game need running online.
This force me stay on 4.1.2 and try disable System update notification next minute, for several weeks or month until the solution come...
Or... Anyone could build a patch which could let 4.2 using 4.1.2 Wi-Fi tethering engine?

[Q] Is WIFI Tether working?

I haven't been able to get my wifi tether working. I've searched for hours but most of the post aren't very recent. I've tried adjusting the settings to many different combinations as mentioned in three other posts. I'm on baseband MC2, JB 4.1.2 and have tried two roms...Swampmonster 2.2/2.3 and Macks Allstar 5.0, as well as using both my PC and laptop to connect. I've used the TrevE mods that come with both roms as well as a couple of apps from the play store.
The same thing happens with every attempt, I connect to the AP but don't get any connection to the internet...DNS server is not responding.
I've recently changed from big red over to sprint and have had my N2 for about a week now. Is this a Sprint thing or is it just my unfamiliarity with my Note 2?
Any help would be much appreciated. Dexter's on tonight.....
Also tried WolfRom and USB tethering, still no connectivity

Delete

It's been working for me, basically. I'm on a stock deoxided MC2 ROM with Perseus kernal. I get an error but I don't know what it is, since the log gives another error about no file existing. The error I had before trying to reinstall WiFi and BusyBox was a routing fix failed error.
I used this at work for at least six hours to connect a tablet and laptop. I figure I'm using around 2GB to 6GB each night.
Unfortunately, you're going to have to keep experimenting. I suggest trying with just the defaults settings. See what happens. If not, try changing Driver reloads or none. Unfortunately, it's just a lot of trial and error.

lovekeiiy said:
It's been working for me, basically. I'm on a stock deoxided MC2 ROM with Perseus kernal. I get an error but I don't know what it is, since the log gives another error about no file existing. The error I had before trying to reinstall WiFi and BusyBox was a routing fix failed error.
I used this at work for at least six hours to connect a tablet and laptop. I figure I'm using around 2GB to 6GB each night.
Unfortunately, you're going to have to keep experimenting. I suggest trying with just the defaults settings. See what happens. If not, try changing Driver reloads or none. Unfortunately, it's just a lot of trial and error.
Click to expand...
Click to collapse
Thanks. I don't give up easily...I'll get it working if possible. I'm just wondering if Sprint is blocking the tether because I connect right away with no errors but the "DNS Server is not responding".
I see you're from the bay area. I grew up in SF but haven't been back in a long time. I miss the beach...

izombie13 said:
Delete
Click to expand...
Click to collapse
Hey Zombie, why u messing with my thread

jksell07 said:
Thanks. I don't give up easily...I'll get it working if possible. I'm just wondering if Sprint is blocking the tether because I connect right away with no errors but the "DNS Server is not responding".
I see you're from the bay area. I grew up in SF but haven't been back in a long time. I miss the beach...
Click to expand...
Click to collapse
Sprint should be blocking you unless there is something off on your phone. My issue, I think, has to deal with the BusyBox Linux binary library that got loaded. I'm assuming maybe a phone wipe and reflash may fix it.
Yea, I'm near the wine valley, actually. Although, I prefer to be back in San Diego.

I installed Goodness Noteworthy v1.0.8 ROM and get good wifi tethering of 3G. I haven't tested 4G as I don't get it yet.

I'm just running stock rooted MC2 with updated CSC data (Garwyn's) and the separate TrevE version of the Wifi Tether APK works like a charm. My kids just used it on 3G and LTE all the way down I-95 in Florida. Sometimes it would boot them all off when switching from LTE to 3G, but they'd reconnect without issue.
Not sure if that helps you, other than I'm using the very latest MC2 OTA and maybe you're still using a ROM based on the leak? I'm not a dev, so if I'm talking out of my posterior just disregard!

Got it working
I'm still not sure why I had problems when nobody else did on the respective threads for the roms I mentioned above.
I did get it going though...For the touchwiz roms I had to run ISWAT tether unlocker while my tether was active (It's on the Play Store).
Right now I'm running LiquidSmooth's AOSP rom and the native tether works great. I've been bouncing back and forth between nandroid
backups; I like TW most of the time but when I want to tether or am looking for speed/responsiveness I switch over to AOSP.

Just to make sure, have you tried this: http://forum.xda-developers.com/showthread.php?p=40234725
I flashed it on deodexed stock MC2 and it works great, even with tablets and an iPod Touch.

I got it working with Treve mod
WifiTether_TrevE_Mod_11_20_2012_insmodv3.apk
Had to change one settings, or else it wouldn't appear on PC
Change Device-Profile to Generic ICS/JB wlan0
Credit for file link:
http://forum.xda-developers.com/showpost.php?p=34465068&postcount=1

I've got it working on deoxidized rooted stock rom. I'm using the latest beta from July 20, 2013 (TrevE Mod Wifi Tether. The only setting I needed to change was to Driver Reload 2.

wifi-tethering
Now, I'm also using the Wifi -Tethering . its still working now.
you can find info from rootnote2.com

Is the problem of wifi tether under AOSP rooms on this device totally insoluble?
I've never found an answer to it, only directions to fixing it under TouchWiz or vague changelog entries about having 'fixed wifi tether' on Carbon and such, which did no such thing.
Standard wifi tether app 3.3b2 fails to start an access point. TrevE mod claims to start fine in the app's log, but no access point shows up on a scan. The mobile hotspot function in system settings also starts up, and even let's devices connect, but there's no data transfer.
I understand that there's something bad going on with Samsung's release of wifi drivers, so I'm just hoping that someone somewhere has looked into this.

[Q] Chromecast Issues on MOAR v7.1.0?

I have the Sprint Galaxy S3 and I recently switched to MOAR. It's great but since then I also am unable to find my Chromecast device from my android phone. My laptop can discover and stream to it just fine, as well as two other Android devices (one that is rooted and one that is not). It seems odd to me that this would be the problem, but I didn't make any other changes around the time it happened.
I've tried power-cycling my phone and the router, making sure everything is on the 2.4ghz network, and resetting the Chromecast via the button as well as in chrome. Help? Is there any solution short of changing roms (if that even is the problem)?

Well as an update.. I have since factory reset the phone and Chromecast worked again. Now I am running the Wicked Rom and I can't find the Chromecast again. If this is really a rom problem I wouldn't know why others haven't brought it up. Also, my friend who has a rooted s4 is running Hyperdrive and he was able to connect to the Chromecast so I am just really confused.

It's because your phone is 5mhz instead of the chromecasts only option the 2.4.
Sprint L710, HTC One, ipad mini, Nexxus 7

Blocked tether, looking for assitance

When it come to rooting and bootloader unlocking I'm quite savvy, however, recently I found myself going in circles. Recently I started new service with Metro PCS and my tether is blocked. I have tried just about everything and cant get it to work. Here is what I have done so far:
1- Added the line "tether_dun_required" to Setting.db
2- Made changes to to APN (changed APN Protocol to IPV4) for
3- I have 3 different wifi tether app including Wifi Tether Router
4- I have installed 2 different custom ROM one of them was AOKP CM11
At this time I no longer know what to do. I know that I could use user agent changer for chrome, but I cant use for my school homework. I need the full Chromebook & Tablet tether.
For the past 3 day I have been reading threads, articles, and anything related to this issue.
Any help or suggestion would be greatly appreciated.
My device is a Nexus 5 running AOKP CM11
Update 1: I tried Hotspot shield and it did dot work. Tried with the native tether and wifi tether router.

Hello! I've ran into the same issue recently with MetroPCS, I've tried almost exactly the same fixes you have but to no avail.
Does anyone out there know of a for sure fix for this? Any help is greatly appreciated, thanks!