Related
My wifi won't start. Whether it's through TouchFLO's comm manager or Window's own Wifi connection, it will give me the "Busy" rotary and then nothing happens.
I know exactly when the problem first appeared, though. I was using WMWifirouter (an ancient version, .8 or .9 something) while it was tethered to a Macbook for power (I think on ActiveSync, but I don't remember). From what I gather, that might not have been a good idea, or, rather, that theoretically should not have worked. But, it did. I disconnected the phone, and since then I've had the aforementioned wifi issue.
I've searched XDA and Google, and it seems the best answer I can find is to hard reset and see if it works. However, it seems that for a large majority of people who tried this method, the problem doesn't go away.
I'm hesitant to try a hard reset, as my HD's been working fine for the past 5 months and I've got a lot of time and work put into it, when it might not get me anywhere.
Hence, I'm asking if anyone's come across a solution to this problem that might work. I'm hoping it might be as easy as a registry tweak (I have seen some "solutions" that involve the registry, but they don't appear to apply in this case).
Since I'm in the US, and the HD is not officially provided by any carriers, I might have a lot of trouble getting any kind of warranty work done on it, and that also entails losing the phone for 2+ months, as best I can tell.
I might try flashing a newer HTC ROM, although I would be pretty mystified that my old ROM suddenly wasn't good enough. Maybe it's just that a new factory ROM would place the correct registry settings back in order?
Sorry for the long post, I'm just frustrated that I am unable to use wifi and that I'm starting to think the only solution will be to get a new phone or live without it.
Does anyone have any thoughts?
(I've looked at several threads on XDA already, none of them were at all resolved or even directly discussing the HD, so I think it's okay to post this thread.)
EDIT: I could tell I was going to get no response here, so I just went ahead and hard reset the device. That seems to have fixed it, for now. Wifi's working how it should. I'm adding this edit here for anyone else has this problem.
Just a bump, and also to add that when I run WMWifirouter with logging, it shows that it fails to Rebind the WLAN and also the CM-Set fails, if that is any clue.
Another detail, I notice that under Settings > Connections > Wi-Fi > Advanced > Advanced, there is nothing under Status, MAC, IP...I'm guessing that will always be empty if it's not connected? If not, are there values I should fill in?
So I was trying to get the new 2.3.20 firmware and I went to the Archos website. But it looks like there was a new firmware posted this morning. 2.3.26.
I don't know how to direct link, but i'll try.
http://update.archos.com/8/gen8/gen8_2.3.26/firmware_archos_android_gen8.aos
Version 2.3.26 - April 21st, 2011
Wi-Fi: fix cannot scan on an access point above channel 11 regression
Phone tethering: fix TCP/IP header compression setting crash
System stability: avoid Android reboot in case of missing audio
Media library: fix media libray not updated on hard drive based A70
Notification: decrease low battery notification volume
Application: attempt to solve Pandora application not able to switch songs
Application: solve music lag in applications using OGG format
Bluetooth GPS: increase compatibility with 3rd party applications
Display: avoid white/black screen happening sometimes when switching back the display on
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Techngro said:
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Click to expand...
Click to collapse
Not that much of a noob, you posted the link to the firmware that should end my buggy horrors
Thanks jknut for the changelog
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
sw6lee said:
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
Click to expand...
Click to collapse
I just followed Steps 2, 3, 4 of Chulri's post. Chulri already has the new files for "fw 2.3.26 +rw" for Step 3. I like the optional Step 4 because I don't have to worry about holding down the volume button everytime I boot to get root.
Hi,
Has somebody tested this new release?
I updated to version 3.2.20 last week and I was very happy when I realized that cinema plugin was not required to play all the formats which I was not able to before the update (AAC, AC3, MPEG2, etc)
Can somebody confirm if this has not been "fixed"?
Thank you.
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
toyface said:
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
Click to expand...
Click to collapse
I just noticed the update when I went to the archosfans 2.3.20 bugs thread to report wifi drop powersave disabled while running tunein radio...
OTA update went fine, just waiting for A43 to charge up, then I'm going to do the A32 as well...
[EDIT]
Power LED blinking -> UI batt meter (and About Device) say 98% charge...
had this once with 2.3.20 showing 97% when LED blinking but next charge and thereafter showed 100% when LED blinking...
[/EDIT]
I had this Problem from the first day.
LED blinks and the battery show around 90%.
If i unplug the power the status goes to 98-100%, most 100%.
If i reboot the device with plugged power, the status is 75-90% after restart.
Sometimes the status falls to 87-91% if i plugged the power in.
I can live with it, but it is annoying.
did they remove bluetooth PAN tether ? I had dun/pan option while setting up BT tether with 2.3.20. but now no more that option. the probken for me is, i am using cdma phone(bell htc touch) but with BT DUN the Archos cannot dial CDMA number #777. I set bell APN (pda.bell.ca) it's not working. Actully even if it works I worry about it because it may charge me more.
Before with 2.3.20 , it worked perfect with BT PAN and my phone set to Internet sharing.
This update cleared up my waking-up issue.
It's pretty much an instant on now after the monitor idles off. Before, (after being off for more than a few minutes) it was a crap-shoot as to whether or not the screen would come on and I often had to fight with it and double, triple, quadruple tap the power button to get things alive. No longer.
still reboot cycles problems when charging the 101..problem started with these last 2 updates.
twit.tv app FCs all of the time with this fw...
I wonder why they released this one OTA as it seems to be more broken than .20 was...
youtube and many other flash video played in the browser hangs after about 15 seconds or so. Soemtime this causes the whole system to freeze requiring forced reboot.
This is the worse build so far, my A70 was most stable at 2.1.08.
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Techngro said:
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Click to expand...
Click to collapse
As a matter of fact I did an Android reset to get away from some of the problems I was having with bootloops and such. This has helped with the general performance of the 101, which I'd say is down to the 64mb swap file I now enjoy.
I did have a couple bootloops until I enabled a lock screen pattern unlock and I have now experienced nothing but fairly good performance
It seems that 2.3.26 is different from vesions before
Need more language for External Keyboard Layout such as Thai
jakkrith said:
Need more language for External Keyboard Layout such as Thai
Click to expand...
Click to collapse
You'd probably be better off posting in the archosfans.com forum's bug list thread for 2.3.26 as Archos employees actually monitor that site and have actually even started some of the buglist/fw release threads... i.e. I'm not sure that they're even aware of the xda-devs gen8 section and even if they were would they bother to read it...
Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
A friend of mine has the same problem, Im pretty sure thats a hardware issue already. !
running gb 2.3.6 #4 - still no wifi/bluetooth
Having the same issues. Does anyone know if wifi and BT share an antennae?
try flashing a differnt radio? for your phone specs
look in ihop thread or fruit cake thread for your radios
r0nz3y said:
Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
Click to expand...
Click to collapse
schufly73 said:
Having the same issues. Does anyone know if wifi and BT share an antennae?
Click to expand...
Click to collapse
I'm pretty sure this is a hardware issue... I have been having this problem myself, and have tried flashing many of ROM and Radio's since it has reared it's ugly head - all to no avail. The WiFi an Bluetooth do share the same Broadcom chip... maybe there's enough of us experiencing the problem that we can collaboratively order a dozen of these things (they only seem to sell in bulk).
Had the same issue, ATT had to replace the phone.
Any more news on this issue?
Same thing happened to my Atrix last week (Bell, 2.3.6, locked bootloader, unrooted).
Same here
Same problem on my original Atrix, which was replaced under warranty by AT&T six months ago. Recently my replacement Atrix has been having the same problem. Wifi won't enable and frequent reboots.
Although the phone should still be under the 1-year warranty, AT&T refuses to honor it because the screen is cracked (so much for Gorilla glass).
After getting two phones with the same problem, and hearing about countless others having the same problem, and getting screwed out of the warranty, this is definitely my last Motorola phone.
EDIT:
The "fix" that was originally posted here doesn't actually work. I'm almost certain that this is a hardware problem. As of now there is no software fix, if one even exists.
Check this thread for more info:
https://forums.motorola.com/posts/0c2f1387d6
I recommend that you post to acknowledge you have the same problem.
i tried the script and it tells me "oops... did NOT find wpa_supplicant.conf! any help?
cafe. said:
I found a permanent solution to the problem. It was probably more obvious than I originally thought it would be. This is probably what will fix it if you recently ran some sort of 3G tweak as it probably damaged/corrupted /data/misc/wifi/wpa_supplicant.conf. Before I get started with what what problems my phone was having:
-'Wifi Error' message when enabled
-Random reboots when trying to enable wifi
-Bluetooth worked fine (and if you are having issues with bluetooth it may be due to a similar bluetooth related file having problems)
-Impossible to fix by flashing new roms, wiping/factory reset, and virtually every other possible thing I tried
So, just before giving up, I found something called 3Gturbocharger--which can be downloaded from here: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 REMEMBER: IT'S 3GTURBOCHARGER, NOT ANY OF THE OTHER SIMILARLY NAMED FILES.
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
I'm assuming that in your case the bluetooth equivalent of "wpa_supplicant.conf" was corrupted. Possibly /data/misc/bluetooth/dynamic_auto_pairing.conf or /data/misc/bluetooth/incoming_connection.conf. Worth a shot trying the method I described on those files as well. Try it out, you've got nothing to lose.
Click to expand...
Click to collapse
im getting that to
My Atrix wifi stopped working in the past, but started working again. It currently stopped working once more, giving me an Error if I turn it on. The Bluetooth has never had issues and still works, I am a month past warranty but with unlocked BL it doesn't matter anyway. This seems to be a slight issue with these phones unfortunately.
I could live with the phone without wifi, but the constant reboots are unavoidable. I notice that when I originally boot the phone, if I use it and keep the screen on it works, but as soon as I turn the screen off, it reboots. Odd to me.
Ya I have the Bell Atrix myself and I'm still on Froyo because of complaints of GB. (especially battery life) Maybe I'll do ICS, but I'll wait for some reviews since its not that easy to go backwards as say my OG SGS...
Sent from my MB860 using xda premium
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
Click to expand...
Click to collapse
Anyone try doing this manually? I can't locate the file.
wpa_supplicant file
hi, the file is in etc/wifi and the bluetooth file is in etc/bluetooth/ i renamed the .conf files but this don't solved the problem.
For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.
yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.
can anyone provide a flashable patch to try? Thanks
This problem is starting to annoy me really badly D:
I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.
This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5
Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133
Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.
A little help please from a rom specialist!
Using a cfautorooted note 3 for a couple of years with no problem. Suddenly the wi-fi will not switch on, the icon showing light green for 1/2 second then grey - using the slider if it is held to the right, there is a light green light, but releasing the slider it returns to off. Nothing was updated/changed. The bluetooth works fine so do not suspect chip yet. Booted to safe mode - no different. Investigated files etc. and noticed that wma_supplicant.conf had been reset to zero bytes at the time this happened, so restored from a back up (Keep copies as has "lost" all wifi passwords in the past" - powered up again and worked!
Today it has returned to this fault.......but the wma_supplicant.conf is the same.....but noticed this time that pgp_supplicant.conf had be modified at around the time of the fault, but I do not have a backup.
Can anyone explain/help with exactly what these files do and which files are essential to connecting android to the hardware.
I have spent a lot of time looking into this, but do not want to factory reset just yet - will take days to re set up as I wish - and only guess it will resolve problems. Also as engineer I prefer to "find the fault and repair" rather than just "fix" without knowing how!
ANY clues would be gratefully accepted.
I also have a note 3 (same model) on android 5 but not sure if the /system/etc/wifi files should be the same. Otherwise any clues where I can get the original UK 4.4.2 rom?
Many thanks
John
UK
ps
I realise that wpa_supplicant.conf is technically just the passwords, so why this worked 1st time I do not know - maybe a coincidence.
an entry says ctrl_interface=/data/misc/wifi/sockets
but that directory is empty in case that helps!
where I can get the original UK 4.4.2 rom?
Firmwares sammobile or samsung-updates and other sources including this forum .
Thansk, but tried Sams and uk version not there. Couldn't find anywhere else so would be nice to extract from existing 'phones rom as correct version. Still looking for how to!
Also would like to understand the wifi set up and repair this issue, rather than use blunt force and just do a factory reset (plus will take a day to rebuild as I want!)
John, UK
Does it have to be "UK version"? It is necessary?
I am from the Czech Republic. (Central Europe ) I have "N9005XXUGNG1_N9005ETLGNG1_N9005XXUGNG1_HOME.tar.md5". It's Android 4.4.2. I can upload to any repository. You want? Not a problem...
EDIT-link:
https://ulozto.cz/!QJJTWod0ZbHe/n9005xxugng1-n9005etlgng1-n9005xxugng1-home-tar-md5
Hi
What a coincidence - I returned from Czech Republic last night at 23:00 !!!!
I live half the year in Velehrad, Okres Zlin!
I will get back to you tomorrow.....I am trying to locate another master circuit board for this device, but first I must try a factory reset and cache clear - been putting it off as will take 7-8 hours to set up again and remove all the rubbish apps!
John
Nice.
You can try my link. (Rom 4.4.2)