Related
First of all, I'm not new to rooting my devices. This is the 4th Android phone for me (Dream, Magic, Captivate now the S III), all have been rooted by myself. What is scaring me off rooting at the moment is the flash counter and a decent working Rogers ROM. I need to be able to toggle LTE, when I travel out of the city there is LTE availability but it is garbage. The phone is faster on GSM at that point, believe me, I tried everything I could to make it better. I need WIFI tether to work properly. I did find the hint about switching to the tether APN, and that works, but that is a bogus solution, I shouldn't have to do that. Ohhh, not to mention the garbage email client (who does *not* support HTML emails these days?!?!?).
What I am looking for from Rogers users is advice from people who have done it for (limited risk) a root solution and a decent ROM that will fit the bill for what I do.
In my everyday travels I use Bluetooth pairing to the car for media streaming, wifi tether, usb tether (only when wifi doesn't work, but then I can't connect the TouchPad to the 'net), email, sms, browser (I do like the stock browser in ICS & Jelly Bean AOSP, but the ioncluded one in Rogers version sucks balls).
Anyone got any fool proof solutions I can use?
PS-I'm not a newb, please don't tell me to go search, I've read thread after thread after thread and there is so much conflicting information available right now. I'm looking for advice from Rogers users (Bell/Telus would probably be ok too) that have actual experience.
tbrummell said:
Ohhh, not to mention the garbage email client (who does *not* support HTML emails these days?!?!?)..
Click to expand...
Click to collapse
To this one point: this has nothing to do with the Rogers ROM. Stock email client on JB/AOSP also does not scale HTML emails, neither does Gmail. In fact, though I hated the convoluted interface and buried menu options Rogers added to the Email app, they actually added the ability to use rich-text when sending emails, which is absent in AOSP.
I guess I got used to the AOKP ROM's which do have a decent email client. And you're right about the Rich Text in the Rogers ROM, but 90% of the emails I get are HTML. Makes them hard to read.
I'm currently rooting the device, still looking for ROM opinions...
Where's my Easy button? That was easy.
Currently rooted and de-bloated. Still waiting for decent ROM suggestions.
I am pretty much in the same boat as you. How/what did you debloat?
I'm backing up my phone now and going to load a ROM shortly. I'll post back if it doesn't brick.
I followed this to root, install CWM Recovery, and de-bloat:
http://forum.xda-developers.com/showthread.php?t=1739426
Just installed this ROM, but it won't toggle back to LTE, currently trying one more fresh flash and will have to restore my Nandroid of the stock ROM if it doesn't work:
http://forum.xda-developers.com/showthread.php?t=1751595
Well that didnt' work well....... the ROM loaded, but Google Play Store won't load. Nor did any of my apps. SO.....
Back to the stock rom until I learn more about this.
dssking said:
I am pretty much in the same boat as you. How/what did you debloat?
I'm backing up my phone now and going to load a ROM shortly. I'll post back if it doesn't brick.
Click to expand...
Click to collapse
Yeah, running that ROM I toggled to GSM & back to LTE and it stuck on Edge, wouldn't come back. So I restored my Nandroid. Will look in to other ROM's when I have some time.
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?
Does anyone know if T-Mobile WiFi calling can be enabled on the vanilla Android S4 when it comes out. I was wondering if it is technically possible.
This is the only thing that's holding me from getting the stock Android S4 (when it comes out) instead of the T-Mobile S4.
From what I've read, the nexus 4 from Google doesn't support it, so I assume the dev version s4 would be the same since it is a T-Mobile feature. I also believe a lot, if not all, roms does not support this feature. I could be wrong, so someone with more experience pls chime in.
Sent from my SGH-M919 using Tapatalk 2
ferganer said:
Does anyone know if T-Mobile WiFi calling can be enabled on the vanilla Android S4 when it comes out. I was wondering if it is technically possible.
This is the only thing that's holding me from getting the stock Android S4 (when it comes out) instead of the T-Mobile S4.
Click to expand...
Click to collapse
If you really value WiFi calling (and I assume you are with T-Mobile now), I don't even know why you don't just go ahead
and buy the T-Mobile S4. There is almost zero advantage the AOSP S4 will have over T-Mo S4.
Maybe you didn't want to root your phone, but then I figure, WiFi probably will not be included on the AOSP version,
and even if there was a way, you would need to root the phone regardless to flash the ROM/MOD.
In the end, I really see the T-Mo S4 as your best bet, as I can guarantee 99% you can flash AOSP ROM with all its features
more easily to a T-Mo S4 than to flash the WiFi calling feature unto an AOSP S4.
I currently have the Nexus S on T-Mobile. My two key features are Wi-Fi Calling and Wi-Fi Hotspot / Tethering. Hotspot/Tethering works great on the Nexus S, and there is no extra charge for it.
Wi-Fi Calling has never been provided for the Nexus S, and nobody has been able to figure out how to add it, so I'm thinking about upgrading to the GS4.
I see two approaches to meet my needs:
1) Buy the T-Mobile version, but have to root it and maybe load new ROMs to eliminate the unwanted carrier apps etc. I'm assuming T-Mobile would not directly offer free tethering like the Nexus S on their phone. I'm aware various apps promise to enable this, but I'm not sure about how well they work. Also, would loading alternate ROMs then cause the Wi-Fi calling capability to be lost?
2) Buy the Google developer version of the GS4. It presumably provides tethering like the Nexus S, but wouldn't have the Wi-Fi calling. Will that be impossible to add later as it was with the Nexus S, or is the GS4 Google version close enough to the T-Mobile version that somebody could port the app?
Advice or suggestions?
Devs have been trying to get WiFi calling going for quite some time. It's closed source and tied into T-Mobile somehow. I know its very complicated. It sucks because I'm used to aosp ROMs but I can't give up WiFi calling because my service is so terrible at home/work.
I know developers are still working on it. If they can get the sensors, ir blaster, and WiFi calling on AOSP I'll never look back. Given the fact that the Nexus GS4 will be Vanilla Android I'm almost positive carrier apps won't be installed. If they don't have the sensors working it'll be a downgrade from tw in my opinion.
Sent from my SGH-M919 using xda premium
The problem with porting WiFi calling to non stock ROMS is that the APK requires all sorts of libs to be installed with it.
It's been done before though. CM7 and CM9 releases for various devices had WiFi calling once the lib situation was figured out. And it worked great.
For other devices it was a matter of pulling the APK and the associated libs from a stock rom, keeping everything to still be recognized as though it was installed on the stock ROM, and putting it into a CM rom.
It was accomplished before. I'd be shocked if it doesn't get accomplished again.
XDA Devs are smarter than Carrier Devs!
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.
Unfortunately this seems to be turning into a tired question that gets asked at least once a year (under different circumstances or requirements I guess), so happy 2015! The included Verizon tethering app seems OK, but I miss some of the tethering apps I used to use back in Gingerbread that would do things like restrict clients and show current upload/download speeds in-app.
At any rate, I currently have the tethering option from Verizon, and I'm rooted, so hopefully I'm pretty compatible with most of the apps out there. My issue with what I've found so far though is that there's a category of root apps that bill themselves as very hacky workarounds, and most of which haven't been updated in years which makes me a little hesitant to install on my device. Then there's another category of apps, both free and paid it seems, updated somewhat recently, but having even less features than the Verizon app, and/or most user reviews state to the effect that they do not work or are in general awful.
To help shorten the list, I've tried FoxFi, which was not so good imo, and I guess that would eliminate PDANet as well since I believe that requires a USB connection. Also, I'm looking to move away from the native Verizon tethering app.
So I guess this is a sort of "what are you using" topic, and are you happy with it?
Thanks for your input!
Just giving this a bump to see what you guys think.
At least for AT&T's tethering restrictions, flashing any custom ROM (that corresponds with your firmware) will do the trick. Or even any stock ROM that isn't carrier branded to Verizon or AT&T (most other carriers and regions have no such tethering restrictions).
I wasn't that impressed by FoxFi or PDANet either back in Gingerbread days. They seem needlessly complicated, compared to just going to the built-in HTC WiFi tethering setting and turning it on.
redpoint73 said:
At least for AT&T's tethering restrictions, flashing any custom ROM (that corresponds with your firmware) will do the trick. Or even any stock ROM that isn't carrier branded to Verizon or AT&T (most other carriers and regions have no such tethering restrictions).
I wasn't that impressed by FoxFi or PDANet either back in Gingerbread days. They seem needlessly complicated, compared to just going to the built-in HTC WiFi tethering setting and turning it on.
Click to expand...
Click to collapse
Yeah, maybe there's some sort of "just right" when it comes to complication that isn't out there right now. I gave in and downloaded a few root-requiring apps so I'll be giving them a run later today.
Well, I gave both Barnacle and the Wifi Tether app a try - sadly, it seemed that neither could properly control the wifi radio to get it broadcasting. Also, it seemed that both would cause the system Wifi Radio controller to glitch in that I could not toggle wifi anymore after using those apps unless I rebooted my phone. 0 for 2!