Open GoogleCodeExporter opened 9 years ago
Original comment by trmfrei...@gmail.com
on 17 Feb 2011 at 3:29
This still happens in 6.3-rc7.
Original comment by trmfrei...@gmail.com
on 17 Feb 2011 at 4:43
This DOESN'T happen in 6.3 RC7!
Original comment by lfg.1...@gmail.com
on 17 Feb 2011 at 7:06
Original comment by trmfrei...@gmail.com
on 17 Feb 2011 at 11:53
I have the same problem in 6.3 rc6 & rc7, don't know wipe can fix it in rc7 or
not, because I upgrade from rc6 without wipe.
Original comment by tony...@gmail.com
on 18 Feb 2011 at 3:29
NOT happen in 6.3-RC7, try use wipe option in flashing process
Original comment by Adhi.Muk...@gmail.com
on 20 Feb 2011 at 12:12
[deleted comment]
Yes IT DOES. With or without wipe it just keeps going on and off again and
again...
Original comment by carno...@gmail.com
on 21 Feb 2011 at 3:39
carno.... please provide a logcat while it is cycling.
Thank you
Original comment by trmfrei...@gmail.com
on 21 Feb 2011 at 10:08
Ok. Let's start being productive, because I'm the biggest interested in this
getting to work properly. I might even write some code, but I'm a Java
programmer and I don't think that could be helpful here :(. Here's your logcat.
Looking forward to help as much as I can
Original comment by carno...@gmail.com
on 21 Feb 2011 at 8:03
Attachments:
Yop, Here is mine...
I made comment in the file corresponding to what happens/I see during the
logcat. They look like this:
******************************************************
* *
* Starting the first connection/reconnection *
* *
******************************************************
I was doing nothing else but reading news on the web (and pressing menu once to
go out from sleep)
Original comment by nobbo...@gmail.com
on 21 Feb 2011 at 9:24
Attachments:
Thank you.
A volunteer is needed to analyze the logs.
Original comment by trmfrei...@gmail.com
on 22 Feb 2011 at 12:28
Any update in analyzing the logs? This is the most frustrating bug on rc7...
Original comment by LynnYeb...@gmail.com
on 2 Mar 2011 at 4:44
I have very similar logcat as nobbo. It's still the same since I upgraded from
6.1-rc5 to 6.3-rc7 WITH WIPE! Very frustrating, nearly unusable for IMs... I
think the priority should be set to High because it seems many people won't use
6.3-rc7 with this bug (see http://forum.openetna.com/index.php?topic=773.0).
Original comment by The.Bo...@gmail.com
on 7 Mar 2011 at 11:15
yo tbm puedo ayudar si es necesario con codigo tanbien soy programador
Original comment by derly...@gmail.com
on 17 Mar 2011 at 1:19
i have the same problem using rc7
Original comment by gecekusu...@gmail.com
on 2 Apr 2011 at 9:17
Same problem for me. I did a clean instal of 6.3 Rc7. Wifi CONSTANTLY
disconnects.
Original comment by ebert.ep...@gmail.com
on 15 Apr 2011 at 5:06
Issue 451 has been merged into this issue.
Original comment by trmfrei...@gmail.com
on 5 May 2011 at 1:43
same problem. need help!
Original comment by hakop...@gmail.com
on 6 Jun 2011 at 5:14
I've been affected by this bug on a GW620, updated to KH9200 with a korean
firmware.
Here's my experience:
- while trying to connect to a fast 802.11g network on an RTL 8186 chipset,
without distance or low signal problems (I have a fairly complex setting at
home, with multiple access points working as repeaters or in WDS mode), the
smartphone presented those problems constantly disconnecting and trying to
reconnect again without success;
- Changed the wi-fi settings, to fixed IP address. The cell "connected" for a
brief period and disconnected after about 15 to 30 seconds. A desktop running
'ping' showed no answer from the cell phone. The pattern
connect-disconnect-reconnect was repeated a couple times until the wi-fi
interface was automatically turned off by the android interface;
- When trying to turn on wi-fi again, got an error and it remained on "off"
state. A new trial and was presented with a kernel panic. Had to remove the
battery and reboot android;
- I have an old 802.11b access point, a Netgear WGR613VAL. The cell phone
connected to this AP without a single problem!
Maybe it is a small kernel flaw or even it's a bug in the firmware running on
some access points.
Original comment by marcus.m...@gmail.com
on 27 Jul 2011 at 12:54
Original issue reported on code.google.com by
trmfrei...@gmail.com
on 15 Feb 2011 at 1:27