For a while not my hotspot feature has been failing. It toggles without throwing an error but is obviously not working as I can't see it from other devices. Sometimes rebooting will get it to work for a while but it is never reliable. I've used a 4.3, 4.4.4, and now 5.0 roms but the problem has remained consistent. I do not think it started with flashing a modem but I can't remember the last time I flashed a modem on the device. Is that a potential fix or does anyone else have a recommendation? Thanks.
android 4.4.2 has a working wifi hotspot. i noticed the behaviour on 4.4.4 as well
Sent from my LG-E980 using XDA Free mobile app
I was really hopeful that someone would have a quick 1-2 punch for this one. Do the CM ROMs include a modem or is it smart to flash a modem after flashing a new ROM? Anyone have any thoughts on this?
Related
Hey guys,
I've clicked around a bit but can't seem to find anyone with the same issue, and I went through about 40 pages on Calkulin's ROM but I really don't want to go through all 200 and some if somebody here can provide a solution.
I've used his ROMs for the past year, really fantastic, no complaints at all. I flashed his beta ICS build a few months ago and it worked well with the exception that it would randomly reboot for no apparent reason. I could be in the middle of a text message or it could be sitting on my desk and all of a sudden, reboot. I went back to his old ROM and decided to put off ICS for a few months to work out the bugs. Today I put his newest ICS ROM up and once again, random reboots. It doesn't seem that others are having the same problem so I'm not sure what to make of it. And for the sake of putting it out there, it's always a clean install - Format All, flash modem and ROM.
Anybody have any ideas? Suggestions? Any help is seriously appreciated.
Thanks guys.
Ive heard of someone else having this issue before have you tried a fresh install with a new download of EL29 or EL26? When i have had issuez in the past that could be the culprit try a new download also you could try one of the new kernals posted that may help as well.
Sent from my SPH-D710 using XDA
Are you using 4g?? This is a known issue with leaving 4g enabled.
Sent from my SPH-D710 using XDA
It is a known issue that if the hacked Hotspot is installed and you are running on 4G that you will experience random reboots. Mijjah74 has implemented a fix for it in his ROMs and it is beginning to go out among the other developers as well.
Until your developer implements the fix the cure is to not use 4G.
Awesome, thanks a ton. What a goofy bug. Yes I frequently use 4g, hourly even, and although I rarely use the hot spot, it is installed. I wonder if un installing it would fix the issue.
Thanks again.
Any idea if using am older modem would fix it?
iJoshh said:
Awesome, thanks a ton. What a goofy bug. Yes I frequently use 4g, hourly even, and although I rarely use the hot spot, it is installed. I wonder if un installing it would fix the issue.
Thanks again.
Any idea if using am older modem would fix it?
Click to expand...
Click to collapse
No, reinstalling won't help. I was testing 4g for this and (for me at least) it would reboot at about exactly the 1 hr mark if 4g is running constantly. Pretty strange but it did it several times in a row that way. I think someone said that they have the timing down pretty well and I can't recall exactly what the recommendation was, turn 4g off and back on right before it's going to reboot (you should time yours to see when it does it). Something like that.
Addendum: FYI, I'm running stock EL29 modem. A different modem won't change the 4g reboot issue either, sorry.
I had random reboots on every ROM. I went all the way back to stock unrooted, and started back over. Haven't has any issues since.
Sent from my SPH-D710 using xda premium
Hey guys! I'm new to the Galaxy Nexus and I'm concerned with the Wifi Tethering app. I don't know if it's related to the Galaxy Nexus itself, or if its my network here where I live but I'm just seeing if anyone else is having any issues? I'm currently running 4.1.1 STOCK rooted. What are you guys using as far as apps? I used to have a T-bolt with the same Wifi Tether app and it rarely ever just stopped working. It says I'm connected but it just doesn't load any pages or work at all. Is there any solutions to this? I've read that I'm supposed to use the Native app (portable hotspot) but it doesn't work since I'm not subscribed. I really actually like the stock rom and it's feel and I don't want to have to flash a custom ROM. I will, IF I have to but I prefer to stay stock and stable. Any help would be great!
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
I'm just trying to keep these straight, since I've seen bits and pieces of various problems on the various dev threads. Would someone be so kind as to check my logic here? Thanks in advance!
Problem: Can't get a GPS lock after flashing any AOSP-based 4.3 rom
Solution: Flash back to stock (RUU?), open up Maps or otherwise get a good GPS lock, flash back to your rom of choice
Burning Question: Why does this happen and why does stock flashing work?
(Idiot Newbie Question: RUU is basically a stock image? I need an encrypted version? Do I need to worry about breaking my rumrunner s-off/root?)
Problem: When on a phone call, and the other party hangs up, you get "call lost" instead of the standard graceful disconnect.
Solution: Isn't one yet. Gotta wait for a fix to be made.
Problem: Signal strength meter shows impossibly low values, despite data, voice, LTE all working as expected.
Solution: No idea. Of the 3 roms I've tried, (CM10, Liquid, Carbon), all do this. Minor problem, but anyways.
Problem: Purplish tint on the camera in dark scenes.
Solution: Phone's defective, send it in. / Or: Wait for a software patch.
Which is it?
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
adrenalinemotion said:
Is the issue with AOSP roms killing the radios on certain phones fixed as of the 11th?
Click to expand...
Click to collapse
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Flyhalf205 said:
That isn't AOSP fault. Something was happening after the s-off procedures that people need to do a factory reset from HBOOT before flashing anything to reset their radio
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Does one need to have the stock recovery to reset from Hboot?
Sent from my HTC6500LVW using Tapatalk now Free
Flyhalf205 said:
@Karunamon
Problem 1. Not really figured out yet. All you need to do is flash any Sense rom.
Problem 2. Is fixed! For a couple of days now for any ROM built after 11th of this month.
Problem 3. I get the same dBm on Sense and AOSP. Sure a lot of other people do also. But people panic when looking at the network bars.
Problem 4. I get no purple/pink tint when on Sense but after flashing AOSP I get the purple/pink tint on my FFC. So I would wait til 4.3.
Click to expand...
Click to collapse
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Karunamon said:
Excellent, seems I just need to dig up a sense rom and then reflash something new and i'll be good on 1 and 2.
Any idea what could be causing 3, though? For comparison, when I was on stock, the meter was completely full for LTE in my home. Now, it's one bar. Coverage is still good though and data still works at breakneck speeds, so I don't think it's an actual signal issue.
Click to expand...
Click to collapse
check DBM isntead of looking at your bars to see if you even have an issue.
The signal issue sounds the same as AOSP on the Rezound. The signal strength would be same, but the signal icon would be different. Basically, HTC has set the icons to show more than AOSP.
I didn't factory reset after using rumrunner and the only thing I have noticed was I would not connect to 4g as much or as fast as before. It seems to be getting better though. I am running bonestock.
Sent from my phone using an app
Like it was explained to me the bars are kinda like the idiot lights on a cars dash. They really don't do much. Aosp shows your true signal and sense and so on shows a false truth just so people doesn't complain about poor signal. As long as my data works I don't care if I have zero bars.
Sent from my M7 using Tapatalk
Are there any bluetooth issue's ?
nujackk said:
Are there any bluetooth issue's ?
Click to expand...
Click to collapse
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
IR work yet?
exzacklyright said:
IR work yet?
Click to expand...
Click to collapse
IR is working on VanirAOSP.
I'm using Smart IR Remote to control my devices; great interface and works well with the majority of the stuff that I have.
Not sure what the progress is re: IR with the other AOSP ROMs.
With smart ir remote it should work on any Rom.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
sawedust said:
No issues using a Bluetooth headset here.
Can't say anything about Bluetooth audio streaming, haven't tried that yet.
Click to expand...
Click to collapse
The streaming is my main concern, Use is inmy truck and main reason I will try to keep my unlimited data FOREVER
adrenalinemotion said:
I s-off'd, unlocked my bootloader and rooted with no issues. I was stock rooted and everything functioned. As soon as I flashed an AOSP rom, the radio broke. I had data, but no voice. (You posted in a thread I started and helped me fix my radio)
I'm not trying to argue or anything, just trying to understand.
Are you saying that I should now be able to flash an AOSP rom and have no radio issues now since I reflashed the stock recovery to fix the radio, then flashed back to TWRP?
Click to expand...
Click to collapse
Did this happen using twrp or cwm? Some folks are thinking its cwm causing this.
Sent from my HTC6500LVW using Tapatalk
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Flyhalf205 said:
I really think you can go back to an AOSP rom. I have no problems and tons of other people with no problems. I noticed that the guys who s-off with sonic didn't have these issues. That is just why I think it is something with the whole current s-off process.
But if you do decide to give AOSP another try. I would flash when you have about a hour of free time with a computer just to make sure it doesn't crap out again.
Click to expand...
Click to collapse
This happened to people who hardware s-off'd and flashed the gpe rom too. Don't think it has anything to do with it.
Sent from my HTC6500LVW using Tapatalk
So I bought my note 2 a month ago and the guy who had it before me had been running a liquid smooth rom. And I put on clean rom 5.0 since then the wifi has not been working. I have found some people that have had a similar issue. But I can't find any bring on the Web for any type of fix or sure fire way of getting it to work again. Aside from flashing a bunch or roms and kernels does anyone know of a fix or trick or rom that has sure working wifi? Preferably success when coming from a broken wifi rom
Sent from my SAMSUNG-SGH-I317 using Tapatalk