Hello All-
HTC Rhodium 400 running on the sprint network. Installed Android build FRX 07.1, everything works very nice and is great to have this on a WINMO phone! However 2 issues.
1) WIFI hotspot will turn on and is located by other devices, however cannot turn this off. The phone fights itself and then either reboots or locks up and i have to remove the battery and reboot into Android.
2) Every once in a great while the phone when left unattended will reboot itself back into windows.
Last night. 11/09/11, i installed the newest kernal, hoping this would possibly fix the problem. Still present, any help?
I have searched the threads but nothing this unique!
Thank you in advance!
YES I AM A NOOB, thank you for moving the post and Sorry for pissing off anyone, sometimes it gets overwhelming to move through all the posts. Thank you again for the 3rd party app that you stated and will just keep downloading the latest kernals. Thank you again moderator for answering the questions of mine.
Wrong section, moved to the right one.
1. The built-in wifi hotspot is broken, that's a well-known issue. Please search before posting a new thread (or even creating an account ). If you use a third-party tool like XDAndroid wifi tethering, should work just fine. The built in USB tethering works great too.
2. A part of running the port. Kernel isn't flawless.
arrrghhh said:
Wrong section, moved to the right one.
1. The built-in wifi hotspot is broken, that's a well-known issue. Please search before posting a new thread (or even creating an account ). If you use a third-party tool like XDAndroid wifi tethering, should work just fine. The built in USB tethering works great too.
2. A part of running the port. Kernel isn't flawless.
Click to expand...
Click to collapse
Could you please let me know the lastest kernal 's flawless than previous kernal?.
I 'm wondering if I update the new kernal , my data ( contact, apk....ect ) will be changed or not?
crownvn said:
Could you please let me know the lastest kernal 's flawless than previous kernal?.
I 'm wondering if I update the new kernal , my data ( contact, apk....ect ) will be changed or not?
Click to expand...
Click to collapse
You can update your kernel without losing any data. Just don't touch the data.img, update per Incremental Updates
arrrghhh said:
Wrong section, moved to the right one.
1. The built-in wifi hotspot is broken, that's a well-known issue. Please search before posting a new thread (or even creating an account ). If you use a third-party tool like XDAndroid wifi tethering, should work just fine. The built in USB tethering works great too.
2. A part of running the port. Kernel isn't flawless.
Click to expand...
Click to collapse
I used the built-in wifi hotspot at the end of October, and didn't notice any problems. What was I doing wrong (or right)?
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844
Hi Guys,
I'm all shiny and new to this forum, so let me introduce myself real quick. My name is Saragn, I'm a security engineer from South Africa and I recently decided to start modding my HTC One M8. I produce music professionally in my spare time and have released music internationally under three different genres on various labels. I love tech and love playing with anything that is powered and has lights ha ha ha...
So, on Friday I installed the following ROM from Skydragon: "SkyDragon M8 v 3.1 WWE Sense 7.zip". It works REALLY WELL, I love how it has opened up the phone for modding. The only gripe I have is the wireless hotspot function does not work anymore. If I try enable it, it simply flicks between on and off repetitively. It is as if it cannot switch on. To stop it from doing that I have to enable the wireless, it then stops and the wireless enables. If I try switch on the hotspot again it does the same thing. I've re installed the ROM twice now and each time it does the same thing.
Firstly, apologies if this is the wrong part of the forum to start this thread, if so, please could one of you be so kind as to point me in the right direction? Thank you.
If it is the right place to post this question then some guidance would be highly appreciated. What can I do to get the wireless hotspot feature to work again? Thanks!!
Ciao for now,
Saragn
Try updating the ROM. Skydragon Sense 7 is now on version 4.1
Changelog for version 4.0 says "Fixed Wifi-HotSpot - may not work, will provide fix zip asap"
http://forum.xda-developers.com/showpost.php?p=59633002&postcount=3
So apparently this is a known issue. But some folks report that WiFi hotspot (tethering) is working. Seems to be working for me on version 4.1, but I haven't testing it extensively.
Saragn said:
So, on Friday I installed the following ROM from Skydragon: "SkyDragon M8 v 3.1 WWE Sense 7.zip". It works REALLY WELL, I love how it has opened up the phone for modding. The only gripe I have is the wireless hotspot function does not work anymore. If I try enable it, it simply flicks between on and off repetitively. It is as if it cannot switch on. To stop it from doing that I have to enable the wireless, it then stops and the wireless enables. If I try switch on the hotspot again it does the same thing. I've re installed the ROM twice now and each time it does the same thing.
Click to expand...
Click to collapse
There was a fix posted for v3.1 : http://forum.xda-developers.com/showpost.php?p=59521467&postcount=2666
But it is advisable to flash a new updated ROM v4.1 : http://forum.xda-developers.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378
You'll have better experience with the updated one
Hi,
Thank you very much for the feedback. I'll try out 4.1 as per your suggestion. I'll let you know how it goes.
Regards,
Saragn
ckpv5 said:
There was a fix posted for v3.1 : http://forum.xda-developers.com/showpost.php?p=59521467&postcount=2666
But it is advisable to flash a new updated ROM v4.1 : http://forum.xda-developers.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378
You'll have better experience with the updated one
Click to expand...
Click to collapse
Hello mate....quick update for ya. Installed 4.1. Hotspot works now. Thank you
ckpv5 said:
There was a fix posted for v3.1 : http://forum.xda-developers.com/showpost.php?p=59521467&postcount=2666
But it is advisable to flash a new updated ROM v4.1 : http://forum.xda-developers.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378
You'll have better experience with the updated one
Click to expand...
Click to collapse
Hi there...Okay so another update for you. The wireless hotspot switches on now, so I thought it would be okay. It isn't. Even though it switches on and accepts connections, what ever end point I connect to the hotspot cannot browse the Internet and while the hotspot is on the phone itself cannot connect to anything so it seems that enabling the hotspot disconnects the phone from the Internet. I am not sure if you guys have picked this up yet on 4.1 ?
hey guys, I need some advice or assistance with a wifi issue on my D855 32GB, running Fullmics 6.1.
The issue is, every time my device goes into deep sleep, is inactive for a lengthy period, the wifi connection becomes dormant until i wake the device. Also, if i enter another area of saved wifi connection, I have to wake the device in order to get connected. For example; if I leave home wifi and enter work wifi I will not connect until i wake the device and vice versa (work wifi to home wifi no connection until device i awoken)
Please, can someone assist?
I did posted this before, got some answers saying it maybe marshmallow/doze related. If so, how do i make adjustments?
P.s. I tried several ROMs and same issue, however, when i first got my device, stock everything (Lollipop), the issue was non existent.
many thanks in advance fellow xda members.
grymmy said:
hey guys, I need some advice or assistance with a wifi issue on my D855 32GB, running Fullmics 6.1.
The issue is, every time my device goes into deep sleep, is inactive for a lengthy period, the wifi connection becomes dormant until i wake the device. Also, if i enter another area of saved wifi connection, I have to wake the device in order to get connected. For example; if I leave home wifi and enter work wifi I will not connect until i wake the device and vice versa (work wifi to home wifi no connection until device i awoken)
Please, can someone assist?
I did posted this before, got some answers saying it maybe marshmallow/doze related. If so, how do i make adjustments?
P.s. I tried several ROMs and same issue, however, when i first got my device, stock everything (Lollipop), the issue was non existent.
many thanks in advance fellow xda members.
Click to expand...
Click to collapse
I had/have same issue since first MM version of Fulmics, it was never fixed. You said you have it on other MM ROMs so I wont point fingers at Fulmics dev since not all users are experiencing it.
Things I tried to do to fix it:
NatusVincere said:
Yap, had the issue while I was on Fulmics.
Made my device useless since it repeated almost every time I turn off the screen so I had to drop this ROM and go to AOSP/CM based.
I tried changing modem to multiple versions, tried delaying doze, tried multiple kernels, tried same as you disabling app optimizations as well.
Click to expand...
Click to collapse
Only possible alternative solution instead of switching ROMs is to make device use internet connection full time, to make it never go to deep sleep.
Perfect app for that would be:
https://play.google.com/store/apps/details?id=com.nhiemhk.keepinglightconnection