yashsingh1/xdaforums huggingface dataset:
[Folio 100 General] EulerVen:
With Topogigi we have isolated that only hangs after screen lock/sleep, then wake-up, then wifi reconnect and after a while (5/10 min) usimg net connection, folio freezes. But if you do not use net (disconnect wifi, because if wifi is connected, sync can freeze it), folio works fine all the time you want.

Of course, it's very annoying because practically all apps connect to net.

Thats the tests we've done. Perhaps that help:
[Folio 100 General] BeRo1985:
WiFi is at me "completely" off/disabled (at the almost time), so that your here described issue is maybe a different issue than mine :)

And I had already two other folios (from fully different webshops), which had exactly the equal identical issue like my current third folio.
[Folio 100 General] EulerVen:
Then the only answer I can manage is that different hardware versions have different issues with the same drivers (1.4 mod). Amazing!
[Folio 100 General] Topogigi:
Check your dmesg: the kernel panic is caused by ar6000 module that is wifi. It's always the same story...

EDIT: I made another test this morning. I fired up a terminal emulator, logged as root (su), then removed ar6000 module with "rmmod ar6000". Wireless connection stopped imediately and I tried to put the device to sleep. At wakeup, I started wifi (need to do it twice, the first time it gives an error), but then I could work with my tablet without hangups. Wireless network became very slow (speedtest.net takes an age to load), but the tablet was fully functional. I'm really convinced that something net related is causing all the hangups. And....I don't use SD at boot (that's another story), so no hangups with the screen lock.
[Folio 100 General] headblow:
In my case, I was unable to use my Folio for more than 30 min.

I can only confirm that from my observation it is related with wifi and wake up.

Its always the same, after reboot it works fine till first wifi disconnection (in sleep mode or during normal operation), and when it will connect again, after 5~10 min device freezes, always.

Besides, when I was using EZ File Explorer and I preform a search of SMB shares in network device freezes, the same was when Ive started FTP server on Folio, and I was trying upload a large file to built in SD (without earlier disconnection).

But right now Im able to work on device without hangs for few hours using following (temporary) solution:

Ive changed settings of a screen to: always on

Ive downloaded "Screen off" widget from techvision (that Topogigi mentioned in other thread) and when I want to have a brake, I use Screen off shortcut.

Ive downloaded Repgon WIFI keep alive, and configure it to always keep wifi connection on.

So with above mix of solution it works better, but still when wifi will disconnect it will hang. This temporary solution also shorten battery life.

But at least I can use it now.

Regards,

headblow
[Folio 100 General] Topogigi:
I think we are narrowing the research: I can suspend the device now without side effects manually removing the ar6000 module with rmmod and reloading it with "insmod /system/wifi/ar6000.ko" at wakeup. With a "netcfg wlan0 up" the tablet reconnects to wifi on a regular basis, but connection is really slow after this (but no more hangups downloading a 10mb file). I'll go further with experiments.
[Folio 100 General] BeRo1985:
Sorry, it's not correct. The "Modules linked in:" line shows only the "loaded" kernel modules to the kernel panic time, but not the modules, which has raised the kernel panic.

And as said I will do more researching at lowlevel debugging as far I get the time for it.
[Folio 100 General] Topogigi:
Sorry, but I'm only arguing that the module is loaded, so the kernel panic (it's my theory) is due to the module. Try to unload the module and let's see if the kernel panics anymore.... :-)
[Folio 100 General] BeRo1985:
My preliminary research results:

nvos_ioctl calls NvOsSemaphoreDestroy in mach-tegra/nvos/nvos.c, which calls sem_handle_search in in mach-tegra/nvos/nvos.c, and at least this sem_handle_search implementation seems to be the final trigger of the page fault (but sem_handle_search must not be the culprit of it too).

sem_handle_search does binary tree search with the semaphore handle as search key, and if a binary tree node contains a invalid node-next-left or node-next-right pointer, then it will trigger this memory access violation or better page fault kernel exception.

And since nvos_ioctl refers to the user space, because nvos_ioctl is located in the mach-tegra/nvos/nvos_user.c as link to unlocked_ioctl in the nvosfops

file_operations structure, which is used by the ioctl user space API calls and/or user space syscalls. So the real culprit must be "maybe" found from there in user space.

Hence my two suspects in addition to the kernel are now: mediaserver or nvrm_daemon maybe together with a multithreading-code-on-multiple-cores-synchronisation problem.

Unfortunately, the Folio has probably no JTAG, to debug it together with printk on kernel level over a serial console. ADB is almost sadly useless here.

So to all hardware-hackers/hardware-freaks here, get/buy a folio, open and disselect it, and search for JTAG pins on the PCB board. That would be really helpful then.

As a small note: I'm a software developer with very strong high-level and very strong low-level-coding skills
[Folio 100 General] bastospn:
I am giving up on folio... I can't understand how someone could be happy with it. Lots of hardware and software problems and sure no great software or games anytime soon. Tegra 2 had a bad start. I really regret to say but apple had the upper hand here. Android is good but not good enough for using in a tablet. I would like to give thanks to everyone who had being working hard to improve folio.
[Folio 100 General] wonger:
@bastospn

Cheers. You're entitled to your opinion. :) Not that I'm defending the Folio here but I believe there are no Android tablets right now that are 'stable'. Of course, we are all constantly benchmarking tablets (Android, WebOS, et al) against the iPad. So, in that sense, Apple has it hands down over Android in this department for now. Agree! But I'd venture to say that this is because Android is a relatively new OS as compared to iOS.

Nevertheless, I guess it's just a matter of choice and preference over which OS to choose (and not so much the tablet).

Cheers~

wonger
[EVO 4G Q&A, Help & Troubleshooting] leo5111:
i used this http://xdaforums.com/showthread.php?t=838448 i installed htc sync drivers turned on debug and set phone mode to charge mode only like it says i ran as administrator says its trying to root says maybe to many apps running reboot, i reboot run task killer kill everything still says cant root? what am i doing wrong? thanks :confused:
[EVO 4G Q&A, Help & Troubleshooting] housry23:
Use this method: http://xdaforums.com/showthread.php?t=829045 ir works every time as long as you follow it to a tee. It is longer and requires more work, but it is definitely the most fail proof way.
[EVO 4G Q&A, Help & Troubleshooting] xHausx:
Usually a factory reset will help with that, either that or your antivirus may be picking up on the exploit. I forget which ones do it but some will pick up on that.
[EVO 4G Q&A, Help & Troubleshooting] leo5111:
oh ,ok so if you dont do a hard wipe sometimes wont root?? and can i use the factory wipe thats listed in the phone? thanks :p
[EVO 4G Q&A, Help & Troubleshooting] Papa Smurf151:
Just use unrevoked. Its the best and fastest and easiest way that I've found
[Nexus S Q&A, Help & Troubleshooting] aviramsegal:
Installed CM7-RC1

(After wipe)

Everything seemed to work until 2 hours later i noticed my GPS application can't get any data connection.

10-15 minute after that I had zero reception with the little X above it.

Had to reboot in order for the phone be usable again.

I really like CM7 but this is a real blocker for me.

I'm back on stock now but i want to give it another try.

Is there a reason that happened ?

If not, is there a way to provide error logs in case it happens to me again ?

Thank you
[Nexus S Q&A, Help & Troubleshooting] nxt:
I think this is a known issue (at least I hope so), I've had this issue for months, I'm on nightlies. Randomly lose cell signal until reboot, randomly goes into soft-reboot bootloop, randomly can't turn back on without battery pull.

-Nexus S
[Epic 4G General] vrojas25:
here is the web page its very simple thanx Yesterday, 04:43 PM

Fidelio_o :D:D:D:D:D:Dhttp://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
[Epic 4G General] NoSoMo:
Welcome to yesterday.......the partiers have all gone home already. There is beer in the fridge and some chicken in the trash.
[Vibrant General] sberic:
Please help.

thanks in advance.
[Vibrant General] krylon360:
SuperOneClick using rageagainstthecage will root it right up. :-)
[Vibrant General] roumenjr:
Here is the link: http://xdaforums.com/showthread.php?t=803682

It will work!

Cheers!
[Vibrant General] Andreal:
EDIT: you mean t959v? I didn't notice...

nwm
[Nook Color General] ringbolo:
I was having problem connecting to my Wi-Fi using CM7 RC1 & nightly's 1-3. I have a D-Link 655 using WPA/WPA2 PSK encryption. It would get stuck in a loop: scanning... connecting... disconnecting.... However, it would tether to my HTC Hero using WEP encryption and to open networks.

I googled and saw that others had similar issues with CM7 and tried some of their solutions (reboot router, set Nook Color Wi-Fi to never sleep) but it didn't work for me.

I went back to Cicada's Nookie Froyo 0.6.8 after each CM7 install because Wi-Fi was working great for me. I did some digging into 0.6.8 zip file and noticed that it has a "scripts" folder in "/system/etc/wifi/softap/" that is not in CM7 also there is an extra file called "tiwlan_drv.ko" in "/system/etc/wifi/" that is not in CM7.

I pushed the entire "wifi" folder from 0.6.8 to CM7 Nightly 3, did a chmod 644 on the individual files rebooted and I was able to connect to my wireless network. I am not really sure what worked specifically but I thought that I would share in case someone was having similar issues or could possibly explain what is going on.

I am really enjoying CM7 and I am grateful to everyone on XDA and to the CM guys for their hard work. :D

Wi-Fi Folder from Nookie Froyo 0.6.8 attached

MD5: 9A47EFD6C96DBA1074C341D98CC30D12
[Nook Color General] therealguppy:
Can you post a copy of that folder here so others can try it with out having to find rom to pull it from.
[Nook Color General] timekeeper:
Same, please - would like to give it a try. Had only two fields to fill in on a EAP/MSCHAPv2 university network on stock rooted (username and pass), but lots more options and not working on CM7.
[Nook Color General] bonobomidwest:
Well I've had no problem at all on multipel networks configurations, with CM7, and actually find it to be much more reliable than other installs. I have literally tried every possible config and they all work.

It doesn't make much sense for encryption to be responsible for the behavior your report (making and dropping connections).

1. Have you checked the network itself - e.g. use wifi analyzer, and look at the signal strength. You may be using a network that is in a crowded band, and adjacent devices may be trying to shout over each other (though the NC seems to generally be able to shout over my celphone). For instance, in my neighborhood almost everybody is on the default channels 1 and 6, which really cuts the range and signal strength of my wifi. Honestly you won't believe the improvement by switching to an empty channel.

2. Is you work network broadcasting over multiple channels? This is typical but it does mean that as you move around the building you will drop briefly as you switch from one router to another with the same SSID on different channels.

3. Have you installed any additional software that might be fighting with the system. For instance set CPU is now redundant - as the same functionality is built into CM7 and it will fight with the system if you install it. So you haven't installed any unecessary wpa_supplicant fixes, right? Or a profile manager? And you are not using a task killer, right?
[Nook Color General] patgnds:
I used a task killer last night and for the first time had problems with file explert connecting. After reinstall it started to work again. This was the only time I have had any problems with wifi.
[Nook Color General] ringbolo:
I've tried several different builds of Nook Froyo (SD/EMMC), Stock Nook Color 1.01/1.1.0 & deeper-blue's Honeycomb v01 and they all worked with my wireless connection. Laptop also works.

I will do a fresh install of a CM7 build (wiping system, cache, data), reboot and the first thing I try to do is connect to Wi-Fi and It would get stuck in at: scanning... connecting... disconnecting.... I've tried to login numerous times making sure the password is correct and nothing.

After giving up I would do a fresh install of Nookie Froyo 0.6.8 and try to access my Wi-Fi and it connects on the first try. As I said, I am not sure why coping the wifi folder works but it works.
[Nook Color General] timekeeper:
Disregard my post, moving to another area of campus made it connect smooth as butter.
[Nook Color General] hongkongdisney:
I have installed phiremod nook V3 to my nc, everything is ok,

except for the wifi connection.

My nc can't connect to any hotspot even my iphone 4

but it can connect to my router (linksys 54-TM the setting is G not mix mode).

I want to try it but I don't know how to copy the wifi folder you provided to my nook.

Is it the script like that:

adb push ??? /system/etc/

How about the script for chmod 644?

thx a lot!
[Nook Color General] albapol:
I have neither Wi-Fi, not USB working now

I have exactly the same issue with the nightly build 8 (2011-02-27) when connecting to my D-Link DIR-655 with WPA2 encryption. My Nook with CM7 would not connect in a meter from a router. I have other wireless devices, like PSP, Cruz Reader, Acer netbook, etc. and all of them work just fine, likewise the same Nook with the original firmware. On the top of that now Nook does not connect via USB to neither XP nor Window 7, which was also working fine with the stock firmware. I followed the instructions from the wiki.
[Nook Color General] trippnk:
Add one more nook to the wifi problem list. I've tried every encryption method and can't get my nook to connect. The only way I could connect was in "Open" and thats not an option.
[Nook Color General] alershka:
Add me to the list as well. I just installed CM7 nightly 12 and I can not connect to my network. It worked prior to installing CM7, ie. rooted stock on the Nook.

I am also running the Dlink DIR-655 and WPA2 encryption as my main router. I also have an Asus working as a repeater using the same SSID but with all other settings the same.

I rebooted the router and repeater and the nook and I wiped and reinstalled CM7. Nothing worked and that didn't work. I get the scanning, connecting, disconnected loop. Without a connection, I really can't do much so I'm going to have to find another rom.
[Nook Color General] ChickenGod:
Thanks for this thread. I was trying to figure out why Nookie Froyo and HCv4 worked for me, but not Phiremod...then I realized that Phiremod is CM7 based. I really liked the look of it, but I never REALLY got to try it out because of the stupid wi-fi issue.

The odd part is at my school, the network is "open." I'll have to try this out and post my results...At first I thought it was the WPA_supplicant file that was all messed up and I was gonna push a different one from Nookie but I got too frustrated.
[Nook Color General] edgie168:
Switching to tkip-only encryption worked. There seems to be an issue with aes encryption and cm7 (on build 13 now).

-via Nook Color.
[Nook Color General] ChickenGod:
Pushing all the files worked for me. Don't push softap...you don't need to...

Just push the tiwlan_drv.ko, tiwlan.ini, and wpa_supplicant.conf files. You should be golden.
[Nook Color General] eyecrispy:
Are you still having trouble connecting to your iPhone? I am using mywi on it and trying to tether using mywi kills my NC 's wifi completely for all wifi networks.
[Nook Color General] sandtiger:
I am not sure what it was on my DIR-655 but i set it to B & G only and it solved the connection issues for me. I am not sure if it is the encryption our CM7 NC's are having issue with or the Wireless N.
[Nook Color General] esuuuu09:
Was on CM7 12 and now on CM7 13. Been having problems with wifi all along. Thanks for this post. Will try when I get back today :)
[Nook Color General] blitz80690:
Having same issue with Wireless N

I too was having issues with CM7 and not connecting to my D-Link DIR-615 Wireless N network (WP2 with AES).

I have already gone back to stock then autonooter 3.0... but that left me with very low usb transfer speeds (0.5 or less kb).

I will have to try this fix out.

Thanks for the post!
[Nook Color General] esuuuu09:
How did you push the file to your nook? Cwr and install zip? If not, how would you install it? The change from aes encryption to tkip encryption worked for now but I would love to be able to get on aes Encryption if possible. Thanks
[Nook Color General] Tolax:
Another one with the DIR-655/WPA2 issue running with CM7. Anytime I enable N then I loose the wireless connection. Setting the DIR-655 to G makes everything connect.

On another network I run WPA2 on a Cisco e2000 and that connects without issue on N. The combination of DIR-655-WPA2-Wireless N seems to be the issue

Tolax
[Nook Color General] mndev12:
This fixed my 802.1x issue with my nook color. Thanks!
[Nook Color General] Pops_G:
I was able to pull this off with these steps. I was a adb noobie.

Step 1: Youtube video, How to Setup ADB for the Nook Color http://www.youtube.com/watch?v=wL3849_QPGA

Step 2: Download the file in the OP and extract to a temp directory, I will call [TEMPDIR]

Step 3: Connect to the phone with ADB and type the following commands at the command prompt

C:\android-sdk-windows\platform-tools>

adb remount

adb push C:\[TEMPDIR]\wifi\tiwlan.ini" "/system/etc/wifi"

adb push C:\[TEMPDIR]\wifi\tiwlan_drv.ko" "/system/etc/wifi"

adb push C:\[TEMPDIR]\wifi\wpa_supplicant.conf" "/system/etc/wifi"

Step 4: I did NOT do this, but the OP said he did. It worked without me doing this so do it if you think you need it.

adb shell

cd system/etc/wifi

chmod 644 tiwlan.ini

chmod 644 tiwlan_drv.ko

chmod 644 wpa_supplicant.con

ps. I also had this problem with a dlink 655 like most of the others.
[Nook Color General] digg.jinx:
I too have a D-Link DIR-655 with WPA2 AES encryption, and replacing those files corrected my issue! Thanks OP!
[Nook Color General] blitz80690:
Thank you OP. This absolutely fixed my problem with Phiremod 4.1 internet connection to a D-Link DIR-615 Wireless N router!
[Nook Color General] Compnetbobby:
god bless you, this worked
[Nook Color General] msung330:
I just got my NC last night and I have the *EXACT* same config (D-Link DIR-655) and problem and just started to investigate... it's actually a relief that others have the same issue. A few interesting things on my side:

1. Router I run 802.11b/g/n, WPA2. No problem MacBook Air, PC laptop, iPhone 3GS, or other people connecting.

2. NC 1.1 unrooted, out of the box connects just fine, no problems.

3. Router has the latest D-Link firmware, tried all sorts of different combos 802.11 mixed or single b, g, or n. WPA2, WPA, WEP, etc.

4. Installed both CM7 and the latest phiremod and have that problem... it will never "connect/acquire IP address" properly and just endless loops scanning... connecting... disconnecting. Sometimes it loses sight of my wifi network.

5. NC rooted in various versions have no problem hooking up to my iPhone 3GS in ad-hoc/hot-spot mode... so thankfully it does work and I didn't fry my wifi.

6. After farting around for ~4 hours, I went back to a clean 1.1 unrooted install, then re-rooted it using autonoot 3.0, and everything's fine again. Actually, that build is quite nice (a bit annoying you need to go to Market to launch other 3rd party apps) but at least my wifi works at home.

I'll report back if I see any good info on this... but +1 for someone else with D-Link DIR-655 and rooted NC wifi problems.

--

UPDATE: best/easiest solution after trying a bunch of different things (I haven't been able to get ADB drivers up and running, mainly because my Win7 box is such a mess)... installed Phiremod v5 last night, changed my router to use b/g/n (need n because of laptop connect speeds), kept WPA2, turned to TKIP only, no AES.) Nook Color connects fine. This was a good compromise, since I still want 802.11n speeds and the security compromise is acceptable.

Thanks again to the nook community for all the great development and tips. I hope we can get the wifi file updates baked into future updates!
[Nook Color General] jgayda666:
I have the same issues as the others. Same router/setup as well.

Have not tried the fix yet though.
[Nook Color General] leorob:
Wf-Fi Fix if running off SD Card?

I am having the same Wi-Fi issues with CM7 but am running it off the SD Card.

The ADB commands don't work in this instance. So, How to fix the Wi-Fi issue running CM7 off the SD card?
[Nook Color General] St1ck33:
First post. Got my Nook yesterday, installed Phiremod 5.1 and wireless is flaky. Have a D-Link DIR-615, WPA.

Also, was at my parent's place for most of the ay, and at their house, no connection issues whatsoever.

Haven't tried copying files over... so far, just playing with router settings.
[Nook Color General] C0BRA01:
Really weird wifi problems.

I set up a nook for a friend, and wifi didn't work on it like on mine when I 1st setup cm7 rc4 GB. I did this copy over (the Nookie Froyo .68 files) which worked fine for mine, but didn't on his. I could not get it to work. So I did a CWR backup of my ROM, and restored it to his. This seemed to work, but I had to wipe the user data on his, so he was not using my market logon. Once I did that, connections were hit, or miss. Since it is now cloned from mine, you would think it would work O.k. They were even both originally the 1.1 ROMs. I am totally at a loss to understand why mine works, and his doesn't, from what is a restore from mine???
[Nook Color General] Adanedhels:
The wifi problems...

Ok your friends router is it a Linksys? Is it set to WPA2? If so it is using AES encryption. He needs to switch it to TKIP as the current build of CM7 DOES NOT LIKE AES which sucks as AES is "safer" but beggers cant be choosers right now...

Adan
[Nook Color General] C0BRA01:
wifi problems

If you are responding to me, then why does mine work, and his does not? I even cloned my install to his. It's a Cisco. WPA. Not sure of the encryption type. Anyway, good to know. I'll pass that along.
[Nook Color General] guy760:
Thenks

Thanks for your post
[Nook Color General] bitnerd:
I did have the OP same problem with WPA2/AES way back in the CM7 nightly builds but haven't seen it since. WPA2/AES is all I run on my routers (a mixture of Ubiquiti and Buffalo routers running OpenWRT) and the nook has been running fine on it for the last month.

The only issue I have seen, and I haven't checked to see if it's resolved, involves the wifi sleep policy. It used to be that it could have problems coming back on if it was set to sleep when the screen was off. Haven't tried it recently
[Nook Color General] khaytsus:
As of Nightly 35 I could not stay connected to a router I set up at work nor my home router, nor my Nexus One wifi tether. All were either AES or TKIP+AES. I switched the two routers to TKIP-Only and all of my problems went away.

Not much I can do about the Nexus One except set it to Open. :(

When did this problem go away for you? Since 35? Otherwise, maybe a different problem than mine albeit with similar symptoms..
[Nook Color General] khaytsus:
Interesting about wpa_supplicant.conf, isn't that modified based on the connections you've set up? Also interesting to note is that the same file are in CM7 Nightly 37, although they are different checksums etc..

Thanks :)