Pandaboard wifi on keeps forcing return to home screen

[Chris Bainbridge]

Hello,

I built AOSP master for Pandaboard yesterday. As soon as I enable
wifi, it seems to get stuck in some loop where it keeps closing the
foreground app and returning to the home screen. Logcat shows:

I/ActivityManager( 265): START {act=android.intent.action.MAIN
cat=[android.intent.category.HOME] flg=0x10200000
cmp=com.android.launcher/com.android.launcher2.Launcher u=0} from pid
265

pid 265 is system_server. These messages are appearing at a rate of
several a second to once every few seconds. Any ideas why this is
happening and how can I stop it? Has anyone else seen this issue? As
soon as I turn wifi off, then everything goes back to working
normally. But I obviously want to be able to use wifi.

D/wpa_supplicant( 605): nl80211: Event message available
D/wpa_supplicant( 605): nl80211: New scan results available
D/wpa_supplicant( 605): nl80211: Received scan results (5 BSSes)
D/wpa_supplicant( 605): nl80211: Survey data missing
D/wpa_supplicant( 605): Add randomness: count=1 entropy=0
D/wpa_supplicant( 605): Add randomness: count=2 entropy=1
D/wpa_supplicant( 605): Add randomness: count=3 entropy=2
D/wpa_supplicant( 605): Add randomness: count=4 entropy=3
D/wpa_supplicant( 605): Add randomness: count=5 entropy=4
D/wpa_supplicant( 605): Calling set grouple idle_timeout from
notif_disconnected
D/wpa_supplicant( 605): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
D/wpa_supplicant( 605): RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
I/ActivityManager( 267): START {act=android.intent.action.MAIN
cat=[android.intent.category.HOME] flg=0x10200000
cmp=com.android.launcher/com.android.launcher2.Launcher u=0} from pid
267

D/wpa_supplicant( 605): Calling set grouple idle_timeout from
notif_disconnected
D/wpa_supplicant( 605): Scan requested (ret=0) - scan timeout 30 seconds
D/wpa_supplicant( 605): nl80211: Event message available
D/wpa_supplicant( 605): nl80211: Scan trigger
D/wpa_supplicant( 605): nl80211: Event message available
D/wpa_supplicant( 605): nl80211: New scan results available
D/wpa_supplicant( 605): nl80211: Received scan results (2 BSSes)
D/wpa_supplicant( 605): nl80211: Survey data missing
D/wpa_supplicant( 605): Add randomness: count=14 entropy=13
D/wpa_supplicant( 605): Add randomness: count=15 entropy=14
D/wpa_supplicant( 605): Calling set grouple idle_timeout from
notif_disconnected
D/wpa_supplicant( 605): RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
D/wpa_supplicant( 605): RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
I/ActivityManager( 267): START {act=android.intent.action.MAIN
cat=[android.intent.category.HOME] flg=0x10200000
cmp=com.android.launcher/com.android.launcher2.Launcher u=0} from pid
267

[Chris Bainbridge]

Did another build today, I am still seeing this issue. Makes it
impossible to connect to a protected wifi network since every time I
try to open the network settings it gets closed again before I can
type in the key. Is this just a pandaboard bug or is wifi setup from a
blank system (no cache or user settings) broken on all targets?

[Chris Bainbridge]

Yes, I see the same. The first time I tried your suggestion (bringing
bluetooth up first) the system hard locked when I enabled wifi. The
second time I tried, I was able to turn wifi on but the scan showed no
networks. The third time I tried, I was able to scan a network and
connect.

On 27 August 2012 14:54, Robert Konopka <rkon...@leenox.de> wrote:
> Hi Chris,
>
> I can observe the same issue on my Pandaboard. I can work around it when I
> turn on bluetooth before switching wifi on. Switching on wifi first leads to
> the situation you described. Can you confirm this?
>
> best regards
>
> Rob

> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en

[olivia mckenzy]

Hi, i think i solved this problem a few months ago, in the folder device/ti/panda there is a file named gpio-keys.kl, the only line there that says:

key 102  HOME   WAKE


i commented that line so the line that i have ther now is:


#key 102  HOME   WAKE


i had the same issue than you, and i even thought that it was the bluetooth or the wifi, but it is about input events, when a click is performed, a signal of going back to the home screen is sent to the O.S, i don't know if that was the best solution, or why that line was there in the sources but the only thing i know is that it solved my problem, it might be a solution for you.

Best Regards.

2012/8/28 Robert Konopka <rkon...@leenox.de>

I wonder if we are alone with this issue or if other Pandaboards also show this bug?

Could anybody else check this?

[olivia mckenzy]

Hi, i'm glad it worked for you too, and i really don't know what is it for, i was going to search about it but i haven't had enough time for it, if you find something about it, tell me about it to have some info of that, the only thing i knew was that it was sending input events when i was tracing the system to catch the problem.

Best Regards.

2012/8/29 Robert Konopka <rkon...@leenox.de>

Thanks, this solution works for me!

But I would like understand why. Do you know what this file and the entry in it is for?